Article Original Creation Date: 2012-01-25

Overview

An error is received when updating from the 4.1.1 to the latest patch. During the upgrade process from 4.1.1 to 4.1.3, WebLogic shuts down for an unknown reason, and the log file had FORCE_SHUTTING_DOWN as an error message.

While patching to 4.2.0, the database patch stopped after 30+ minutes because of the table SPRT_NC_CWMP_LAST_SESSION is missing,

Environment

• Solaris 10
• Oracle 10
• Weblogic 9.2.3
• Apache-tomcat 5.5.25

Root Cause

The installation script caused the problem in automatic starting the WebLogic and patching database.

Resolution

To resolve the issue mentioned previously, follow the steps listed below:

1. Manually stop the WebLogic to prevent startup problems with the installer script.

2. Navigate to folder /usr/local/sprt/sg-admin/ and update the file sprt_installer.dat by replacing

   Components=,INIT_SG_4_0_DATABASE,SERVICEGATEWAY_4_0

   with

    Components=,SERVICEGATEWAY_4_0

3. Execute the database upgrade part manually following the process listed below:

   1. The scripts can are available in the <PATCH_DIR>/sql directory. Note that ServiceGateway 4.2.0.0 uses runSQL utility and not SQLPlus.

   2. Copy file ojdbc14.jar into <PATCH_DIR>.

   3. Change the directory to <PATCH_DIR>.

   4. Load the DDL (Data Definition Language) file:

      /path/to/java –cp <PATCH_DIR>/ojdbc14.jar:<PATCH_DIR>/scripts runSQL oracle <DB_IP> <DB_PORT> <DB_ID> <DB_USER> <DB_PASS> <PATCH_DIR>/sql/OracleDBChangesFrom4.1.3.0_DDL.sql

   5. Load the first DML (Data Manipulation Language) file:

      /path/to/java –cp <PATCH_DIR>/ojdbc14.jar:<PATCH_DIR>/scripts runSQL oracle <DB_IP> <DB_PORT> <DB_ID> <DB_USER> <DB_PASS> <PATCH_DIR>/sql/OracleDBChangesFrom4.1.3.0_DML_1.sql

   6. Load the second DML (Data Manipulation Language) file:

      /path/to/java –cp <PATCH_DIR>/ojdbc14.jar:<PATCH_DIR>/scripts runSQL oracle <DB_IP> <DB_PORT> <DB_ID> <DB_USER> <DB_PASS> <PATCH_DIR>/sql/OracleDBChangesFrom4.1.3.0_DML_2.sql

   7. Change directory to <PATCH_DIR>/sql.

4. Use the installer to update WebLogic part of the admin server.

5. Use the installer to update the WebLogic part of the managed server(s).

6. Reverse the change made in step 1 because the future upgrades, e.g., SG4.2.1 can use the automated installer process again.

7. Start WebLogic services.