Oracle 1Z0-182 Exam Dumps

Logical structures (e.g., segments, extents) map to physical structures (e.g., data files, blocks). Let's dissect each option:

A . A segment can span multiple data files in some tablespaces.

True. A segment (e.g., a table or index) is a logical entity stored in a tablespace. In a smallfile tablespace (default in Oracle), a segment's extents can span multiple data files if the tablespace has multiple files and space allocation requires it. This is common in large tables or when autoextend adds new files.

Mechanics:Oracle allocates extents across available data files in a round-robin fashion (with ASSM) or as needed, ensuring the segment's data is distributed. This doesn't apply to bigfile tablespaces, which use a single data file.

Example:A 10GB table in a tablespace with two 5GB data files will span both.

B . Segments can span multiple tablespaces.

False. A segment is confined to a single tablespace. Oracle enforces this to maintain logical separation (e.g., a table's data stays in its assigned tablespace). Partitioned tables can have partitions in different tablespaces, but each partition is a separate segment.

Why Not:The segment header and extent map reside in one tablespace, preventing cross-tablespace spanning for a single segment.

C . A segment might have only one extent.

True. A segment starts with one extent upon creation (e.g., a small table or index). If no further growth occurs, it remains a single-extent segment. This is common with small objects or when INITIAL extent size suffices.

Mechanics:In locally managed tablespaces (default), the initial extent is allocated based on INITIAL or tablespace defaults (e.g., 64KB), and additional extents are added only as needed.

D . All tablespaces may have one or more data files.

False. Bigfile tablespaces are restricted to one data file (up to 128TB). Smallfile tablespaces (traditional) can have multiple data files (up to 1022), but the ''all'' phrasing makes this false due to bigfile exceptions.

Clarification:The question's intent may assume smallfile tablespaces, but Oracle 23ai supports both types.

A .False. LREG handles registration in 23ai, not PMON.

B .False. CKPT (Checkpoint) process updates the control file.

C .True. PMON cleans up after failed processes (e.g., releases locks).

D .True. PMON rolls back uncommitted transactions of failed processes.

E .False. SMON (System Monitor) manages temporary segment cleanup.

The ALTER DATABASE MOVE DATAFILE command relocates a data file to a new location while the database remains online, introduced in Oracle 12c and enhanced in subsequent releases like 23ai. Let's evaluate each option:

A . DML may be performed on tables with one or more extents in this data file during the execution of this command.True. The move operation is online by default in Oracle 23ai, allowing DML (INSERT, UPDATE, DELETE) operations on tables within the data file being moved. The database ensures consistency using redo and undo mechanisms.

B . It overwrites any existing file with the name sales02.dbf in /u02 by default.False. By default, the command does not overwrite an existing file unless the REUSE clause is specified (e.g., ALTER DATABASE MOVE DATAFILE ... REUSE). Without it, the command fails if the target file exists.

C . The 'TO' clause containing the new file name must be specified even if Oracle Managed Files (OMF) is used.False. When OMF is enabled (via DB_CREATE_FILE_DEST), the TO clause is optional. If omitted, Oracle automatically generates a file name and places it in the OMF destination.

D . Compressed objects in sales01.dbf will be uncompressed in sales02.dbf after the move.False. The move operation is a physical relocation of the data file; it does not alter the logical structure or compression state of objects within it. Compressed data remains compressed.

E . Tables with one or more extents in this data file may be queried during the execution of this command.True. The online nature of the move allows queries (SELECT statements) to proceed without interruption, leveraging Oracle's multi-version consistency model.

A .False. Limited to captured privileges, not all schema objects.

B .False. SYS is excluded from capture.

C .True. Captures indirect role privileges used.

D .True. Captures direct role privileges used.

E .False. Focus is on roles, not self-owned objects broadly.

A .False. ADR is file-based, not in a schema.

B .False. No such default exists.

C .True. ADR logs ASM diagnostics.

D .True. Supports Clusterware diagnostics.

E .False. Defaults to $ORACLE_BASE or /u01/app/oracle if unset.