Running the post-upgrade DBA script (Db2)

Applies to: On premises

Ask your database administrator to run the post-upgrade script. Or, if you have the required Db2® authorities, you can run the script.

Before you begin

  • The IBM® Db2 database server is running. All other OpenPages® servers are stopped.
  • The JAVA_HOME system variable is defined and points to the Java™ SDK that is installed with Db2. For example, for Db2 11.5: 
    export JAVA_HOME=/db2/V11.5/java/jdk64
export PATH=$JAVA_HOME/bin:$PATH

    If you are running the script from another host, ensure that JAVA_HOME is pointing to the Java SDK that is installed on the computer.

  • The DB2_HOME system variable is defined.
  • The op-database-product-upgrade.sh|.bat script completed successfully.

About this task

Run the following script: op-database-dba-upgrade.sh|.bat. The script uses the parameters that are defined in the sql-wrapper.sql file.

Procedure

  1. Log on to the IBM Db2 database server computer as a database administrator (DBA).
  2. Locate the scripts that are required.

    If you are a database administrator, get the scripts from your OpenPages team.

    Or, you can get the scripts from the /OP_<version>_Main/OP_<version>_Configuration/Database/DB2/UPGRADE_SCRIPTS directory.

  3. Verify that you have execute permission on the scripts in UPGRADE_SCRIPTS and its subdirectories.
  4. Open the sql-wrapper.sql file. Verify that the values are suitable for your environment.
    • If you are installing an OpenPages fix pack, use the Db2 instance owner, which has DBADM and SECADM authorities.
    • If you are upgrading, use the Db2 instance owner, which has DBADM and SECADM authorities.
    • If you are migrating, use a Db2 user with the following authorities:
      • Releases prior to Db2 11.5.6: Both DBADM and SECADM authorities
      • Releases after Db2 11.5.7: DBADM, SECADM, and SYSADM authorities

        If you want to avoid the SYSADM requirement that was introduced in Db2 11.5.7, an alternative approach is to modify the DB2_ALTERNATE_AUTHZ_BEHAVIOUR registry variable to include the NOT_FENCED_ROUTINE_DBAUTH value. For more information, see the Db2 documentation.

  5. Run the following command:
    • On Linux®:
      ./op-database-dba-upgrade.sh post '<dba_password>'
    • Windows:
      op-database-dba-upgrade.bat post "<dba_password>"
    Note: Quotation marks are required around a password only if the password contains special characters. See Special characters in passwords.
  6. Verify that the return code is 0, indicating success.

    You can also check the log file: op-database-dba-upgrade.post.*.log.

What to do next

Validate the post-upgrade DBA step.