Service Operations Insight

Problem: The ENTITY_FACT table allows the use of two "names" to uniquely identify an "entity", namely ENTITY_NAME and INSTANCE_NAME. Rollups, including hourly, daily and business hour rollups, successfully include rows from the ENTITY_FACT table that are identified by the pair ENTITY_NAME and INSTANCE_NAME. However, a bug prevents the REGRESSION_VALUES table from being populated with rows that are identified by both ENTITY_NAME and INSTANCE_NAME in the business hour rollup table.

Solution: The attached files contain a code fix for the Regression_precalc package and an enhancement for the Regression_values table. After deploying the package on your system, business hour rollup metrics should be correctly imported into the REGRESSION_VALUES table.

Follow these steps:

1. Download the hotfix package that corresponds to your release of Capacity Management (2.9 or 2.9.2) to a temporary location and uncompress it.

Note: In the steps that follow, replace "<version_number>" with the actual version number of your Capacity Command Center installation. For example:

C:\Program Files\CA\Capacity Command Center 2.9\ccc-migrations\standard\environments\ccc-db.properties

or

/opt/CA/CapacityCommandCenter2.9.2/ccc-migrations/standard/environments/ccc-db.properties

Deploy the Regression_values and Regression_precalc .sql files on your system:

2. Copy the 20151111225858_Regression_values_table.sql and 20151111235959_Regression_Precalcs_Pacakge_Creation.sql files to the following location:

Windows: C:\Program Files\CA\Capacity Command Center <version_number>\ccc-migrations\standard\scripts

Linux: /opt/CA/CapacityCommandCenter<version_number>/ccc-migrations/standard/scripts

3. Open the following file in a text editor:

Windows: C:\Program Files\CA\Capacity Command Center <version_number>\ccc-migrations\standard\environments\ccc-db.properties.

Linux: /opt/CA/CapacityCommandCenter<version_number>/ccc-migrations/standard/environments/ccc-db.properties.

Look for the password property. If the password is blank, provide the password for the current user, and save the file.

4. Open the following file in a text editor:

Windows: C:\Program Files\CA\Capacity Command Center <version_number>\ccc-migrations\cml\environments\ccc-db.properties.

Linux: /opt/CA/CapacityCommandCenter<version_number>/ccc-migrations/cml/environments/ccc-db.properties.

Look for the password property. If the password is blank, provide the password for the current user, and save the file.

5. Call the upgrade script:

Windows: Run the upgrade-ccc-db.bat file at C:\Program Files\CA\Capacity Command Center <version_number>\ccc-migrations\bin by double clicking on this file.

Linux: Run /opt/CA/CapacityCommandCenter<version_number>/ccc-migrations/bin/upgrade-ccc.db.sh in a terminal.

6. A log file named upgrade-ccc-db.log is created at:

Windows: C:\Program Files\CA\Capacity Command Center <version_number>\ccc-migrations\bin.

Linux: /opt/CA/CapacityCommandCenter<version_number>/ccc-migrations/bin

Open the log file in a text editor. If the log file does not contain any error, the upgrade completed successfully.

Verify that the deployment was successful:

1. Connect to the Data Manager and pull your required data.
2. After successful staging, start the migration.
3. Check the migration status. The migration tables should get populated with the data.
4. After completing the migration, run the DM group.
5. Once the group connects to CCC, run the rollup.
6. After completion of the rollup, connect to the database to check the values of the REGRESSION_VALUES table:
   1. Run the following query: SELECT * FROM REGRESSION_VALUES
   2. Depending on your version of CCC, the REGRESSION_VALUES table will now have the following additional fields:
      • If your are running CCC 2.9: instance_name, r_squared
      • If you are running CCC 2.9.2 instance_name