Troubleshooting - DB2 MultiNode iDataAgent

Updated

Unable to discover DB2 instances from the CommCell Console

If you are unable to discover DB2 instances from the CommCell Console and get the below error message:

Unable to execute SrvDb2Agent to populate CV tables for DB2

You need to restart the services and then try to discover the Db2 instance from the CommCell as DB2 Instances cannot be discovered from the CommCell when the services are down on the DB2 client computer.

Log Only backup is failing after a DB2 upgrade from 32-bit to 64-bit

When you upgrade from 32bit to 64bit, the log only backup will fail if you have not linked the sqllib/lib library to a correct lib64 for 64bit DB2.

Make sure to link the sqllib/lib library to a correct lib64 for 64bit DB2 when you upgrade DB2 from 32bit to 64bit.

DBMN0001: DB2 Online Backup Fails with SQL2428N error after upgrading Commvault

Issue

The DB2 online backup fails.

Symptom

The following error message is received when an online backup is performed.

SQL2428N The BACKUP did not complete because one or more of the requested log files could not be retrieved

Resolution

The DB2 Services need to be restarted to clear the API information cached by the db2logmgr process. After the restart, retry the backup.

DB20014: DB2 dir_cache parameter can cause the database access processes to hang

Issue

If you use DB2 V9.7fp10 and the directory cache (dir_cache) parameter is set to yes, which is the default, processes that access the database (for example create db, list db) can hang. The processes are waiting for the sqleDirCacheLatch latch.

The stack trace shows most of the agents are waiting for the SQLO_LT_SQLE_KRCB__sqleDirCacheLatch latch.

Resolution

Set DIR_CACHE to no ("DIR_CACHE=NO").