The Update Guide To 1Z0-053 Practice Question

None

AutoTask Overview
Oracle 11g added a new component to the Oracle automated task infrastructure, that began in Oracle 10g, called AutoTask. AutoTask provides a central component that is responsible for management of scheduled maintenance tasks.
AutoTask Architecture
AutoTask builds on much of the existing architecture of Oracle 10g. The AutoTask architecture consists of the following components:
AutoTask Background Process (ABP) - APB is spawned by MMON and is responsible for managing the AutoTask features. It coordinates the AutoTask clients and the scheduler. It also maintains AutoTask related history that can be seen in the DBA_AUTOTASK_TASK view.
AutoTask Clients - Automated maintenance tasks that are scheduled by AutoTask. Oracle 11g includes clients for statistics gathering, the Segment Advisor, and the Automatic SQL Tuning Advisor.
The AutoTask Maintenance Windows - Individual maintenance windows exist for different days of the week.
These windows can be modified as required.
Resource Manager - A resource plan is enabled that is designed to limit the amount of resources that the AutoTask tasks can consume. This resource plan can be modified as required.
OEM - You can manage the start time and duration of the various AutoTask maintenance windows and add or remove maintenance tasks with OEM. You can also use OEM to enable or disable maintenance tasks.
The Scheduler - AutoTask operations rely heavily on the Scheduler. The AutoTask architecture uses scheduler windows and the scheduler infrastructure to execute AutoTask tasks.

From the training book:
“Full backup: Makes a copy of each data block that contains data and that is within the files being backed up.”
“A full backup contains all used data file blocks.”
“A full backup is different from a whole database backup.”
Conclusion – it means that not all data files are backed up when you do full backup.

None

If you have enough disk space that you can have both your entire non-ASM database and your ASM disk group on disk at the same time, you can do the migration directly without using tapes.
1. Back up your database files as copies to the ASM disk group.
BACKUP AS COPY INCREMENTAL LEVEL 0 DATABASE FORMAT ‘+DISK’ TAG ‘ORA_ASM_MIGRATION’;
REF: Oracle(r) 10g Backup and Recovery Advance User’s Guide, 16-2

None

None

None

None

None

None

Once the DROP DISK operation is completed, you CANNOT run the UNDROP DISKS
command any more.

The information gathered by SQL Test Case Builder includes:
✑ the query being executed,
✑ table and index definitions (but not the actual data),
✑ PL/SQL functions, procedures, and packages,
✑ optimizer statistics,
✑ and initialization parameter settings.

None

None

None

A backup set is an RMAN-specific proprietary format, whereas an image copy is a bit-for-bit copy of a file. By default, RMAN creates backup sets.
Refer to here

None

None

Incident packaging service (IPS) and incident packages
The IPS enables you to automatically and easily gather the diagnostic data—traces, dumps, health check reports, and more—pertaining to a critical error and package the data into a zip file for transmission to Oracle Support. Because all diagnostic data relating to a critical error are tagged with that error's incident number, you do not have to search through trace files and other files to determine the files that are required for analysis; the incident packaging service identifies the required files automatically and adds them to the zip file.
Before creating the zip file, the IPS first collects diagnostic data into an intermediate logical structure called an incident package (package). Packages are stored in the Automatic Diagnostic Repository. If you choose to, you can access this intermediate logical structure, view and modify its contents, add or remove additional diagnostic data at any time, and when you are ready, create the zip file from the package. After these steps are completed, the zip file is ready to be uploaded to Oracle Support.

The SQL Access Advisor analyzes all SQL running during a given time period and recommends indexes and materialized views to improve the overall performance of the database.
A is incorrect because there is no such advisor as the Automatic Memory Manager.
B is incorrect because the SQL Tuning Advisor looks only at a single SQL statement and provides recommendations.
C is incorrect because the Segment Advisor recommends segment shrink when table and index segments are heavily fragmented.

None

Results of the Redefinition Process
The following are the end results of the redefinition process:
The original table is redefined with the columns, indexes, constraints, grants, triggers, and statistics of the interim table.
Dependent objects that were registered, either explicitly using REGISTER_DEPENDENT_OBJECT or implicitly using COPY_TABLE_DEPENDENTS, are renamed automatically so that dependent object names on the redefined table are the same as before redefinition.
Note:
If no registration is done or no automatic copying is done, then you must manually rename the dependent objects.
The referential constraints involving the interim table now involve the redefined table and
are enabled.
✑ Any indexes, triggers, materialized view logs, grants, and constraints defined on the original table (prior to redefinition) are transferred to the interim table and are dropped when the user drops the interim table. Any referential constraints involving the original table before the redefinition now involve the interim table and are disabled.
✑ Some PL/SQL objects, views, synonyms, and other table-dependent objects may become invalidated. Only those objects that depend on elements of the table that were changed are invalidated. For example, if a PL/SQL procedure queries only columns of the redefined table that were unchanged by the redefinition, the procedure remains valid. See "Managing Object Dependencies" for more information about schema object dependencies.

The bulk load operation can be done by setting up a file watcher, then raise the event to
inform the scheduler, it is kind of application based event.
After the bulk load job, you can use Scheduler raised event, e.g. JOB COMPLETE, to fire the index rebuild job.
There are two kinds of events consumed by the Scheduler:
✑ Events raised by your application
An application can raise an event to be consumed by the Scheduler. The Scheduler reacts to the event by starting a job. For example, when an inventory tracking system notices that the inventory has gone below a certain threshold, it can raise an event that starts an inventory replenishment job.
See "Starting Jobs with Events Raised by Your Application".
✑ File arrival events raised by a file watcher
You can create a file watcher—a Scheduler object introduced in Oracle Database 11g Release 2—to watch for the arrival of a file on a system. You can then configure a job to start when the file watcher detects the presence of the file. For example, a data warehouse for a chain of stores loads data from end-of-day revenue reports uploaded from the point- of-sale systems in the stores. The data warehouse load job starts each time a new end-of- day report arrives.

None