Troubleshooting: Database update fails after instance creation

After you create an instance using an existing database, an attempt to update the database fails.


When you create an instance with an existing database, the Configuration Manager does not ask for the database administrator user ID and password, so it cannot record this information.


Note: The database administrator password is required only when the database has workspaces or content versioning enabled.
  1. Generate the encrypted password using the wcs_encrypt utility:
    1. Start:
      • LinuxAIXA command line session.
      • For IBM i OS operating systemA QShell session.
      • WindowsA command prompt session.
    2. Change to the following directory:
      • LinuxAIXFor IBM i OS operating systemWC_installdir/bin
      • WindowsWC_installdir\bin
    3. Issue the following command:
      • LinuxAIXFor IBM i OS operating system./ dba_password
      • Windows wcs_encrypt dba_password

      Where dba_password is the new password for the Configuration Manager.

      Two encrypted versions of the new password will be generated:

      • ASCII encrypted string
      • HEX encrypted string

      The ASCII encrypted string will be required for the next step.

  2. Follow the manual instructions in Update the WebSphere Commerce configuration file to ensure that the information is properly recorded:
    1. In the WebSphere Commerce configuration file, search for the field named "DBAPwd". The "DBAPwd" field is under config/InstanceProperties/Database/DB.
    2. Update the field with the ASCII encrypted password from the step 1c.
    3. Save and deploy the changes.
  3. Try again to update the instance.
Note: 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.