|
|
|
During ENF operations, you may receive the following messages:
DATACOME:DB02406I - PXX END - EXTEND FAILURE DUE TO X37 ABEND DATACOME:DB01702I - DYNAMIC EXTEND OF AREA ENF00700 HAS FAILED CAS9316E - STEPTERM "Insert " failed - rc(-258) r/s(X'F5F7E2F0F6'). CAS9340I - TABLE FULL - DBID=700 INTERNAL NAME B22 . *CAS9208E - CA-ENF DB: DB Insert error SQLCODE=-258 SQLSTATE=57S06 CAS9303E - Event XXXXXXXX no longer recorded due to DB error 0008 ...
Additional similar messages can appear for errors for other events being recorded. New records are not recorded to the database during this time. However, the CA applications "listening" for these events continue to run without issue because they receive event information before any attempt is made to write the events to the database. If these applications shut down, they cannot recover events (checkpoint) from the database during the timeframe when event recording stopped.
If you experience this situation, check that an ENF ARCHIVE is being done on a regular basis. Check the ENFPARM parameter file for the ARCHIVE control option. During the ARCHIVE process, expired events are deleted from the ENF database. Events expire based on the Retention Period (RP) set for the individual events. If a retention period is not set for the individual event, ENF uses the value that is specified on the DETAIL control option in the ENFPARM parameter file.
If the ENF ARCHIVE is successfully running each day, the ENF database may be too small for the number of event records being recorded. If possible, use SELECT statements to filter events to be written. Information on the SELECT control option (and all ENF control options) can be found in the CA Common Services Reference Guide.
If you have not experienced problems with previous ARCHIVE processing and if you cannot further filter the number of events being recorded, do one of the following:
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |