Database performance considerations when upgrading from WSRR V8.5.0 to V8.5.5

For improved database performance when upgrading from WSRR V8.5.0 to V8.5.5, consider making the following changes to your system, logging, or database parameters.

DB2 for Linux, UNIX, and Windows

Increase the values of the LOGFILSIZ and LOGBUFSZ parameters as follows:

Set LOGFILSIZ to 7500.
Set LOGBUFSZ to 8192.

DB2 for z/OS

Changes have been made to the DB2® for z/OS® database configuration in WSRR V8.5.5 to substantially improve the performance profile when multiple concurrent WSRR operations are running on a DB2 for z/OS system. To benefit from these changes:

Install WSRR V8.5.5 on the target system and then perform a migration from your WSRR V8.5.0 source system.
Apply APAR PI30406 to the DB2 for z/OS system to prevent database deadlocks for multiple concurrent users.
For optimal WSRR operation in concurrent scenarios, increase the values for the NUMLKTS and NUMLKUS system parameters:
- Set NUMLKTS to 15000.
- Set NUMLKUS to 25000.
If these values exceed your organizational limits, increase each value to the maximum number permitted by your organizational policy.

Oracle

Increase the total log file capacity to at least 750 MB, and increase the log buffer size to 32 MB.

SQL Server

If the database log file is smaller than 1 GB, consider increasing the log file size to 1 GB.

Changes have been made to the SQL Server database configuration in WSRR V8.5.5 to substantially improve the performance profile when multiple concurrent WSRR operations are running on a SQL Server system. To benefit from these changes, complete the following steps:

Shut down WSRR.
Alter the main WSRR database to set ALLOW_SNAPSHOT_ISOLATION and READ_COMMITTED_SNAPSHOT to ON.
Run the following command on the main WSRR database, replacing __DBSCHEMA__ with the relevant schema value:
INSERT INTO __DBSCHEMA__.MOD_LOCK (ID,MLOCK) VALUES (2,0);
Run the modifySIBEngines.py script, which is located in the WAS_HOME/WSRR/install/jython directory, to enable short duration locking on the WSRR SIB tables:
wsadmin.sh -user user_name -password password -f WAS_HOME/WSRR/install/jython/modifySIBEngines.py -lockSetting true

wsadmin.bat -user user_name -password password -f WAS_HOME\WSRR\install\jython\modifySIBEngines.py -lockSetting true

Important: Ensure that you complete all of these steps. If the database changes are made without altering SIB behavior, it will impair the stability of the WSRR system.