Notifications

118 views

Description

Rollback attempt failed due to existence of an already active rollback context, sys_rollback_context in state = 'in_progress'. There are no identifiable (limited log availability) signs that the user force cancelled or that the system was power-cycled during this time.

Steps to Reproduce

Not applicable.

Workaround

This problem has been fixed. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.
 
The same script as the one mentioned in the Known Error Article KB0714289 can be used to fix the issue. You must confirm first that the rollback context is not being used. For this, you can 
check whether there is any active rollback contexts in the [sys_trigger] table using the rollback context id mentioned in the message from the logs. 

Related Problem: PRB1238920

Seen In

SR - IRM - Audit Management - New York 2019 Q3
SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - GRC Workbench - New York 2019 Q3
SR - IRM - NIST CSF - New York 2019 Q3
SR - IRM - NIST RMF - New York 2019 Q3
SR - IRM - PA Premium Integration - New York 2019 Q3
SR - IRM - Policy and Compliance - Madrid 2019 Q2
SR - IRM - Risk Management - New York 2019 Q3
SR - ITOM - Discovery and Service Mapping - v1.0.35
SR - PAR - Performance Analytics Content Pack for Guided Tours - v1.0.1
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - VR - Qualys - New York 2019 Q3
SR - VR - Vulnerability Response - New York 2019 Q3
SR - VR - Vulnerability Response PA Content - Madrid 2019 Q2

Fixed In

New York

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2019-11-11 11:50:52
Published:2019-10-21