Closed as fixed if next.
Currently, the prune command is designed to run on all daos-enabled databases on the server and not specific databases. The functionality does not exist to run the prune command on just one database. There are situations where running the prune on just one database may be useful or necessary. For example, if the NLO retention interval is set to a high value such as 1 or 2 years and a database is deleted, the NLOs referenced by this database will remain on the server until the 1 or 2 years have elapsed even if they are no longer referenced by any other databases. The only way to purge these NLOs immediately would be to run the Prune 0 command but this would affect all databases on the server. It would be useful in this type of situation to have the ability to run the Prune command on just this one database. Otherwise, these lingering NLOs will begin to drastically impact server disk space.
Manually search for the NLOs and delete them
This APAR is closed as FIN. We have deferred the fix to a future release.
This APAR is associated with SPR# MKHS92HSTZ. This APAR is closed as FIN. We have deferred the fix to a future release.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Applicable component levels