ILM Errors

Document ID : KB000089899
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
ILM Errors
Resolution:
Detailed Description and Symptoms

U0005333 ILM: Server processing will be halted….

….

U0005327 ILM processing is set to   I N A C T I V E!

U0005322 There is a statement showing status 'R' (unsuccessfully restarted) in the ISTMT table. 

This has to be manually checked and solved.


Investigation

The following messages appear in the PWP log file:

 

U0005333 ILM: Server processing will be halted….

….

U0005327 ILM processing is set to   I N A C T I V E!

U0005322 There is a statement showing status 'R' (unsuccessfully restarted) in the ISTMT table. 

This has to be manually checked and solved.

 

**Please NOTE - The following messages are normal for ILM in the PWP log:
….

U0005333 ILM: Server processing will be halted. Option: 'CY'

U0003352 Processing of Server 'UC4P#WP002' ought to be stopped.

U0003352 Processing of Server 'UC4P#WP003' ought to be stopped.

U0003352 Processing of Server 'UC4P#WP004' ought to be stopped.

….

 

U0003351 Processing of Server 'UC4P#WP002' has been stopped.

U0003351 Processing of Server 'UC4P#WP004' has been stopped.

U0003351 Processing of Server 'UC4P#WP003' has been stopped.

….

 U0005353 ILM: Processing after system stop was called with option 'CY' .

Solution

If an ILM error occurs it is important that it is repaired immediately!  The WPs will normally restart so the OM system will continue to run.  The real impact will likely be that ILM will remain inactive and partition switch-outs will not happen.  The System Overview can be used to view the status of ILM. The "Partition" tab contains a list of existing partitions and the displays the status of ILM (active or inactive.

Not repairing an ILM error could lead to an inconsistent database and repairing this will be much more difficult than just repairing the original cause!!

 

Please DO NOT attempt to repair the ILM error on your own. Here are the steps that should be taken:

 

1) Contact technical support for further assistance as soon as possible.

2) If possible, have your DBA check the following tables (If data is found, please forward that information to technical support):

  • The ISTMT table to see if there is any data in the table
  • The IPH table to see if there is any data in the table. 

3) The server logs (or at least the PWP log) containing the unsuccessful ILM operations.