Troubleshooting: Database update fails after instance creation
After you create an instance using an existing database, an attempt to update the database fails.
Problem
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.Solution
Note: The database administrator
password is required only when the database has workspaces or content
versioning enabled.
- Generate the encrypted password using the wcs_encrypt utility:
- Start:
- A command line session.
- A QShell session.
- A command prompt session.
- Change to the following directory:
- WC_installdir/bin
- WC_installdir\bin
- Issue the following command:
./wcs_encrypt.sh dba_password
-
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.
- Start:
- Follow the manual instructions in Update
the WebSphere Commerce configuration file to ensure that the
information is properly recorded:
- In the WebSphere Commerce configuration file, search for the field named "DBAPwd". The "DBAPwd" field is under config/InstanceProperties/Database/DB.
- Update the field with the ASCII encrypted password from the step 1c.
- Save and deploy the changes.
- 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.