1Z0-183 Practice Questions

When unplugging a Pluggable Database (PDB) using the ALTER PLUGGABLE DATABASE ... UNPLUG INTO command, specifying a destination filename with a .pdb extension instructs Oracle to create a PDB archive file. This archive is a single, compressed file (using a tar and gzip format) that contains both the XML metadata file describing the PDB's structure and a copy of all the PDB's physical datafiles. This creates a self-contained, portable package for easily moving the PDB to another CDB.

A. The .pdb archive is a standard compressed tarball (.tar.gz), not a proprietary RMAN backup set format.

C. Creating only an XML metadata file occurs when the specified filename has an .xml extension or an extension other than .pdb.

D. This command creates a portable file for transfer; it does not create a database directory object or point to live datafiles.

1. Oracle Database SQL Language Reference, 19c. "ALTER PLUGGABLE DATABASE", unplugclause. The documentation states: "If you specify a file name with a .pdb extension, then the database creates a PDB archive file... The PDB archive file is a compressed file that includes the XML file and the PDB's data files."

2. Oracle Database Multitenant Administrator’s Guide, 19c. Chapter 6, "Unplugging and Plugging In PDBs". The section "About Unplugging a PDB" describes the creation of a PDB archive file when using the .pdb extension.

The MAXOPENFILES parameter for an RMAN channel specifies the maximum number of input datafiles that RMAN can read from simultaneously. The default is 8. In a scenario with hundreds of small files on a high-performance I/O subsystem, the default value can lead to I/O bottlenecks as the channel waits for reads to complete. Increasing MAXOPENFILES allows the channel to open and read from more files concurrently, thereby increasing I/O throughput and keeping the storage array busy, which directly addresses the stated goal.

A. RATE is used to throttle (limit) the I/O rate, not increase concurrent file reads. Increasing it would only remove a potential cap, not change the parallelism of reads.

C. SECTION SIZE is used for multisection backups to parallelize the backup of a single large file across multiple channels, not for reading multiple small files by one channel.

D. MAXPIECESIZE limits the size of the output backup piece. Lowering it creates more pieces but does not affect the number of input files read concurrently.

1. Oracle Database Backup and Recovery User's Guide, 23c, "Tuning RMAN Backup Performance". The section on MAXOPENFILES states: "The MAXOPENFILES parameter of the ALLOCATE CHANNEL or CONFIGURE CHANNEL command specifies the maximum number of input files that a backup channel can have open at any given time. The default value is 8."

2. Oracle Database Backup and Recovery Reference, 23c, "CONFIGURE". The description for MAXOPENFILES confirms its purpose is to control the number of concurrently open input files for a channel.

When Automatic Memory Management (AMM) is enabled by setting MEMORYTARGET to a non-zero value, any explicitly set value for SGATARGET is interpreted as the minimum size for the System Global Area (SGA). The AMM mechanism will dynamically resize the SGA and PGA within the total MEMORYTARGET limit to meet workload demands. However, it will not shrink the SGA to a size smaller than the value specified by SGATARGET. This allows administrators to guarantee a minimum amount of memory is always allocated to the SGA components.

B. Auto-tuning for the SGA is not disabled; SGATARGET simply sets a lower bound for the tuning, not a fixed size.

C. The SGATARGET setting is not ignored; it is actively used by AMM as a boundary condition for its resizing algorithms.

D. SGATARGET acts as a minimum, not a maximum, in this configuration. SGAMAXSIZE would serve as a hard upper limit.

1. Oracle Database Concepts, 19c, Chapter 15, "Memory Architecture", Section "About Automatic Memory Management". It states: "The SGATARGET and PGAAGGREGATETARGET parameters act as minimum size settings for their respective memory areas."

2. Oracle Database Reference, 19c, Initialization Parameters, MEMORYTARGET. The documentation explains: "If you set MEMORYTARGET, you can also set SGATARGET... SGATARGET will be treated as the minimum size of the SGA."

3. Oracle Database Performance Tuning Guide, 19c, Chapter 7, "Configuring and Using Memory", Section "Using Automatic Memory Management". It confirms that with AMM, SGATARGET specifies the minimum size of the SGA.

Oracle provides a pre-installation RPM package specifically for Oracle Linux to automate the preparation of the operating system for a database installation. For Oracle Database 23ai, this package is oracle-database-preinstall-23ai. Installing this package using a package manager like dnf or yum automatically creates the oracle user and standard groups (e.g., oinstall, dba), configures required kernel parameters in /etc/sysctl.conf, sets resource limits, and installs all necessary software dependencies.

B: The root.sh script is executed after the Oracle software is installed to finalize permissions and configurations for the current version, not to prepare the OS beforehand.

C: The dbca (Database Configuration Assistant) tool is used to create and configure databases after the software installation is complete. It does not have an OS configuration flag.

D: The sysresv utility is a diagnostic tool used to view information about shared memory and semaphores allocated by an Oracle instance, not for OS preparation.

Oracle Database 23c Installation Guide for Linux, "Automatically Configuring Oracle Linux with Oracle Preinstallation RPM", Section 4.2.2. The guide states, "If you use the Oracle Preinstallation RPM, then it completes most prerequisite configuration steps for you."

Oracle Database 23c Installation Guide for Linux, "About the Oracle Database Preinstallation RPM", Section 4.2.2.1. This section details the specific actions performed by the RPM, including user creation, kernel parameter configuration, and dependency installation.

When INMEMORYAUTOMATICLEVEL is set to HIGH, Automatic In-Memory (AIM) is fully enabled. AIM uses the database's heat map and other usage statistics to identify segments that would benefit most from being in the In-Memory Column Store (IMCS). For "hot" segments created without an INMEMORY clause, AIM will automatically issue an ALTER TABLE ... INMEMORY command to enable them for the IMCS and then trigger their population. This automates the management of the IMCS, ensuring optimal performance without manual DBA intervention.

B. This describes the behavior when INMEMORYAUTOMATICLEVEL is OFF or LOW, where AIM does not automatically add objects to the IMCS.

C. Using a tablespace's INMEMORY attribute is one method of population, but INMEMORYAUTOMATICLEVEL=HIGH enables object-level automation regardless of the tablespace setting.

D. AIM persists the INMEMORY attribute in the data dictionary for the object; the change is not temporary. It will remain until AIM evicts it or a DBA manually alters it.

1. Oracle Database In-Memory Guide, 23c, "Automating In-Memory Column Store Management". This chapter details the functionality of Automatic In-Memory (AIM).

2. Oracle Database Reference, 23c, "INMEMORYAUTOMATICLEVEL". The documentation for the HIGH value states: "enables full automation for the IM column store. The database automatically manages the population and eviction of objects in the IM column store based on their usage patterns."

Active Database Duplication is a feature where RMAN copies a source database over the network to a destination host without relying on pre-existing backups. For this process to work, RMAN must establish simultaneous connections to both the source database instance and the auxiliary (destination) instance. The connection to the source is designated as TARGET, and the connection to the destination instance, which is typically in a NOMOUNT state, is designated as AUXILIARY. RMAN uses these two connections to coordinate the direct transfer of data blocks from the target to the auxiliary.

A. The AUXILIARY connection is mandatory for any duplication operation, as it represents the destination instance where the new database is being created.

C. Connecting only to the TARGET is insufficient. RMAN requires an active connection to the AUXILIARY instance to create datafiles and manage the duplication process.

D. Connecting only to the AUXILIARY is insufficient. RMAN needs the TARGET connection to read the data blocks from the source database.

1. Oracle Database Backup and Recovery User's Guide, 23c, Chapter 23, "Duplicating a Database", Section: "About Active Database Duplication". The documentation states: "For active database duplication, RMAN connects to the source database as TARGET and the destination database as AUXILIARY. RMAN copies the live source database files over the network to the auxiliary destination."

2. Oracle Database Backup and Recovery Reference, 23c, "DUPLICATE Command". The usage notes and examples for DUPLICATE ... FROM ACTIVE DATABASE consistently show RMAN connected to both TARGET and AUXILIARY instances.

The FLASHBACK TABLE command reverts a table to a past state. This operation may require moving rows between data blocks to restore their previous state, for example, if rows were deleted and their space was reclaimed. The ORA-08189 error explicitly states that this is not possible because row movement is disabled for the target table. To permit Oracle to move rows as needed during the flashback operation, row movement must be explicitly enabled on the table using the ALTER TABLE ... ENABLE ROW MOVEMENT command.

A. ROWMOVEMENT is not a system-level parameter; it is a table-specific property and cannot be set with ALTER SYSTEM.

C. FLASHBACK ON is not a valid clause for the ALTER TABLE statement in this context. Flashback capabilities are managed differently.

D. ALTER TABLESPACE ... FLASHBACK ON is used for Flashback Database, which is a separate feature operating at the database level, not for individual table flashback.

1. Oracle Database SQL Language Reference, 23ai. "FLASHBACK TABLE". The prerequisites section states: "To flash back a table, you must have the FLASHBACK object privilege on the table or the FLASHBACK ANY TABLE system privilege. You must also have SELECT, INSERT, DELETE, and ALTER object privileges on the table. In addition, you must enable row movement on the table (ALTER TABLE...ENABLE ROW MOVEMENT)."

2. Oracle Database Administrator's Guide, 23ai. "Flashing Back a Table to a Point in Time". The section "Prerequisites for Using Flashback Table" explicitly lists: "Row movement must be enabled on the table for which you are issuing the FLASHBACK TABLE statement."

The DBMSMONITOR.SERVMODACTTRACEENABLE procedure is designed specifically for this requirement. It enables SQL tracing for database sessions based on a combination of service name, module, and action. This configuration is persistent, meaning it is stored in the data dictionary and remains active across session disconnects and database instance restarts. New sessions matching the specified criteria will automatically have tracing enabled. This method provides a granular and persistent way to trace specific application components without manual intervention.

A. DBMSSESSION.SESSIONTRACEENABLE enables tracing only for the current session and is not persistent; it ends when the session disconnects.

C. DBMSAPPLICATIONINFO.SETACTION is used by an application to set the action name for its current session; it does not enable tracing.

D. DBMSSYSTEM.SETEV is an older, undocumented procedure for setting events in another session and is not the standard or supported method for persistent tracing.

1. Oracle Database PL/SQL Packages and Types Reference, 23ai. "DBMSMONITOR Subprograms". The documentation for SERVMODACTTRACEENABLE Procedure states it "Enables SQL tracing for a given service name, module, and action."

2. Oracle Database Performance Tuning Guide, 23ai. Chapter 12, "SQL Trace and TKPROF". Section "Enabling and Disabling SQL Trace for a Specific Service, Module, and Action". This section details the usage and persistence of this procedure.

Server-generated alerts for metrics like tablespace usage are "stateful." When the condition that triggered the alert is resolved (i.e., tablespace usage drops below the warning threshold), the database automatically clears the alert. The clearing process involves removing the alert record from the DBAOUTSTANDINGALERTS view, which shows current, active alerts, and moving it to the DBAALERTHISTORY view for historical tracking and auditing purposes. This automated lifecycle ensures that the outstanding alerts view accurately reflects only current problems requiring attention.

B. Cleared alerts are moved to the history view; they do not remain in the outstanding alerts view with a different status.

C. This alert is metric-based and clears automatically when the metric is no longer in the threshold range. It does not require manual acknowledgement via DBMSSERVERALERT.

D. The alert is not deleted entirely. It is archived in DBAALERTHISTORY to maintain a record of past events, which is crucial for system monitoring and analysis.

1. Oracle Database Administrator's Guide, 23c, "Monitoring Operations with Server-Generated Alerts". The section "Viewing Alerts" describes the purpose of DBAOUTSTANDINGALERTS and DBAALERTHISTORY.

2. Oracle Database Reference, 23c, "DBAOUTSTANDINGALERTS". The view description notes that it contains outstanding alerts. Once an alert is cleared, it is moved to DBAALERTHISTORY.

The Incident Packaging Service (IPS) is a component of the Oracle Database fault diagnosability infrastructure. It is managed through the ADR Command-Line Interface (ADRCI). ADRCI provides the IPS command set (e.g., IPS CREATE PACKAGE) to package all relevant diagnostic data for a specific incident or problem. This service gathers the necessary trace files, dumps, and metadata from the Automatic Diagnostic Repository (ADR) and consolidates them into a single compressed (zip) file. This package can then be easily uploaded to Oracle Support for analysis, streamlining the support process.

D: lsinventory is a command associated with the OPatch utility, used to list the patches installed in an Oracle Home, not for packaging diagnostic data.

1. Oracle Database Utilities, 19c, Chapter 3, "ADRCI: ADR Command Interpreter". The chapter details the use of ADRCI and its IPS commands. The section "Packaging Incidents with the IPS Command" states, "You can use the ADRCI IPS command to collect diagnostic data for an incident... into a zip file for transmission to Oracle Support."

2. Oracle Database Administrator's Guide, 19c, Chapter 15, "Managing Diagnostic Data". This chapter describes the overall fault diagnosability infrastructure, including the role of ADRCI and IPS in packaging incidents.