Question & Answer
Question
Db2 database manager can be configured by to automatically prune the recovery history file and also delete the corresponding physical log files, backup images, and load copy images after each full database backup, and some recovery objects may be unexpectedly remained sometimes after full database backup.
Are there any workaround to prune the unexpectedly remained recovery objects which are to be pruned by automated deletion of recovery objects feature ?
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"recovery","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Product Synonym
Db2; DB2 LUW
Was this topic helpful?
Document Information
Modified date:
30 April 2025
UID
ibm10716439