The updatedb script fails during the application of the fix pack

If the updatedb script fails, you can try to perform a manual update of the database.

Problem

The updatedb process fails during the WebSphere Commerce fix pack update.
Note: If the updatedb process fails during the WebSphere Commerce Developer fix pack update, see the following WebSphere Commerce Developer fix pack troubleshooting topic.

Solution

Complete these steps:

  1. Go to the following directory:
    • SolarisLinuxAIXWC_installdir/logs/updatedb
    • WindowsWC_installdir\logs\updatedb
    • WebSphere Commerce DeveloperWCDE_installdir\logs
    Review the following log files:
    • SolarisLinuxWindowsAIXupdatedb-instance_name.log
    • WebSphere Commerce Developerupdatedb.log
    • trace.txt
    • messages.txt
    Where instance_name is the name of your instance, such as demo. For instance, updatedb-demo.log. The trace.txt and messages.txt files are log files for the massload utility, which is called by the updatedb utility. Review these error messages with your database administrator to ensure that there are no data errors.
    Feature Pack 7 or laterNote: You can also encounter errors when you are running a process or utility if the input parameters that are used to establish a database connection are incorrect. To validate that a database connection can be established with the configured input parameters, use the database connection validation utility. For more information about running this utility, see Running the database connection validation utility.
  2. Manually update the database:
    1. Ensure that you have a backup of the database. This backup ensures that the database is reverted to the state it was in before the unsuccessful attempt to run the updatedb command.
    2. Complete one of the following actions:
      • SolarisLinuxAIXLog on as the non-root user.
      • WindowsLog on as a user with Administrator privileges
    3. From a command prompt, run the following command:
      • SolarisLinuxAIXWC_installdir/bin/updatedb.sh instance_name [currentPropFile]
      • WindowsWC_installdir/bin/updatedb.bat instance_name [currentPropFile]
      • WebSphere Commerce Version 7.0.0.3WebSphere Commerce Version 7.0.0.2For IBM i OS operating systemWebSphere Commerce Version 7.0.0.1WC_installdir/bin/updatedb.sh instance_name [currentPropFile]
      Where instance_name is the name of the instance to be updated.

      DB2The currentPropFile is the full path and name of the database properties file. The currentPropFile is used when a database, other than the one specified in the instance.xml file, is to be updated. For example, two databases might be configured; one for operational purposes and the other for content purposes. The currentPropFile takes the same format as the createInstance.properties found under directory WC_installdir/instances/instance_name/properties. The database section in the currentPropFile is used to acquire the parameters that are required for the updatedb command.

    4. When the update is complete, review the output that is displayed in the console window and ensure that you successfully update the database to the correct fix pack level. For example:
      UpdateSiteTable: [EchoNL] Updating database fixpack level ... 
      [eCDatabaseVersionInfo] UPDATE SITE SET EDITION='ENT', VERSION=7, RELEASE=0, MOD=0, FIXPACK=X WHERE COMPNAME='BASE' 
      [eCDatabaseVersionInfo] SELECT COUNT(*) FROM SITE 
      [eCDatabaseVersionInfo] SELECT * FROM SITE 
      [eCDatabaseVersionInfo] Columns in SITE table: 
      [eCDatabaseVersionInfo] COMPNAME=BASE 
      [eCDatabaseVersionInfo] EDITION=ENT 
      [eCDatabaseVersionInfo] VERSION=7 
      [eCDatabaseVersionInfo] RELEASE=0 
      [eCDatabaseVersionInfo] MOD=0 
      [eCDatabaseVersionInfo] FIXPACK=X 
      [eCDatabaseVersionInfo] Updated SITE table successfully. 
      [EchoNL] Completed database fixpack update.  BUILD SUCCESSFUL 
      Where X is the number of the fix pack installed.