Скачать с ютуб OEM Blackout Options - Different Ways Including Command Line Options to Start and Stop a Blackout в хорошем качестве

OEM Blackout Options - Different Ways Including Command Line Options to Start and Stop a Blackout

A blackout is an arrangement in the OEM during which OEM does not sent alerts or notifications on covered targets for a specific period of time or indefinitely as defined. It is usually started on one or a group of targets during maintenance or planned downtime. however during the blackout, OEM continues to collect metric data and certain jobs on some targets. it only stops sending alerts and notification. I am going to show 4 different methods of starting and stopping a blackout and based on the scenario the dba can chose the best option to start the blackout. Option-1: First option which is the traditional way of starting a blackout from the oem console and most of us already know...this is useful when we want to include one or more targets from one or more servers Option-2: Second option, right click on the target, go to Control menu and select Blackout...this is useful when you want to include only one particular target in the blackout...this is the quickest way to issue a blackout on a particular target from OEM console Option-3: Third option, is to start the blackout using command prompt from OMS server...this is the least used option but useful when you are already logged into the oms server and working with the oms. to go with this option, you must know a super user password like SYSMAN and THE name of the target or targets on which you are starting the blackout. emcli login -username=sysman emcli create_blackout -name=test_bo3 -add_targets=catdb.manash.hom:oracle_database -schedule="duration::1" -reason="test reason" emcli get_blackout_details -name=test_bo3 emcli stop_blackout -name=test_bo3 emcli get_blackout_details -name=test_bo3 Option-4: The fourth option which is also using command prompt and it is very useful when you are already in a target server, say you are working on a database maintenance that needs bouncing the instance or restarting a listener or bouncing the OEM agent itself. This is the quickest as you don't have to login to OEM console and instead issue the start and stop commands from the target DB server itself. emctl start blackout test_bo4 -nodelevel -d 00:10 emctl status blackout test_bo4 emctl stop blackout test_bo4 emctl status blackout test_bo4