In Grid Control, the Blackout Status is Frozen at 'Modify Pending" After Attempting to Remove it. (Doc ID 397359.1)

Last updated on SEPTEMBER 28, 2015

Applies to:

Enterprise Manager Base Platform - Version 10.1.0.1.0 to 11.1.0.1 [Release 10.1 to 11.1]
Information in this document applies to any platform.
***Checked for relevance on 24-April-2013***

Symptoms

A blackout had been setup on several nodes to reduce the load on the OMS.
Need to remove the blackout as the OMS server has been upgraded for improved performance.
After removing a couple of targets from the blackout the status of the blackout is 'Modify Pending'.

Steps followed:
---------------
1) Login to Grid control console, trying to Edit blackout returns this error message: "Modify not supported at this status" 

2) Checking the blackout status from the repository table MGMT_BLACKOUTS.

SQL> Select * from MGMT_BLACKOUTS where BLACKOUT_NAME like '<Blackout-Name>';

 For example :

SQL> select * from MGMT_BLACKOUTS where BLACKOUT_NAME like '%Performance_Issues%'; 
BLACKOUT_GUID BLACKOUT_NAME REASON_ID 
-------------------------------- ---------------------------------------------
BLACKOUT_DESC 
------------------------------------------------------------------------------
BLACKOUT_STATUS JOB_FLAG CREATED_BY 
--------------- ---------- ------------------------------ 
CREATED_THRU 
------------------------------------------------------------------------------
LAST_UPDATED_BY LAST_UPDATED_TI LAST_START_TIME LAST_END_TIME SCHEDULED_TIME 
START_JOB_ID 
------------------------------ --------------- --------------- ---------------
END_JOB_ID OCCURRENCE_NUMBER 
-------------------------------- ----------------- 
887F2AC4D14DF3521425A36D4B363132 Performance_Issues 4 
Targets blacked out due to performance issues. 
13 0 SYSMAN 

SYSMAN 05-OCT-06 05-OCT-06 11-SEP-06 1D2F4BDCB31812FDE0440003BA0B1CCD
1

BLACKOUT_STATUS appears 13 means 'Modify Pending' as seen from console

3) Checking blackout status at command prompt in the target agent :

Prompt> ./emctl status blackout

Blackoutname = Performance_Issues
Targets = (xxxxxxxxxxxxxxxxxxx)
Time = ({2006-9-11|15:30:33,|} )
Expired = False

'Emctl status blackout' shows the blackout as still enabled ; EXPIRED=False [the target still under blackout although its status is Modify pending]

4) check Blackouts.xml

- <Blackouts>
- <Blackout NAME="Performance_Issues" GUID="887F2AC4D14DF3521425A36D4B363132"
CREATED_USING="CONSOLE" NODE_LEVEL="FALSE">
<Schedule START_DATE="2006-9-11" START_TIME="15:30:33" />
<Target NAME="xxxxxxxxxxxxxxxxxxxxx" TYPE="host" />
<Target NAME="xxxxxxxxxxxxxxxx" TYPE="oracle_database" />
</Blackout>
</Blackouts>

Blackout details are present in the Blackouts.xml  but there is no end duration.

4) Stopping blackout from the repository:

SQL> exec MGMT_BLACKOUT.stop_blackout('887F2AC4D14DF3521425A36D4B363132',null)

BEGIN MGMT_BLACKOUT.stop_blackout('887F2AC4D14DF3521425A36D4B363132',null); END; 

ERROR at line 1: 
ORA-20705: The last set of edits to the blackout have not yet been committed 
ORA-06512: at "SYSMAN.MGMT_BLACKOUT_ENGINE", line 2912 
ORA-06512: at "SYSMAN.MGMT_BLACKOUT", line 74 
ORA-06512: at line 1 

Cannot stop the blackout, the error is: "The last set of edits to the blackout have not yet been committed "

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms