Oracle 1Z0-182 Exam Dumps

The Automatic Workload Repository (AWR) is a cornerstone of Oracle's self-tuning capabilities, collecting and storing performance statistics for analysis. Let's dissect each option:

A . Automatic capture of statistical information from the SGA and storing it in the AWR using Automatic Database Diagnostic.

True. AWR automatically captures statistics (e.g., wait events, SQL stats) from the System Global Area (SGA) via the MMON (Manageability Monitor) process, storing them in the AWR repository (in SYSAUX). This is part of the Automatic Database Diagnostic Monitor (ADDM) framework, though ''Automatic Database Diagnostic'' likely refers to this broader mechanism.

Mechanics:Snapshots are taken hourly by default (configurable via DBMS_WORKLOAD_REPOSITORY.MODIFY_SNAPSHOT_SETTINGS), persisting data like DBA_HIST_SYSSTAT for self-tuning analysis.

Practical Use:Enables historical performance tracking, feeding tools like ADDM and SQL Tuning Advisor.

Edge Case:If STATISTICS_LEVEL=BASIC, AWR collection is disabled, haltingself-tuning.

Historical Note:Introduced in 10g, enhanced in 23ai for finer granularity.

B . ADDM, a server-based expert that reviews database performance statistics captured by Snapshots to identify potential problems before system performance degrades noticeably.

True. The Automatic Database Diagnostic Monitor (ADDM) analyzes AWR snapshots to proactively detect issues (e.g., high CPU usage, I/O bottlenecks) and recommend fixes. It runs automatically after each snapshot in maintenance windows.

Mechanics:ADDM uses DBA_ADVISOR_FINDINGS to log issues, leveraging AWR data like DBA_HIST_SQLSTAT. Example: It might suggest adding an index for a slow query.

Practical Use:Prevents performance degradation in production systems by catching trends early.

Edge Case:Limited by snapshot frequency; real-time issues may need manual intervention.

C . Automatic Diagnostic Collector used to capture and store database errors and hung analysis.

False. No such tool exists as an ''Automatic Diagnostic Collector'' in AWR context. This likely confuses the Incident Packaging Service (IPS) or ADR (Automatic Diagnostic Repository), which handles errors but isn't AWR-based or self-tuning.

Why Incorrect:ADR collects trace files and logs, not AWR statistics, and isn't part of self-tuning.

D . Automatic population of performance views (V$ views) from statistical data stored in AWR repository and using Automatic Database Diagnostic.

False. V$ views (e.g., V$SESSION) are real-time memory structures in the SGA, not populated from AWR, which is historical (e.g., DBA_HIST_*). AWR doesn't back-feed V$ views; the reverse occurs via snapshots.

Why Incorrect:Misunderstands the data flow; AWR is a sink, not a source for V$ views.

Temp UNDO, introduced in Oracle 12c and refined in 23ai, stores undo for global temporary tables (GTTs) in temporary tablespaces:

A . It permits DML on GTTs even if the database is opened read-only.False. In read-only mode, DML on GTTs is allowed regardless of temp UNDO, as GTT data is session-private, but temp UNDO doesn't specifically enable this.

B . It reduces the amount of UNDO stored in the UNDO tablespace.True. Temp UNDO stores undo in the temporary tablespace, reducing usage of the permanent UNDO tablespace.

C . It reduces I/Os to the SYSTEM tablespace.True. By avoiding permanent undo, it reduces metadata updates in the SYSTEM tablespace related to undo management.

D . It reduces the amount of redo generated.True. Temp UNDO changes are not redo-logged to the same extent as permanent undo, minimizing redo generation.

E . It reduces I/Os to the SYSAUX tablespace.False. SYSAUX is unrelated to undo management; temp UNDO affects temporary and SYSTEM tablespaces.

A .False. Works with DMTs too.

B .True. LMTs use bitmaps, unlike DMT freelists.

C .False. OMF is independent of management type.

D .False. Alerts work with both.

E .True. Shrink requires LMTs with ASSM.

A .False. Schema owners need EXECUTE on DBMS_FGA.

B .False. Not limited to SYSDBA.

C .True. AUDIT_ADMIN includes FGA creation rights.

D .False. No such role exists.

E .True. DBMS_FGA.ADD_POLICY requires this privilege.

A .False. Links can connect to non-Oracle DBs via gateways.

B .False. No such user requirement; authentication is separate.

C .False. Any user with CREATE PUBLIC DATABASE LINK can create one.

D .True. Links enable remote schema access (e.g., SELECT * FROM emp@remote).

E .False. Public links allow access, but privileges on remote objects are needed.