Restarting Purging Service if stopped and not scheduled

book

Article ID: 224460

calendar_today

Updated On:

Products

CA Release Automation - DataManagement Server (Nolio) CA Release Automation Connector

Issue/Introduction

It is noticed that sometime due to errors mentioned below, the purging service stopped with exception and the offline process will not be processed for reporting.

"ORA-30036: unable to extend segment by 8mb undo tablespace 'UNDOTBS1' "

Cause

There can be numerous reason or error which can cause stopping of purging service with exceptions.

Environment

Release : 6.6, 6.x

Component : CA RELEASE AUTOMATION CORE

Resolution

Note:

  • No performance impact on NAC server with below operations as we are just checking status of Purging Service and starting it in case if stopped.
  • Modify the URL noliocenter:type=info to replace NAC-IP with actual IP/HOSTNAME in respective environment and port 20203, if JMX in environment is not running on default port.

 

The alternative approach to restore purging service without restarting the NAC service is mentioned below.

1: Check the status of purging service by invoking action getPurgeOldExecutionsJobStatus from JMX noliocenter:type=info. The result of invocation will be as below

2: If the invocation result is "Result: Success" no need to perform below steps. If the invocation result is "Result: Stopped/Failed" perform steps mentioned below

3: Invoke operation recreatePurgeOldScheduledExecutor from JMX noliocenter:type=info with below parameters.

4: Check the status of purging service by invoking action getPurgeOldExecutionsJobStatus from JMX noliocenter:type=info. The result of invocation will be as below

Attachments