Oracle 1Z0-182 Exam Dumps

Dictionary-managed tablespaces (DMTs) use the data dictionary for extent management, whilelocally managed tablespaces (LMTs) use bitmaps. Let's evaluate compatibility:

A . Capacity planning growth reports based on historical data in the Automatic Workload Repository (AWR).

True. AWR tracks space usage (e.g., DBA_HIST_TBSPC_SPACE_USAGE) regardless of tablespace type, enabling growth reports for both DMTs and LMTs.

Mechanics:MMON collects metrics like segment growth, stored in SYSAUX, accessible via EM or scripts.

Practical Use:Helps predict when to add data files, universal across management types.

B . Online table segment shrink.

False. ALTER TABLE ... SHRINK SPACE requires LMTs with Automatic Segment Space Management (ASSM), unavailable in DMTs, which lack bitmap-based free space tracking.

Why Incorrect:DMTs use freelists, incompatible with shrink operations.

C . Online index segment shrink.

False. Like tables, ALTER INDEX ... SHRINK SPACE requires LMTs with ASSM, not supported in DMTs.

Why Incorrect:Same limitation as B; DMTs can't compact online.

D . Oracle Managed Files (OMF).

True. OMF automates file naming and placement (via DB_CREATE_FILE_DEST) for both DMTs and LMTs, agnostic to extent management.

Mechanics:Example: CREATE TABLESPACE ts1; creates an OMF file in either type.

Edge Case:DMTs are rare in 23ai, but OMF still applies.

E . Automatic data file extension (AUTOEXTEND).

True. AUTOEXTEND ON allows data files to grow as needed, supported in both DMTs and LMTs since early versions.

Mechanics:ALTER DATABASE DATAFILE ... AUTOEXTEND ON NEXT 100M; works universally.

A .True. Local checkpoints are allowed in PDBs.

B .False. Buffer cache is CDB-level.

C .False. Log switching is CDB-level.

D .True. Restricted session can be toggled per PDB.

A .True. PDB_DBA grants admin rights (e.g., CREATE SESSION, ALTER SYSTEM) within the PDB.

B .False. DDL on objects requires ownership or explicit grants.

C .False. User management needs CREATE USER privilege, not inherent.

D .False. It includes multiple privileges, not none.

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.

Roles in Oracle manage privileges efficiently. Let's dive into each option:

A . Roles must be password protected.

False. Roles can be password-protected (e.g., CREATE ROLE mgr IDENTIFIED BY secret), but it's optional. Non-protected roles (default) are enabled automatically if granted, requiring no password.

Mechanics:Password-protected roles need SET ROLE mgr IDENTIFIED BY secret, enhancing security for sensitive privileges.

B . Roles may be granted to other roles.

True. Roles can form hierarchies (e.g., GRANT clerk TO mgr), allowing nested privilege management.

Mechanics:A user with mgr inherits clerk privileges indirectly. Revoking clerk from mgr cascades appropriately.

Practical Use:Simplifies complex privilege structures in large organizations.

C . The SET ROLE statement can enable one or more roles for a session.

True. SET ROLE role1, role2; activates specified roles for the session, assuming they're granted and not password-protected (or password is provided).

Mechanics:Enabled roles grant their privileges immediately within the session scope.

D . Object privileges may not be granted to roles.

False. Object privileges (e.g., GRANT SELECT ON emp TO clerk) are a primary use of roles, making this statement incorrect.

Why Incorrect:Roles are designed for this purpose, contradicting the option.

E . All roles granted to a user are set on default when the user logs in.

False. Only roles marked as DEFAULT ROLE (via ALTER USER ... DEFAULT ROLE role1) are enabled at login. Non-default roles require SET ROLE.

Mechanics:Check via SELECT * FROM DBA_ROLE_PRIVS WHERE DEFAULT_ROLE='YES'.

F . The SET ROLE statement can disable one or more roles for a session.

True. SET ROLE NONE disables all roles, or SET ROLE role1 implicitly disables others not listed, providing granular control.

Practical Use:Useful for testing or restricting privileges temporarily.