CA-ENF DB: Database Insert error:72 reason:0
search cancel

CA-ENF DB: Database Insert error:72 reason:0

book

Article ID: 113442

calendar_today

Updated On:

Products

COMMON SERVICES FOR Z/OS 90S SERVICES Common Services Datacom/AD

Issue/Introduction

After switching to a backup CPU, I received the following errors. Even recycling ENF STC does not help to resolve this problem.  

hh.mm.sec STCnnnnn *CAS9359E - Unrecoverable Database subtask failure detected. Recycle ENF 
hh.mm.sec STCnnnnn *CAS9208E - CA-ENF DB: Database Insert error:72 reason:0 
hh.mm.sec STCnnnnn *CAS9303E - Event JOBFAIL no longer recorded due to DB error 0012 

Could you please tell me what is causing the issue? 

Why do I get the message: CA-ENF DB: Database Insert error:72 reason:0 
after switching to a backup CPU? 
 

Environment

CA Common Services 15.0
ENF component set to record events
Datacom/AD 
- z/OS supported releases - 

Cause

Probable cause is the Datacom/AD Log Recovery setting, LOGRCV, is set to LOGRCV=NO

Found in datacom.CUSMAC(AXDATAIN)

LOGRCV=NO allows LXX/RXX files to be used for backup and recovery. 

However, the ENF database is self sustaining, contains only transient data, and no backup is necessary. 

Resolution

Review the ENF joblog look for the LOGRCV setting 

Assuming it is NO:

1. Edit your DATACOM.CUSMAC(AXDATIN1) member and change the current value of LOGRCV from LOGRCV=NO to LOGRCV=NEVER.  

             What NEVER does is to allow the LOGFILE (LXX) to be reused and will not write anything to a Recovery File (RXX). 

2. Shutdown ENF and run DATACOM.Rxx.INSTJCL(ADxxLXXI) to reinitialize the log file to use the LOGRCV value.
 
3. Restart ENF. 


 












 

Additional Information

Refer to the r15.1 Datacom/AD documentation and review the Backup and Recovery Considerations found under the Datacom/AD Environment Maintenance.