Rollback errors during a database upgrade

When you upgrade the OpenPages® database, the upgrade script reports the following error: [exec] Load PL/SQL package failed. Please check log file..

Review the AuroraProcCreate.log file. The AuroraProcCreate.log file that you need to check depends on the release that the upgrade script was applying when the error occurred. If you're upgrading across multiple releases, such as 8.1 to 8.3, you might need to look in multiple AuroraProcCreate.log files.

Examples:
  • If you are upgrading from OpenPages 8.2 to OpenPages 8.3, look at the AuroraProcCreate.log file in the /OP820X_TO_OP8300 directory. For Db2® the path is /OP_<version>_Main/OP_<version>_Configuration/Database/DB2/UPGRADE_SCRIPTS/OP820X_TO_OP8300
  • If you are upgrading from OpenPages 7.4 or 8.0.0.x to OpenPages 8.3, look at the AuroraProcCreate.log file in each of the following directories: /OP740X_TO_OP8100, /OP810X_TO_OP8200, and /OP820X_TO_OP8300.
Note: The directory names change for each OpenPages release.

In the AuroraProcCreate.log file, look for a message that is similar to the following example:

SQL0911N  The current transaction has been rolled back because of a deadlock 
or timeout.  Reason code "2".  LINE NUMBER=1.  SQLSTATE=40001

If you see this message, it's likely that one or more OpenPages components were running during the database upgrade.

To resolve the error, do the following steps:
  1. Shut down all OpenPages components. For more information, see Starting and stopping servers.
  2. Rerun the database upgrade script that failed with the [exec] Load PL/SQL package failed. Please check log file error.
    Note: If you are upgrading across multiple releases, you might need to set opx_override_ver_check to Y. For more information, see Preparing for the database upgrade (Db2).