Before any planned outage on the target database or hot , we need to create blackout for that target, to avoid incident alerts. Blackouts allow Enterprise Manager Administrators to suspend all data collection activity.

 

ORACLE DATABASE - > MONITORING - > BLACKOUTS

 

Select the databases or services  which want to include in blackout.

 

 

You can select whether we need to initiate the blackout immediately or schedule it for future.

 

 

 

 

 

Removing BLACKOUT:

Once target maintenance is done, we need to remove the targets from Blackout, to enable the incident and notification services.

ENTERPRISE - > MONITORING - > BLACKOUTS

 

 

CLOUD


Related Topics

Generate custom report from OEM cloud control
Install oracle enterprise manager cloud control 12c
Change dbsnmp password for target db in oem 12c
Deinstall Management Agents Oracle 12c cloud control
Upgrade database using OEM 12C cloud control
Add database as target oracle 12c cloud control
Apply database patch from OEM Cloud control
Blackout targets in OEM 12c cloud control
EMCLI command - OEM 12C
How to change sysman password for oracle 12c cloud control

You May Also Like

how to send mail using utl_mail in oracle 11g
Shell script to monitor lag in standby datbase using dgmgrl
How to generate ADDM report
WHAT IS SQL PROFILE IN ORACLE
SETUP ORACLE 18C DATABASE - STEP BY STEP
Change dbsnmp password for target db in oem 12c
How to use expdp to export data from physical standby database
LOG_CHECKPOINTS_TO_ALERT parameter in oracle
Rollback database patch in oracle 12c
How to move controlfile to a new location in oracle

From This Website

Open wallet automatically after starting the database
resumable_timeout parameter in oracle database
OUTBOUND_DBLINK_PROTOCOLS in oracle 12.2
Display sql_id of the sql, using set feedback in oracle 18C - New feature
How to move spfile from file system to ASM in RAC
How to get the execution plan for a SQL between two AWR snapshots
TNS-12542: TNS:address already in use
Exception in thread -main" java.lang.OutOfMemoryError: GC overhead limit exceeded with bsu.sh
How to find execution history of an sql_id
Shell script to report failed login attempt in oracle