IBM Platform Symphony 6.1.0.1 Fix Patch #229536

Readme File

 

Abstract

 

The Symphony purger service encounters a deadlock error thrown by the SQL Server database, which leads to a large size of the RESOURCE_METRICS table.

 

Description

·When the RESOURCE_METRICS table has too many records (that is, 20,000,000) to be deleted, the purger service requires a lot of time to perform the operation on the SQL Server database.

·At the same time, if the Symphony plc service inserts a large number of records into the RESOURCE_METRICS table, the SQL Server database might throw a deadlock error, which causes the purger service to fail to delete records.

· If the purger service encounters the deadlock error every time, the size of the RESOURCE_METRICS table becomes larger and larger.

 This fix patch applies only to the following platform:

·   Windows 64-bit

 

Readme file for: IBM® Platform Symphony

Product/Component Release: 6.1.0.1

Update Name: Fix pack

Fix ID: sym-6.1.0.1-build229536-mumss

Publication date: 19^th March 2014

Last modified date: 19^th March 2014

 

Contents:

 

1. List of fixes

2. Download location

3. Products or components affected

4. System requirements

5. Installation and configuration

6. List of files

7. Copyright and trademark information

 

1.    List of fixes

 

SUP_BY_SYM#228340

 

2.    Download location

 

Download fix #229536 from the following location:

http://www.ibm.com/eserver/support/fixes/

 

3.    Products or components affected

 

Product/Component Name:

Platform Symphony/purger

 

4.    System requirements

 

SQL Server 2005

 

5.    Installation and configuration

 

5.1  Before installation

 

       1. Stop the running services

      

       Log on to the master host as the cluster administrator and run:

       > egosh service stop purger plc

 

       2. Back up the file

 

       Log on to each management host and back up the following binary file that will be replaced by this patch:

       > EGO_TOP\perf\1.2.7\lib\perf_purger.jar

     

          Note:

·  Do not put the backup binary file under EGO_TOP\perf\1.2.7\lib\ because it will cause unexpected behavior.

·  EGO_TOP represents the Symphony installation directory

 

5.2    Installation steps

      

       1. Apply the fix patch.

      

       Log on to each management host and replace the old binary perf_purger.jar file with the downloaded one in the following directory:

       > EGO_TOP\perf\1.2.7\lib\perf_purger.jar

 

       Note: EGO_TOP represents the Symphony installation directory

 

       2. Update the database schema in the SQL Server.

 

       > Run the script "update_ego_RESOURCE_METRICS_#228340.sql" to update the database schema:

       > SQL server command: osql -U user_name -P password -d db_name -i update_script

      

       Where:

·   user_name is the user name on the database server.

·   password is the password for this user name on the database server.

·   db_name is the reporting database name.

·   update_script is the name of the update script.

 

       Note:

·   For information about how to update an SQL Server database, refer to the chapter "Update a SQL Server database" in the Symphony Knowledge Center

·   If there are a large number of records in the RESOURCE_METRICS table, the update will take a long time.

 

       3. Configure the batch size for the purger service.

     

· Log on to the master host, and configure the batch size in the following directory:

 

SYM_SHARE_DIR\perf\conf\perf.conf

 

Note: SYM_SHARE_DIR represents the Symphony installation share directory.

 

· The configuration example in perf.conf:

  

 PURGER_BATCH_SIZE=5000

 

Note:

· The value of PURGER_BATCH_SIZE is the maximum number of records that can be deleted in one batch operation.

· If there are "N" records, and "N" is an integer multiple of PURGER_BATCH_SIZE, N/PURGER_BATCH_SIZE batch operations are required; otherwise, N/PURGER_BATCH_SIZE + 1 batch operations are required.

 

5.3    After installation

      

       1. Start the services.

      

       Log on to the master host as the cluster administrator and run:

       > egosh service start purger plc

 

5.4    Uninstalling

 

       1. Stop the running services.

      

       Log on to the master host as the cluster administrator and run:

       > egosh service stop purger plc

 

       2. Restore the backup file

 

       Log on to each management host, and restore the backup file for the following binary file:

       > EGO_TOP\perf\1.2.7\lib\perf_purger.jar

      

       Note: EGO_TOP represents the Symphony installation directory.

     

3. Rollback the database schema in the SQL server

 

       > Run the script "rollback_ego_RESOURCE_METRICS_#228340.sql" to rollback the database schema:

       > SQL server command: osql -U user_name -P password -d db_name -i rollbak_script

      

       Where:

·   user_name is the user name on the database server

·   password is the password for this user name on the database server

·  db_name is the reporting database name

·   rollback_script is the name of the rollback script

 

       Note:

·  For information about how to update an SQL Server database, refer to the chapter "Update a SQL Server database" in the Symphony Knowledge Center

·   If there are a large number of records in the RESOURCE_METRICS table, the rollback will take a long time.

 

6.    List of files

 

perf_purger.jar

update_ego_RESOURCE_METRICS_228340.sql

rollback_ego_RESOURCE_METRICS_228340.sql

 

7.    Copyright and trademark information

 

© Copyright IBM Corporation 2014

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM®, the IBM logo and ibm.com® are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.