PWP Log Rotation fails - U00020292 RunID '207688001' could not be found.

book

Article ID: 241829

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic One Automation

Issue/Introduction

When using "Initiate log rotation" on PWP in client 0 Administration perspective, the log does not rollover and an error is shown in the WP log:

WP log error shows:
36 - 20220210/180418.473 - U00015006 System forced memory trace dump.
36 - 20220210/180418.478 - U00015006 System forced memory trace dump.
36 - 20220210/180418.478 - U00003631 Dump caused by:
36 - 20220210/180418.478 - U00020292 RunID '207692001' could not be found.
36 - 20220210/180418.478 - U00011801 Error in Server routine 'UCDS_R  ', Server: 'AUTOMIC#WP024' AE system: 'AUTOMIC'.

There is no impact to the system.

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Resolution

Workaround:

Initiate log rotation on non-PWP WP
Switch non-PWP WP to PWP
Initial log rotation on earlier PWP

To fully resolve:

Cycle all the WPs (one at a time is fine) to try to get rid of the old RunID out of rotation.
Look at Archive/reorg/unload - the amount of days kept is how long it will take for the log rotation to work again.