PFR0067E - ALLOCATE FAILED FOR ARCHIVE LOG DATASET executing Log Analyzer
search cancel

PFR0067E - ALLOCATE FAILED FOR ARCHIVE LOG DATASET executing Log Analyzer

book

Article ID: 14224

calendar_today

Updated On:

Products

Log Analyzer for DB2 for z/OS

Issue/Introduction

Log Analyzer for Db2 for z/OS (PLA) mounting old image copies:

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?

Resolution

Without DATA CAPTURE CHANGES enabled for the SYSIBM catalog tables , 

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.