WARNING: ==ILM-REDO-MODE== Due to a possible Server crash some ILM statements could not be processed

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

The primary Work Process reports in its log file this message during ILM Processing:

U00005323 WARNING: ==ILM-REDO-MODE== Due to a possible Server crash some ILM statements could not be processed. They will be executed now. 

In addition, in the log file following sequence is logged:

U00005305 ILM: 'ALTER TABLE RT ENABLE NOVALIDATE CONSTRAINT FK_RT_RH' 
U00029108 UCUDB: SQL_ERROR Database handles DB-HENV: 652c70 DB-HDBC: 16bad628 
U00003591 UCUDB - DB error info: OPC: 'OCIStmtExecute' Return code: 'ERROR' 
U00003592 UCUDB - Status: '' Native error: '54' Msg: 'ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired' 
U00000005 LOCK 
U00000005 LOCK 
U00005334 ILM: Server processing will be continued. 
... 
20190520/160857.137 - U00005305 ILM: 'ALTER TABLE RT ENABLE NOVALIDATE CONSTRAINT FK_RT_RH' 
20190520/160857.169 - U00005305 ILM: 'ALTER TABLE ABLOB ENABLE NOVALIDATE CONSTRAINT FK_ABLOB_AH'

The Oracle command select * from ISTMT does not return any lines

Environment

Release:
Component: AAUTEN

Cause

The problem is that ILM tried to acquire an exclusive lock on a table. This acquisition failed the first time and was successful the second time. (See the two alter commands for the object TABLE RT ENABLE NOVALIDATE CONSTRAINT FK_RT_RH).

.

Resolution

Each time this kind of table lock conflict occurs, a U00005323 message will reported in the log. 

However,  ILM is working correctly. No action are required in this case.


IMPORTANT: 
Please note that this explanation is exclusively applicable to this particular context where tablelocks took place; 
But, be aware that U00005323 messages can also be due to other issues with ILM. That is why we advise to always reported and have support analyzed.