Update an Oracle database

The database is properly configured and running.
  • If your original cluster is Symphony 3.1, you have applied the required Symphony 3.1 patch (Solution 88352) from Platform.

  • You have a user name, password, and URL to access the database server. You can create triggers, sequences, tables, and stored procedures.

  • You installed the latest JDBC driver (ojdbc14.jar or newer) for the database. This driver is available from the following URL:

    http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html

  • You are able to run sqlplus.

To update a Platform product, get the corresponding database update scripts from Platform and update the database schema before you update the cluster.

For a normal Platform Symphony cluster that consists of Symphony and EGO components, get the following packages:

  • 3.1 to 4.1

    • upgrade_ego_data_1_2_1_to_1_2_3.sql

    • upgrade_sym_data_3_1_to_4_1.sql

  • 3.2 to 4.1

    • upgrade_sym_data_3_2_to_4_1.sql

If you have Symphony 3.1 with LSF in the cluster, get the following packages:

  • upgrade_ego_data_1_2_1_to_1_2_3_mh.sql

  • upgrade_sym_data_3_1_to_4_1_mh.sql

  1. Extract the database update scripts to any directory.
  2. In the command console, change to the Oracle/Patch subdirectory. For example, if you extracted the scripts to sym41_temp:

    cd sym41_temp/DBschema/Oracle/Patch

  3. Run the scripts in this directory to update the database schema.

    sqlplus user_name/password@connect_string @update_script

    where
    • user_name is the user name on the database server

    • password is the password for this user name on the database server

    • connect_string is the named SQLNet connection for this database

    • update_script is the name of the update script

  4. Additionally, after installation, you must copy the jdbc driver to:

    EGO_TOP/gui/1.2.3u1/lib

    EGO_TOP/perf/1.2.3u1/lib