Upgrade ALBPM 5.5 Oracle DBs

This section explain how to upgrade the structure of ALBPM 5.5 databases on Oracle.

Follow these steps if you are upgrading from ALBPM version 5.5.x (and not 5.7.x) using Oracle as the database server.

You need a database user with enough privileges to perform SQL DDL (Data Definition Language) operations (like ALTER, CREATE and DROP statements) on the ALBPM databases.

  1. Locate the 5.5 to 6.0 migration SQL scripts for Oracle.

    ALBPM Enterprise 6.0.3+ (on the first Hotfix) includes SQL scripts for upgrading the structure of ALBPM 5.5 databases on Oracle. These scripts are located under the following directory: <ALBPM_DIR>/conf/migration/oracle/. Refer to Upgrade Scripts for 5.5 on Oracle for a detailed list of files included.

    You have one directory for each ALBPM database to upgrade:
    • directory/ (for ALBPM Directory database)
    • engine/ (for ALBPM Engine database)
    • archiving/ (for ALBPM Archiving database)
    • bam/ (for ALBPM Business Activity Monitoring database)
    • dataMart/ (for ALBPM DataMart database -formerly "DataStore" for historical reporting-)
  2. For each ALBPM 5.5 database, follow the steps below to run the SQL migration scripts.
    1. Modify the SQL scripts to match your database schema name.

      Open each .sql script file with a text editor and replace the text <schema_name> with the actual name of your schema.

    2. Review the scripts and ensure they fit your environment.

      Each .sql script may include specific instructions on how it works and how to use it. Make sure you read them before executing any SQL statements.

    3. Execute the SQL scripts to upgrade the database structure.
      Important: You must run more than one SQL script on each database, in the right order. The file name of each SQL script is prefixed with a number indicating the order in which they must be executed.
      For example, for upgrading the Directory database, you must execute the following scripts, in this order:
      1. 1DisableConstraints.sql
      2. 2AlterTables.sql
      3. 3RebuildIndexes.sql
      4. 4EnableConstraints.sql
      5. 5UpdateFDIVersionInfo.sql
      Important: Some scripts (like 1DisableConstraints.sql and 4EnableConstraints.sql) do not modify your database. Instead, they construct and return a list of SQL statements which you must capture and execute on your database.
      You can use Oracle's sqlplus command to execute each script, following this syntax:
        sqlplus <user_id>/<password> @<file_name>
      
      Example:
        sqlplus system/manager @2AlterTables.sql