SQL2161N A damaged recovery history file could not be fixed.

The “SQL2161N A damaged recovery history file could not be fixed. The specified action failed” error message , can cause some DBA panic, but can be fixed . Recently I executed the following command db2 PRUNE HISTORY 20120701 --received this error message SQL2161N A damaged recovery history file could not be fixed. The specified action failed. Often, the db2rhist.asc file is damaged when the file system becomes full OR when the file size limit has been reached. Checks I made: 1) db2 prune history 2) db2 list history SQL2161N– (same error as above) I fixed by : a) Removed the... Read more →

DB2 - SQL1762N Unable to connect to database because there is not enough

Question : In the daily check of the db2diag.log files the following error message appeared. How do I fix? SQL1762N Unable to connect to database because there is not enough space to allocate active log files. Answer: Possible Reasons include : 1) Could be space restriction on the drive . Hint: Check for DIA8312C Disk was full. 2) Log archiving method is not working as expected 3) Userexit is not working as expected How to Fix - Depending on which reason 1) Free up space on drive 2) Fix userexit and make sure it’s working correctly. 3) Make sure log... Read more →