LinuxFeature Pack 8

WebSphere Commerce Patterns 2.1 deployment failure due to database errors

After you deploy WebSphere Commerce Patterns 2.1, you notice database failures.

For example, you might notice a red X that indicates a failure on the dbname_DB_PC_DB2_Server-Part process, where dbname is the name of your database. The default database name is comm. The failure is also indicated in various locations in the virtual machine:
  • Under dbname_DB_PC_HADR_Primary, in the Middleware status section:

    Red X beside dbname_DB_PC_HADR_Primary dbname_DB_PC_DB2_Server-Part

  • Under dbname_DB_PC_HADR_Standby, in the Middleware status section:

    Red X beside dbname_DB_PC_HADR_Primary dbname_DB_PC_DB2_Server-Part

  • In the Script packages section:

    Red X beside CreateDB_HADRStandby.

Problem

The Tivoli Storage Manager plug-in for IBM DB2 with BLU Acceleration Pattern 1.2.1 is not configured properly. By default, the Tivoli Storage Manager server properties for IBM DB2 with BLU Acceleration Pattern 1.2.1 are preconfigured with hardcoded values.

Solution

Update the Tivoli Storage Manager server properties:
  1. Click Catalog > System Plug-ins
  2. In the Filter drop-down menu, select IBM DB2 with BLU Acceleration Pattern 1.2.1.0
  3. Select tsmclient 1.2.1.0.
  4. Click Configure. The TSM configuration window opens.
  5. Update the fields:
    • If you want to enable Tivoli Storage Manager to back up DB2 log files, update all fields to match your server properties.
    • If you do not want to enable Tivoli Storage Manager and you want to store the DB2 log files on the local file system, clear the TSM server address and TSM server administrator password fields.