Problem(Abstract)
A very large db2rhist.asc file can cause performance degradation to DML that modifies tables.
Symptom
Poor performance during inserts, updates and deletes. The application snapshots will show applications in COMMIT-ACTIVE longer than it should
Cause
During a log archive, DB2 writes to the db2rhist.asc file. As the file gets larger, the writes takes longer than usual. During this time any inserts, updates and deletes attempting to COMMIT during a log switch have to wait for the db2rhist.asc update to complete. This can momentarily 'freeze' the system for a few seconds.
This problem usually affects customers who use flash copy to backup the database. As DB2 backup is not invoked directly, the db2rhist.asc does not get pruned despite the RETENTION setting.
Diagnosing the problem
Disable HADR for isolation, as it may cause COMMIT-ACTIVE as well
Resolving the problem
Reduce the size of the db2rhist.asc via the prune force command periodically
http://www-01.ibm.com/support/docview.wss?uid=swg21575692
http://dbaspot.com/ibm-db2/195591-commit-active-problem-solved-db2rhist-asc.html
'Db2 > Db2 troubleshooting' 카테고리의 다른 글
| LIC1449N error applying DB2 Enterprise Server Edition license on a 32-bit Linux system (0) | 2013.11.07 |
|---|---|
| History File (0) | 2013.08.08 |
| Collecting data for index corruption and/or index or data inconsistency issues (0) | 2013.05.31 |
| DB2 database corruption causing Tivoli Storage Manager crash (0) | 2013.05.28 |
| SQL30082N Security processing failed with reason “26″ (0) | 2013.05.13 |