Search dba-db2.com
*Use the Comments section for questions
Recent Posts
SQL2161N A damaged recovery history file could not be fixed.
27 September,2012 by Tom Collins
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 recovery history file
b)Resubmitted command and new file was created
c)Set up monitoring to ensure a warning arises before system becomes full
Related Posts
Verify your Comment
Previewing your Comment
This is only a preview. Your comment has not yet been posted.
As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.
Having trouble reading this image? View an alternate.
dba-db2.com | DB2 Performance Tuning | DBA DB2:Everything | FAQ | Contact | Copyright
Posted by: |