WebSphere Commerce Developer

Troubleshooting: 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.


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


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. Navigate to the WCDE_installdir/bin directory.
  3. Manually update the database:
    1. Ensure that you have a backup of the database. This backup ensures that the database can be reverted to the state it was in before the unsuccessful attempt to run the updatedb command.
    2. From a command prompt, run the following command:
      • Apache DerbyWCDE_installdir\bin\updatedb.bat cloudscape
      • DB2WCDE_installdir/bin/updatedb.bat db2 database_name database_user_name database_user_password
      • OracleWCDE_installdir/bin/updatedb.bat oracle database_name database_user_name database_user_password database_host server_port
      • For IBM i OS operating systemWCDE_installdir/bin/updatedb.bat iseries database_name database_user_name database_user_password database_host
      The name of your WebSphere Commerce Developer database. For example, WCDE_installdir/db/mall
      The name of your WebSphere Commerce Developer database user.
      The WebSphere Commerce Developer database user password.
      The database server host name.
      The database server host port number.
    3. When the update is complete, review the output that is displayed in the console window to ensure that you successfully updated the database to the correct fix pack level. For example:
      UpdateSiteTable: [EchoNL] Updating database fixpack level ... 
      [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.