Automation Through Shell Scripts - Oracle Enterprise Manager 12c Command-Line Interface - page 61

You must provide three values for the EM CLI create_blackout verb.
Unique name for each blackout passed as •

-name

• Targets to include in the blackout, used in

-add_targets argument
Schedule information about start and end times,input as

-schedule argument
The -reason variableis not required by EM CLI but should be included to make it easier for OEM administrators
to assess running, scheduled, and stopped blackouts. Be courteous.
The syntax to create a simple blackout is fairly straightforward:

•

> emcli create blackout -name="sample_blackout"\
-add_targets="oracla:oracle_database"\
-schedule="duration::360 ..."
-reason="Blackout demonstration using emcli"

Name Argument
You may pass anything as the name of a blackout. The blackout name is applied when you create the blackout, but
it's also used when it's time to stop and delete the blackout. It's always a good practice to use a descriptive name like
scripted_blackout_$SID or a similar, consistent naming standard. As we work through the examples, you'll begin to
see how consistency affects your solution's design.

Add Targets Argument
Targets must be identified by target name and target type. For example:

• oracla:oracle_database

• demohost:host

• lsnroracla:oracle_listener

Schedule Argument
Each schedule argument accepts two required and several optional values at the command line, similar to the
flexibility found in the console:

frequency:once

requires => duration or end_time
optional => start_time, tzinfo, tzoffset

frequency:interval

requires => duration, repeat

optional => start_time, end_time, tzinfo, tzoffset

frequency:weekly
requires => duration, days
optional => start_time, end_time, tzinfo, tzoffset
frequency:monthly
requires => duration, days
optional => start_time, end_time, tzinfo, tzoffset