[Daily one] 11gOCP 1z0-052:2013-09-21 automatic Maintenance window ................ ... B53

Please indicate the source of the transfer: http://blog.csdn.net/guoyjoe/article/details/11895359

Correct answer: D

After you create a database using DBC, three tasks are configured in the Autotask system. These tasks are shown below:

1. Collect Optimizer statistic information

2. Operation Section Consultant

3, run SQL Consultant Autotask in the Scheduler's Maintenance window. The Maintenance window is defined to be open at 22 o'clock on each weekday night and closed after 4 hours, or 2 o'clock in the morning, and in Saturday and Sunday, starting at 6 o'clock in the morning and closing 20 hours later, 2 o'clock in the morning. The scheduler is associated with another data feature, resource Manager. The Resource Manager program that is activated during the Maintenance window ensures that the total number of computer resources allocated to Autotask jobs is less than 25%, which means that running these tasks does not negatively affect other work. You can adjust the window's time range if it does not fit the needs of the database workload. If the maximum resource usage percentage is set to 25%, it can cause performance degradation in other jobs, as well as modification. The potential assumption is that Autotask runs at a certain time, and that the optimization level at which it resides does not cause problems for ordinary users ' day-to-day work.

As shown in the following illustration:

To run with any autotask, you must set the Statistics_level parameter to typical (default) or all. The easiest way to manage the scheduling of Autotask jobs is to use database control. On the Database home page, select the Server tab, and then click the Automated Maintenance Task link in the Scheduler section.

The Segment Advisor task relies on the history of object statistics that are built by running optimizer Statistics gather tasks on a day-to-day basis. By looking at this information, the Segment advisor can see not only the unused space in the table and index, but also whether the space is likely to be needed again, and if it is no longer needed, the organizational segment is suggested. The SQL Tuning Advisor relies on the AWR statistics collected by the Mmon process. These statistics include: Which statements are executed multiple times (perhaps hundreds of times per hour) which statements use a large amount of disk and memory I/O, and which statements run in time. These are high load statements that need to be adjusted for analysis.

To view and adjust the window schedule, click the Configure button.

QQ:252803295

Technical Exchange QQ Group:
Dsi&core Searchⅰ Group: 127149411 (2000 people Technical Group: not full)
Dsi&core Searchⅱ Group: 177089463 (1000 people Technical Group: not full)
Dsi&core Searchⅲ Group: 284596437 (500 people Technical Group: not full)
Dsi&core Searchⅳ Group: 192136702 (500 people Technical Group: not full)
Dsi&core Searchⅴ Group: 285030382 (500 people chat group: not full)

mail:dbathink@hotmail. com

BLOG: http://blog.csdn.net/guoyjoe

WEIBO:http://weibo.com/guoyJoe0218

itpub: http://www.itpub.net/space-uid-28460966.html

OCM: Http://education.oracle.com/education/otn/YGuo.HTM