Page Comparison

...

1. Before performing an upgrade, the database may require an upgrade by running certain patch scripts. 
    

   1. Run the following script for generating a *.tar file containing the patch script(s):

      Code Block
      $ ./setup.sh prepare_db_upgrade

      
      

      Note
      title Note!
      You must specify username, password, and database type. You can also specify them using command line. Code Block theme Eclipse $ ./setup.sh prepare_db_upgrade -Dmz.username=mzadmin -Dmz.password=<password> -Dmz.databasetype=<database type: [oracle, postgresql, derby, saphana]>

      The file database-upgrade.tar containing the required patch scripts is generated.

      Info
      title Derby Database
      For a Derby database, no tar file is generated. It is automatically upgraded during step 2, skipping steps b-d.

      
      

   2. Copy the file to the database server. This is not applicable for Derby databases.
       

   3. Extract the script(s):

      Code Block
      $ tar xvf database-upgrade.tar

      
       

   4. Run the commands specific to the database.

      1. For Oracle:

         Code Block
         $ sqlplus <Owner user>/<password> < database-upgrade.sql $ sqlplus <JDBC User>/<password> < database-upgrade-synonyms.sql

         
         

      2. For PostgreSQL:

         Code Block
         $ psql -d mz -U <Owner user> -f database-upgrade.sql

         
         

      3. For SAP HANA:

         Code Block
         $ hdbsql -d MZ -u <JDBC User> -p <password> -I database-upgrade.sql

         
         

2. Use the setup script setup.sh, that which was extracted when unzipping the upgrade software, to upgrade the Platform Container.

$ ./setup.sh upgrade

$ ./setup.sh upgrade -DsilentMode=y

      3. Enter user name and password at the prompt.

$ ./setup.sh upgrade -Dmz.username=mzadmin -Dmz.password=<password>

      4. Enter the URL for the Platform web interface at the prompt, e g  http://platform1:9000, and the upgrade will start. 

$ ./setup.sh upgrade -Dmz.platform=<URL>

When using the setup.sh upgrade command, three different log files will be created; generate<timestamp>.log, validate<timestamp>.log, and upgrade<timestamp>.log. By default, these log files will be placed in the same directory as setup.sh. If you want the log file to be placed in another directory, you can add the upgradelogdir property to the setup script.

$ ./setup.sh upgrade -Dmz.upgradelogdir=<directory path>

A successful upgrade command will print out "Version successfully changed from <old_version> to <new_version>" at the end of the command output. A successful upgrade may also print out "The following things may require your manual attention" at the end of the command output, followed by a list of things that may need manual attention. In case the upgrade was unsuccessful, this will be indicated. Check the latest upgrade_<timestamp>.log foe for further details in order to analyze the result and see what may have caused the problem. If it is needed, a downgrade can be performed. For information about how to perform a downgrade, see 7. Standard Downgrade Procedure.

Mon Nov 19 10:52:10 CET 2013 Regenerating configs 
The following configurations changed status 
and may require manual attention: 
Workflow Test.WF1 became invalid, 
Workflow Test.WF2 became invalid, 
APL Code Test.apl_profile became invalid,