[Dec 25, 2025] Genuine 1Z1-182 Exam Dumps Free Demo [Q48-Q65]

False. Server processes (foreground) read blocks into the buffer cache during user queries, not background processes.
Explanation:
Background processes manage core database operations. Let’s break it down:
A : Creating dedicated server connections.
False. Dedicated server connections are created by the listener, not background processes. The listener hands off the connection to a server process (e.g., ora_s000), which isn’t a background process.
B : Registering services with Oracle Net listeners.
True. The LREG process (Listener Registration, formerly PMON’s role) registers services with listeners, using parameters like LOCAL_LISTENER.
Mechanics:LREG sends service details (e.g., orcl) to the listener every 60 seconds or on startup.
C : Writing redo to log files.
True. The LGWR (Log Writer) process writes redo entries from the redo log buffer to online redo log files, ensuring transaction durability.
Mechanics:Triggered by commits, log buffer fills, or checkpoints.
D : Writing dirty database block images from the buffer cache.
True. The DBWn (Database Writer) processes write modified (dirty) blocks from the buffer cache to data files, maintaining consistency.
Mechanics:Occurs at checkpoints or when free buffers are needed.

A .False. DBCA can’t change character sets post-creation.
B .False. Listeners are managed via NetCA or lsnrctl.
C .True. DBCA can switch server modes for existing DBs.
D .False. Tablespaces are created via SQL, not DBCA for existing DBs.
E .True. DBCA can generate clone templates from existing DBs.

A .False. Backups are configured via RMAN, not DBCA.
B .True. DBCA allows nonstandard block sizes during DB creation.
C .True. DBCA can register new DBs with EM.
D .False. Block size is fixed post-creation.
E .False. Flashback is enabled via SQL, not DBCA for existing DBs.

A .False. No checkpoint occurs with ABORT.
B .False. Instance recovery, not media recovery, is needed.
C .True. Crash recovery rolls back uncommitted changes on startup.
D .False. Files aren’t closed cleanly with ABORT.
E .True. Shutdown doesn’t roll back; recovery does.

A . Dependent indexes become UNUSABLE.False. SHRINK SPACE COMPACT does not affect index usability; only SHRINK SPACE without COMPACT may require index maintenance if CASCADE is omitted.
B . … starting toward the end of the ORDERS segment.False. Rows are compacted toward the beginning of the segment, not the end.
C . Only queries are allowed …False. Both queries and DML are allowed during SHRINK SPACE COMPACT as it’s an online operation.
D . The high-water mark (HWM) of ORDERS is adjusted.False. COMPACT moves rows but doesn’t adjust the HWM; the full SHRINK SPACE command is needed for HWM adjustment.
E . Queries and DML statements are allowed …True. This is an online operation in 23ai, allowing concurrent access.
F . … starting from the beginning of the ORDERS segment.True. Rows are moved to fill free space from the segment’s start.

A .False. Data files open in OPEN.
B .False. Redo logs open in OPEN.
C .False. PFILE/SPFILE is read at NOMOUNT.
D .False. SGA is allocated at NOMOUNT.
E .True. Alert log records mount event.
F .True. Control files are read in MOUNT.

A .False. Net Manager is local, not centralized.
B .False. NetCA can run standalone.
C .True. EMCC manages service names centrally.
D .True. EMCC configures listeners on managed targets.
E .False. lsnrctl starts a default listener if no listener.ora exists.
F .True. Net Manager configures local tnsnames.ora.

A .True. DBA_EXTERNAL_LOCATIONS (or prefixed variants) shows external table data sources (e.g., file paths).
B-D .False. These views cover columns or tables but not external sources specifically.

A .False. AWR doesn’t create PDBs.
B .True. AWR stats aid migration planning (e.g., performance baselines).
C .False. AWR doesn’t convert CDB to Non-CDB.
D .False. SID management isn’t AWR’s role.

A .False. Session limits don’t tie to password changes.
B .False. CPU limits don’t lock accounts.
C .False. No direct “logged-in days” parameter.
D .True. PASSWORD_REUSE_MAX=UNLIMITED prevents reuse.
E .True. PASSWORD_LOCK_TIME sets inactivity lockout.

A .True. ASSM categorizes blocks (e.g., 0-25%, 25-50%) for efficient space use.
B .False. Updates may cause chaining/migration, not always relocation.
C .True. ASSM optimizes inserts into suitable blocks.
D .False. ASSM uses a bitmap, not necessarily the first block.
E .False. PCTFREE is segment-specific, not universally 10%.

A .True. ADR is a file system directory structure (e.g., /u01/app/oracle/diag), external to the database.
B .False. ADR also stores diagnostics for non-database components (e.g., ASM, listener).
C .False. It’s file-based, not schema-based.
D .True. ADR logs (e.g., alert logs, trace files) are accessible even if the instance is down.
E .True. DIAGNOSTIC_DEST sets the ADR base directory.

B .True. The SQL Statistics Advisor (new in 23ai) identifies stale or missing statistics. Others focus on tuning, performance analysis, or access paths.

This command moves/renames a data file online. Let’s evaluate:
A . DML may be performed on tables with one or more extents in this data file during the execution of this command.
True. Introduced in 12c and refined in 23ai, MOVE DATAFILE is an online operation, allowing DML (e.g., INSERT, UPDATE) on tables within the file. Oracle ensures consistency via redo and undo.
Mechanics:The file is copied to the new location/name while tracking changes, then switched atomically.
Practical Use:Minimizes downtime in production systems.
B . If Oracle Managed Files (OMF) is used, then the file is renamed but moved to DB_CREATE_FILE_DEST.
False. With OMF, omitting the TO clause would place the file in DB_CREATE_FILE_DEST, but here, TO ‘\u01/sales01.dbf’ explicitly specifies the target, overriding OMF defaults.
Mechanics:OMF only applies if the destination is unspecified (e.g., MOVE DATAFILE … without TO).
Why Incorrect:Explicit path trumps OMF behavior.
C . The tablespace containing SALES1.DBF must be altered READ ONLY before executing the command.
False. READ ONLY isn’t required; the operation is online and supports active use.
Why Incorrect:Conflicts with Oracle’s online move feature.
D . The file is renamed and stored in the same location.
True. The command renames /u01/sales1.dbf to /u01/sales01.dbf (correcting \u01 to /u01 as a Windows/Unix typo), keeping it in /u01/. REUSE allows overwriting if sales01.dbf exists.
Mechanics:File is copied and renamed in-place within the same filesystem directory.
E . The tablespace containing SALES1.DBF must be altered OFFLINE before executing the command.
False. Offline mode isn’t needed; the online move handles activetablespaces.

A .False. No such restriction exists; DB_32K_CACHE_SIZE is independent of DB_CACHE_SIZE.
B .True. A nonstandard block size (32K) requires a corresponding cache (DB_32K_CACHE_SIZE) set to a non-zero value within SGA limits.
C .False. OS block size is irrelevant; Oracle manages its own block sizes.
D .False. No requirement for it to exceed DB_CACHE_SIZE.
E .True. The file system must have 100G available for the datafile.

A .True. Enabled per session with ALTER SESSION ENABLE RESUMABLE.
B .True. Multiple suspensions can occur in one session.
C .False. Works with dictionary-managed tablespaces too.
D .False. Timeout is session-specific.
E .True. Privilege doesn’t prevent suspension; quota limits do.
F .False. Triggers execute but can’t suspend themselves.

False. No “Automatic Application Tracing” exists as an AWR tool. SQL tracing (e.g., DBMS_MONITOR) is manual, and high-load SQL is captured by AWR indirectly via V$SQL snapshots, not a distinct tracing tool.
Why Incorrect:Conflates manual tracing with AWR’s passive collection.
Explanation:
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.

A .False. ORCL is a TNS alias, not necessarily the DB name.
B .True. Must map to a connect descriptor (e.g., HOST=… PORT=1531) in tnsnames.ora.
C .False. It’s not the server name but a network alias.
D .False. Client-side tnsnames.ora is used, not server-side.
E .False. SERVICE_NAMES is server-side, not client-side.