Free 1Z0-182 Practice Test

The view EXTERNALLOCATIONS catalogs every file, URL, or other location that supplies data to an external table or external partition. The DBA form (and its ALL and USER synonyms) is therefore the data dictionary view that explicitly “describes the data sources of external tables.”

B. TABCOLUMNS lists column metadata; it contains no information about external‐table data sources.
C. EXTERNALTABLES contains definition metadata (type, default directory, access parameters) but not the individual data source locations.
D. TABLES is the general catalogue of relational tables; it has no external-table-specific columns.

1. Oracle Database Reference 23c, F85463-01, “DBAEXTERNALLOCATIONS – describes the data sources of external tables,” View Descriptions chapter, p. 3337.

2. Oracle Database Concepts 23c, F85456-01, chap. 21 “External Tables,” subsection “Data sources for external tables,” para. 2.

To view the current and effective initialization parameter settings for a specific Pluggable Database (PDB), you must connect to that PDB and query the V$PARAMETER view. This dynamic performance view is container-aware; when queried from within a PDB, it displays the parameter values that are specifically in effect for that container. The ISPDBMODIFIABLE column indicates whether the parameter can be altered at the PDB level. This is the standard and correct method for inspecting a PDB's active parameter configuration.

A. pdbspfile$ is an internal, undocumented view related to stored SPFILE settings, not the current effective values, and should not be queried directly.
B. Querying v$parameter from the CDB root shows the settings for the root container, not the specific effective values for a particular PDB.
C. pdbspfiles is not a valid view name. The internal view is pdbspfile$, which should not be used for this purpose.

1. Oracle Database 23ai, "Database Reference", Chapter 4, "Dynamic Performance (V$) Views", Section "V$PARAMETER". (Documents that V$PARAMETER shows parameter values for the current session and is container-specific).

2. Oracle Database 23ai, "Multitenant Administrator's Guide", Chapter 5, "Administering PDBs", Section "Modifying Initialization Parameters for a PDB". (Describes using ALTER SYSTEM SET ... SCOPE=... within a PDB and verifying with SHOW PARAMETER or querying V$PARAMETER).

Oracle background processes perform maintenance tasks for the database instance. The Listener Registration (LREG) process registers instance and service information with the listener. The Log Writer (LGWR) process is responsible for writing redo log entries from the redo log buffer to the online redo log files. The Database Writer (DBWn) process writes modified (dirty) data blocks from the database buffer cache to the data files on disk. These are all fundamental background process tasks.

A. The Oracle Net Listener, a separate process, creates dedicated server processes in response to client connection requests.
E. Reading data blocks from disk into the buffer cache is performed by foreground server processes at the request of a user session.

1. Oracle Database Concepts 23ai, Chapter 7, "Processes". The section "Background Processes" provides a detailed list and description of mandatory and optional background processes.

2. Oracle Database Concepts 23ai, Chapter 7, "Processes". The description for "Listener Registration Process (LREG)" states it registers information with the listener.

3. Oracle Database Concepts 23ai, Chapter 7, "Processes". The description for "Log Writer Process (LGWR)" states it writes redo log entries to disk.

4. Oracle Database Concepts 23ai, Chapter 7, "Processes". The description for "Database Writer Process (DBWn)" states its primary purpose is to write modified blocks from the buffer cache to data files.

5. Oracle Database Concepts 23ai, Chapter 7, "Processes". The section "Server Processes" explains that these processes fulfill user requests, which includes reading data blocks from disk into the SGA.

The primary function of a database link is to act as a pointer within a local database that defines a one-way communication path to a remote database. This allows users and applications connected to the local instance to access schema objects, such as tables and views, in the remote database's instance as if they were local, subject to privileges. This is precisely what option D describes. It is the most accurate and fundamental definition of a database link's purpose among the choices provided.

A. Oracle Database Gateways (formerly Heterogeneous Services) allow the creation of database links to non-Oracle database systems, making this statement false.
B. A private database link can be created with a CONNECT TO clause specifying a different user and password for the remote database.
C. Any user with the CREATE PUBLIC DATABASE LINK system privilege can create a public database link, not just the SYS user.
E. While any user can use a public database link, their access to data is restricted by the privileges granted to the user that the link connects as on the remote database.

Oracle Database Administrator's Guide, 23ai, "20 Managing Distributed Databases", "Managing Database Links". The introduction states, "A database link is a schema object in one database that enables you to access objects on another database."

Oracle Database SQL Language Reference, 23ai, "CREATE DATABASE LINK". The documentation shows the syntax, including the CONNECT TO clause, and lists the required CREATE PUBLIC DATABASE LINK privilege.

Oracle Database Heterogeneous Connectivity User's Guide, 23ai, "1 Introduction to Oracle Database Gateway". This document describes how to use database links to access non-Oracle systems.

After SHUTDOWN TRANSACTIONAL is issued, the instance refuses new connection attempts (C). Existing sessions remain connected if not currently in a transaction, although they cannot begin new transactions (D). Active uncommitted transactions are allowed to finish naturally—either to a COMMIT (E) or, if users choose, a ROLLBACK; shutdown proceeds only after completion.

A. No instance recovery occurs; the shutdown is clean.
B. Oracle waits for completion, not specifically for the next explicit ROLLBACK; users may commit instead.

1. Oracle Database Administrator’s Guide 23c, “Shutting Down and Starting Up – Shutdown Modes”, Table 10-3 (“TRANSACTIONAL”)

2. Oracle SQLPlus User’s Guide and Reference 23c, “SHUTDOWN Command”, sub-topic “TRANSACTIONAL”

The DBMSAUDITMGMT package provides the necessary procedures for managing the unified audit trail. To purge audit records, administrators can use two primary methods. For automated, periodic purging, DBMSAUDITMGMT.CREATEPURGEJOB is used to schedule a job that runs at specified intervals. For immediate, manual purging of the audit trail up to a certain timestamp, the DBMSAUDITMGMT.CLEANAUDITTRAIL procedure is executed. Both methods require a privileged user with the AUDITADMIN role.

A. Purging is based on the age of the audit records (timestamp), not on whether they have been viewed or accessed.
C. Purging is a privileged administrative task, not restricted to the owner of a specific audit policy. It affects the entire audit trail.
E. The procedure DELETEAUDITRECORDS does not exist in the DBMSAUDITMGMT package for this purpose; the correct procedure is CLEANAUDITTRAIL.

Oracle Database 23ai Security Guide, "Configuring and Administering Auditing", section "Purging Audit Records".

Oracle Database 23ai PL/SQL Packages and Types Reference, "DBMSAUDITMGMT", sections "CREATEPURGEJOB Procedure" and "CLEANAUDITTRAIL Procedure".

Oracle Database Metrics are statistical values collected by the database kernel, providing insight into system performance. They are typically measured as rates per unit of time (second), per transaction, or per session. These metrics form the foundation of Oracle's performance monitoring infrastructure. The database can be configured with thresholds for these metrics; when a threshold is crossed, a server-generated alert is created. This allows for proactive performance management by automatically detecting and notifying administrators of potential issues.

B. Metrics are the data used for monitoring; the notification system is a separate component that acts on alerts generated from metrics, but they are not part of it.
D. This incorrectly states metrics are part of the EM notification system. Metrics are generated by the database; EM is a tool that consumes and acts on them.
E. Metrics are generated by the database itself, not "built in" Oracle Enterprise Manager. EM is a management tool that collects and displays these metrics.

1. Oracle Database 23ai, Performance Tuning Guide, Chapter 5, "Automatic Performance Diagnostics". It defines metrics as "statistics that are measured over a time interval."

2. Oracle Database 23ai, Administrator's Guide, Chapter 8, "Monitoring the Database", Section "Managing Server-Generated Alerts". It states, "The Oracle Database server provides a monitoring infrastructure that is based on metrics... When a metric value crosses a server-defined threshold, the server generates an alert."

3. Oracle Database 23ai, Reference, "V$SYSMETRIC". This view description details the system-level metrics captured by the database, such as 'Physical Reads Per Sec' and 'User Commits Per Sec'.

In a multitenant environment, ALTER SYSTEM statements that affect instance-wide, shared resources (like the SGA or redo log files) must be executed from the root container. However, statements that affect only a specific Pluggable Database (PDB) can be run from within that PDB. ALTER SYSTEM CHECKPOINT when run from a PDB defaults to a local checkpoint for that PDB only. Similarly, ALTER SYSTEM ENABLE/DISABLE RESTRICTED SESSION when run from a PDB puts only that specific PDB into restricted mode, not the entire instance.

B. FLUSH BUFFERCACHE affects the entire System Global Area (SGA), which is shared by all PDBs, and thus must be run from the root container.
C. SWITCH LOGFILE affects the instance-wide redo log files, which are a shared resource for the entire CDB, and must be run from the root.

1. Oracle Database 23ai, SQL Language Reference, "ALTER SYSTEM". The documentation includes a section "Usage in a Multitenant Environment" which specifies which clauses are permissible within a PDB.

2. Oracle Database 23ai, Multitenant Administrator's Guide, Chapter 3, "Administering a CDB", Section "Executing ALTER SYSTEM Statements in a CDB". This section explicitly lists which ALTER SYSTEM clauses are allowed or disallowed in a PDB. It confirms that CHECKPOINT (as a local checkpoint) and ENABLE/DISABLE RESTRICTED SESSION are allowed.

Optimizer statistics, which are crucial for generating efficient execution plans, are collected in two primary ways. First, Oracle Database includes an automated maintenance task, "auto optimizer stats collection," that runs during predefined maintenance windows to gather stale or missing statistics. Second, for more granular control or immediate updates, a Database Administrator can manually collect statistics at various levels (e.g., table, schema, database) using the procedures within the DBMSSTATS PL/SQL package, such as GATHERTABLESTATS or GATHERSCHEMASTATS.

B. While Real-Time Statistics exist for bulk loads, general DML operations do not trigger real-time statistics collection; it is primarily a scheduled or manual task.
D. The Statistics Advisor analyzes existing statistics and provides recommendations for improvement; it does not perform the collection itself.
E. The Automatic Workload Repository (AWR) collects performance metrics and workload data, not the optimizer statistics used for query planning.

Oracle Database 23ai SQL Tuning Guide, "Managing Optimizer Statistics", section "Automatic Optimizer Statistics Collection".

Oracle Database 23ai SQL Tuning Guide, "Managing Optimizer Statistics", section "Manual Optimizer Statistics Collection".

Oracle Database 23ai PL/SQL Packages and Types Reference, "DBMSSTATS", for a full list of manual gathering procedures.

The V$OPTION dynamic performance view lists database features and options that are installed and enabled. To validate that a database is running in pure unified auditing mode (i.e., has been migrated), you query this view. If the parameter 'Unified Auditing' has a value of 'TRUE', it confirms the feature is fully enabled at the database kernel level. This is the definitive method for verification.

B: lsinventory is an OPatch utility that queries the Oracle Home software installation, not the runtime configuration of a database. C: DBAUNIFIEDAUDITOPTION shows which audit policies are enabled, but does not confirm the database is in pure unified auditing mode. D: The DBMSAUDITMGMT package is used for managing audit data and policies, not for verifying the database's auditing mode.

1. Oracle Database Security Guide, 23ai, Chapter 19, "Introduction to Auditing", Section "Verifying That Unified Auditing Is Enabled". The guide states: "To verify that unified auditing has been enabled, query the V$OPTION view."

2. Oracle Database Reference, 23ai, "V$OPTION". This document describes the view and lists 'Unified Auditing' as one of the parameters it displays.