PFR0067E - ALLOCATE FAILED FOR ARCHIVE LOG DATASET

Document ID : KB000014224
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

Log Analyzer mounting old image copies

Question:

PFR0067E - ALLOCATE FAILED FOR ARCHIVE LOG DATASET

 

This is a DB2 that is not so much in use. 

The log files are only keep a few weeks . 

In the BSDS longer. 

 

Why is Log Analyzer trying to mount old log files? 

Environment:
z/os DB2
Answer:

Without DATA CAPTURE CHANGES enabled for the SYSIBM catalog tables , 

CA Log Analyzer will need to process archive logs forward since the most 

recent image copy of the DB2 catalog tablespaces. 

If image copies are not taken regularly of your Catalog Tablespaces 

we need to go back some time. 

 

The recommendation would be to enable DATA CAPTURE CHANGES for the SYSIBM tables 

so the image copy and additional archive logs are not required. 

 

 

So this can be prevented by either taking more frequent copies of the catalog or 

setting DATA CAPTURE CHANGES. 

On lightly used system, we would recommend DCC, as the logging overhead would be negligible. 

 

There is a TEC doc explains this TEC1971745