My problem is one of disk space the location designated by the LOGARCHMETH1 paremeter is filling up.
The database itself is in a HADR pair with another database (at the same level and license).
What is the method employed by other users of DB2 to manage the archive logs.
I have tried using the "db2 prune prior to " command but this seemingly does nothing.
Another useful bit of information is that LOGRETAIN and USEREXIT are both set to off.
[db2inst1@centws01 NODE0000]$ db2 get db cfg | grep LOGRETAIN
Log retain for recovery enabled (LOGRETAIN) = OFF
[db2inst1@centws01 NODE0000]$ db2 get db cfg | grep USER
User exit for logging enabled (USEREXIT) = OFF
If you set the auto_del_rec_obj database configuration parameter to ON, calling PRUNE HISTORY with the AND DELETE parameter will also physically delete backup images and load copy images if their history file entry is pruned
The current HADR systems I support archive the logs directly to TSM. We have configured TSM so we can access the archived logs / backups from both sides of the HADR pair. After you archive logs are you backing them up to another location for recovery purposes? As I am sure you now you should not delete archived logs until you have either backed them up to another location or are 100% sure you will never need them for recovery.