Blackouts allow you to suspend collection of metrics on a target when performing scheduled maintenance on the target. Blacking out a target suspends monitoring on the target for the duration of the blackout. Blackouts are named entities that mainly consist of a list of targets that participate in the blackout and the schedule that defines when the blackout is in effect. Blackouts may be defined on a single target or on aggregate targets such as groups, hosts, systems, or web applications.
The Blackouts Best Effort feature allows you to create blackouts on aggregate targets, such as groups or systems, for which you do not have OPERATOR (or Higher) privileges on all members of the aggregate target.
Here, an Enterprise Manager administrator hasOPERATOR privilege on an aggregate target but do not have OPERATOR privilege on its member/associated targets. You want to create a Full Blackout on this aggregate target. When defining the blackout, you are allowed to select any member target, even those member targets for which you have no OPERATOR privileges. When the blackout actually starts, Enterprise Manager checks privileges on each member target and only blackout those on which you have OPERATOR( or Higher) privileges. This automated privilege check and target blackout selection is Enterprise Manager's "best effort" at blacking out the aggregate target.
The Blackout Best Effort functionality is targeted towards the creation of blackouts on targets of any aggregate type, such as Group, Hosts, Application Servers, Web Applications, Redundancy Groups, or Systems.
All targets the blackout creator has OPERATOR (or higher) privilege on will be displayed in the first step of Create/Edit Blackout Wizard. Once the blackout creator selects an aggregate type of target to be included in the Blackout Definition, this Blackout is "Full Blackout" (in Step 2), by default. The creator has the option of choosing the Blackout to run on “All Current” or “Selected” Targets, by selecting the appropriate values from the List box. Only when the "Full Blackout" option is chosen, will Blackout Best Effort affect targets for which the creator does not have OPERATOR (or higher) privileges.
Consider 3 targets T1,T2 and T3 (all databases). A Group G1 contains all these 3 targets.
User U1 has OPERATOR privilege on T1,T2 and G1. User U1 has VIEW privilege on T3.
User U1 creates a scheduled full blackout on target G1. Scheduled implies that the blackout will start at a later point in time.
At the time of blackout creation, the tip text Needs Operator privilege, see Tip below the table would be shown beside target T3.
When this blackout starts, if by that time User U1 has been granted OPERATOR privileges on target T3, then target T3 would also be under blackout. Otherwise only targets T1, T2 and G1 will be under blackout.
Tip text appears at the bottom of screen to explain the meaning of "Needs
Operator privilege".
"Needs Operator privilege" means that the administrator who submitted
the blackout does not have Operator privilege on the target so the target will
not be blacked out. If this administrator is granted the privilege before the
blackout starts, the target will be blacked out."
Enterprise Manager Information Roadmap
Copyright © 1996, 2007, Oracle. All rights reserved.