CA Log Analyzer returns messages LAE0320I LAE0311W LAE0071W related to compression dictionary after ALTER COMPRESS YES
Article ID: 104105
Updated On:
Products
24X7 High-Availability Manager for DB2 for z/OS
Batch Processor
Compile QQF
Data Compressor for DB2 for z/OS
CA Unicenter NSM
RC/Update for DB2 for z/OS
DB2 TOOLS- DATABASE MISC
Issue/Introduction
After a tablespace is ALTERed to specify COMPRESS YES, a Production
CA Log Analyzer for DB2 for z/OS (PLA) job fails with the following messages:
LAE0320 Unable to establish the dictionary creation point.
Reverting to KEEPDICTIONARY NO processing
Database : dbname
Tablespace: tsname
Instance : 0001
LAE0311W A problem has occured while reading the compression dictionary
from a VSAM dataset. Return Code: 0000, Reason Code: GETE.
LAE0071W Unable to build expansion dictionary for dbname.tsname
instance 0001.
from DB2 VSAM file. Reason = 0004.
LAE0071W Unable to build expansion dictionary for dbname.tsname
instance 0001.
from Image Copy Reason = 0028.
LAE0098W 8 update(s) were discarded during DML Activity reporting. Log records
are discarded whenever incomplete row images or data formatting errors prevent
log analyzer from determining if the log record meets your selection criteria.
A log record may also be discarded if log analyzer is unable to format the column
data needed to build a LOAD output format record or REDO/UNDO SQL statement.
CA Log Analyzer for DB2 for z/OS (PLA) job fails with the following messages:
LAE0320 Unable to establish the dictionary creation point.
Reverting to KEEPDICTIONARY NO processing
Database : dbname
Tablespace: tsname
Instance : 0001
LAE0311W A problem has occured while reading the compression dictionary
from a VSAM dataset. Return Code: 0000, Reason Code: GETE.
LAE0071W Unable to build expansion dictionary for dbname.tsname
instance 0001.
from DB2 VSAM file. Reason = 0004.
LAE0071W Unable to build expansion dictionary for dbname.tsname
instance 0001.
from Image Copy Reason = 0028.
LAE0098W 8 update(s) were discarded during DML Activity reporting. Log records
are discarded whenever incomplete row images or data formatting errors prevent
log analyzer from determining if the log record meets your selection criteria.
A log record may also be discarded if log analyzer is unable to format the column
data needed to build a LOAD output format record or REDO/UNDO SQL statement.
Environment
Release:
Component: PLA
Component: PLA
Resolution
The following informational message is related to a non-partitioned tablespace that has
a dynamic compression dictionary built on insert where the dictionary pages are not
in the first VSAM dataset (A001):
LAE0320I Unable to establish the dictionary creation point.
Reverting to KEEPDICTIONARY NO processing
Database : dbname
Tablespace: tsname
Instance : 0001
The following is an example of the DB2 MSTR address space messages when the
dynamic compression dictionary is built after an ALTER COMPRESS YES is performed
and a utility has not be run to build the dictionary:
04.43.28 STC02582 DSNU231I + DSNUZLCR - DICTIONARY WITH 4096 ENTRIES
HAS BEEN SUCCESSFULLY BUILT FROM 782 ROWS FOR TABLE SPACE
The following are circumvention methods that have been determined for this problem:
1. Create a new image copy following the dynamic compress dictionary build
which would contain the dictionary pages. CA Log Analyzer should utilize this
recent image copy to obtain the dictionary pages. Be advised that the
LAE0320I / LAE0311W warning messages will still occur related to the VSAM
dataset but the image copy should be used to obtain the compression dictionary pages.
The job will likely end with a COND CODE 4 if this will impact your job or production scheduler.
2. Execute a reorg process with KEEPDICTIONARY specified which will place the
compression dictionary pages in the standard position in the first VSAM dataset (A001).
CA Log Analyzer should be able to resolve the compression dictionary from the VSAM dataset
as normal.
a dynamic compression dictionary built on insert where the dictionary pages are not
in the first VSAM dataset (A001):
LAE0320I Unable to establish the dictionary creation point.
Reverting to KEEPDICTIONARY NO processing
Database : dbname
Tablespace: tsname
Instance : 0001
The following is an example of the DB2 MSTR address space messages when the
dynamic compression dictionary is built after an ALTER COMPRESS YES is performed
and a utility has not be run to build the dictionary:
04.43.28 STC02582 DSNU231I + DSNUZLCR - DICTIONARY WITH 4096 ENTRIES
HAS BEEN SUCCESSFULLY BUILT FROM 782 ROWS FOR TABLE SPACE
The following are circumvention methods that have been determined for this problem:
1. Create a new image copy following the dynamic compress dictionary build
which would contain the dictionary pages. CA Log Analyzer should utilize this
recent image copy to obtain the dictionary pages. Be advised that the
LAE0320I / LAE0311W warning messages will still occur related to the VSAM
dataset but the image copy should be used to obtain the compression dictionary pages.
The job will likely end with a COND CODE 4 if this will impact your job or production scheduler.
2. Execute a reorg process with KEEPDICTIONARY specified which will place the
compression dictionary pages in the standard position in the first VSAM dataset (A001).
CA Log Analyzer should be able to resolve the compression dictionary from the VSAM dataset
as normal.
Feedback
Yes
No
Powered by
