1Z0-1094-24 Sample Questions & Answers

The ORA-65169 error, 'missing or invalid password in database link,' is commonly encountered during remote cloning when the database link setup is incorrect. A critical step is creating a common user in the target CDB that has the CREATE PLUGGABLE DATABASE system privilege. The database link in the source CDB must then connect to the target CDB using this specific user's credentials. Failure to create this user or grant the necessary privilege will cause the remote clone operation to fail.

The most efficient approach for this scenario is ELT (Extract, Load, Transform). Autonomous Data Warehouse is a powerful, highly optimized query engine. By loading the raw data into staging tables first, you can leverage the massively parallel processing capabilities of ADW to perform the complex joins and transformations using SQL. This is significantly more scalable and performant than pulling all the data to a separate mid-tier transformation engine (ETL). OCI Data Integration services are optimized for this ELT pattern.

The ZDM_RMAN_CHANNEL_COUNT parameter in the ZDM response file controls the number of parallel RMAN channels used for the backup and restore operations. The default value is often low. To fully utilize a high-speed network link like a 1 Gbps FastConnect, increasing this value will create more parallel streams for the data transfer to OCI Object Storage, significantly improving the overall performance of the initial data transfer phase. The other parameters are for configuration, not performance tuning of the transfer.

OCI Vault is a managed key management service that securely stores and controls access to encryption keys. Integrating the database with OCI Vault ensures the TDE master keys are managed outside the DB System's file system in a FIPS 140-2 Level 3 certified hardware security module.

Oracle Key Vault (OKV) is a centralized key management solution. By deploying OKV on a separate, hardened compute instance, you can manage the TDE master keys centrally and ensure they are not stored on the database server itself, meeting the security requirement.

The SQL Developer Migration Wizard requires a migration repository to store its metadata. This repository is created as a collection of tables, views, and other objects within a dedicated user schema in the target Oracle database. The wizard prompts for credentials for a user (which it can create) to install this repository before the migration process begins.

When using ESTIMATE_ONLY=Y with Data Pump Export, the estimate of the space that would be consumed is provided in Oracle database blocks, not in bytes, megabytes, or gigabytes. The user must then multiply this number by the database block size to get the estimate in bytes.

Transportable Tablespaces (TTS) is a physical migration method that copies data files directly. Because of this, it is highly sensitive to differences in the time zone file version between the source and target. If there is a mismatch, data of the TIMESTAMP WITH TIME ZONE datatype can become corrupted or misinterpreted after the tablespaces are plugged in. This requires either upgrading the time zone file on one of the databases to match the other or taking corrective actions post-migration. Logical methods like Data Pump handle the conversion automatically.

In a ZDM logical online migration, GoldenGate replication must be started before the initial data load (Data Pump export) begins. This is critical to capture any transactions that occur on the source database while the lengthy Data Pump export is running. By starting replication first, ZDM ensures that once the initial load is complete, GoldenGate can apply all the captured interim changes to bring the target database into sync with the source before the final switchover.

This statement is false. The Oracle Database Cloud Backup Service is available for all supported Oracle Database editions, including Enterprise Edition, Standard Edition, and Standard Edition 2. It requires installing the Oracle Database Cloud Backup Module on the source database server.

When restoring a database to a new host where no information about the database exists, RMAN needs the control file to find the metadata about the database structure and the location of the backup pieces. The correct procedure is to start the instance in NOMOUNT state, restore the control file first (RESTORE CONTROLFILE FROM...), mount the database, and then execute RESTORE DATABASE. Without the restored control file, RMAN has no catalog of the backups and cannot locate the backup pieces, even with correct credentials.