1z0-067 Practice Exam Questions with Answers Upgrade Oracle9i/10g/11g OCA to Oracle Database 12c OCP Certification

Partitions of purchase_order_items are assigned unique names based on a sequence.

The purchase_orders and purchase_order_items tables are created with four partitioneach.

purchase_order_items table partitions exist in the same tablespaces as the purchase_orders table partitions.

The purckase_order_:teks table inherits the partitioning key by duplicating the key columns from the parent table.

Partition maintenance operations on the purchase_order_items table require disabling the foreign key constraint.

ASM disk groups with ASM disks consisting of Exadata Grid Disks.

ASM disk groups with ASM disks consisting of LUNS on any Storage Area Network array

ASM disk groups with ASM disks consisting of any zero padded NFS-mounted files

Database files stored in ZFS and accessed using conventional NFS mounts.

Database files stored in ZFS and accessed using the Oracle Direct NFS feature

Database files stored in any file system and accessed using the Oracle Direct NFS feature

ASM disk groups with ASM disks consisting of LUNs on Pillar Axiom Storage arrays

Two channels are allocated and two copies of the backup set are taken in parallel in both locations

Two channels are allocated and backup pieces for the backup set are created in both the specified destinations

The default channel is allocated and the backup set is created in only one destination

Two channels are allocated and a copy of the backup set is taken in the location specified by CHANNEL 2

Only a single partitioning key column can be specified.

All DML statements must use partition-extended syntax.

The same physical attributes must be specified for each partition.

Unique local indexes cannot be created on a system-partitioned table.

Traditional partition pruning and partitionwise joins are not supported on these tables.

because pga_aggregate_target is not set

because statistics_level is set to basic

because memory_target and memory_max_target cannot be equal

because sga_target and memory_target are both set

Both orcl1 and orcl2 are automatically added to the Oracle Restart configuration.

All database listeners running from the database home are automatically added to the Oracle Restart configuration.

The srvct1 add database command must be used to add orcl1 and orcl2 to the Oracle Restart configuration.

The crsct1 start has command must be used to start software services for Oracle Automatic Storage Management (ASM) after the "Oracle Grid Infrastructure for a standalone server" installation is complete.

All databases subsequently created by using the Database Configuration Assistant (DBCA) are automatically added to the Oracle Restart configuration.

ALTER SYSTEM SET DB_CACHE_SIZE=50M;

ALTER SYSTEM SET DB_16K_CACHE_SIZE=0;

ALTER SYSTEM SET DB_16K_CACHE_SIZE=10M;

ALTER SYSTEM SET DB_8K_CACHE_SIZE=10M;

ALTER SYSTEM SET DB_4K_CACHE_SIZE=10M;

You cannot export data from a remote database.

You can rename tables during import.

You can overwrite existing dump files during export.

You can compress data but not metadata during export.

A unified audit trail captures audit information from unified audit policies and audit settings.

Unified auditing is enabled by executing make-fins_rdbms.mk uniaud_onioracle ORACLE_HOME=SORACLE_HOME.

Audit records are created for all users except sys.

Audit records are created only for the DML and DDL operations performed on database objects.

Unified auditing is enabled by setting the audit_trail parameter to db, extended.

A unified audit trail resides in a read-only table in the audsys schema in the system tablespace.

The pending area is automatically submitted when creating plan directives.

The procedure must be executed before creating any plan directive.

The sys_group group is not included in the resource plan.

The other_groups group is not included in the resource plan.

Pending areas can not be validated until submitted.

Queries may be performed on columns that have the NO SALT option.

Data remains encrypted when read into the buffer cache.

Redo generated by DML remains encrypted.

UNDO generated by DML remains encrypted if the UNDO tablespace is encrypted.

Data remains encrypted when read into the PGA for direct path reads.

The amount of undo retained is user controlled.

They can be used only for nonpartitioned tables.

Fragmentation is minimized by using variable-sized chunks.

They support random reads and writes of encrypted LOB data.

An unplugged PDB can be plugged into the same or another container database (CDB).

PDB data files are automatically removed from disk.

A PDB must have been opened at least once after creation.

A PDB must be in closed state before it can be unplugged.

A PDB must be in MOUNT state before it can be unplugged.

Block change tracking must be enabled before executing this command.

The database must be running in archivelog mode for the successful execution of this command.

A complete database backup must exist before executing this command.

The command checks for blocks containing all zeros, an invalid checksum, or a corrupt block header.

The command checks for blocks that contain a valid checksum and matching headers and footers, but that has logically inconsistent contents.

Fast Recovery Area must be enabled for the database

The EXECUTE privilege must be granted to a user on the DBMS_FLASHBACK package

Undo retention guarantee must be configured for the database

A supplemental log must be enabled for the primary key

Row movement must be enabled

It restores all data files from the specified time, and then applies the redo logs

It restores all data files, redo log files, and control files, and then applies the redo logs up to the specified time

It restores all data files and control files from the most recent backup taken before the “until time”, and then recovers up to the “until time” using any restored archieve logs that are needed to complete the task

It restores the control file and all data files from the most recent backup, and then applies the redo logs up to the “until time”.

You must take the tools01.dbf data file offline.

You must ensure that the database is mounted or open.

You must use an incremental level-1 backup to restore blocks.

You must configure a block change tracking file.

You must have full or level-0 backups to restore blocks.

1,2,3,4,5,6,8,9, and 10

1,2, 4,5,6,7, and 8

1, 2, 3, 8, 9, and 10

1, 2, 4, 5, 7, 8, 9, and 10

1, 2, 4, 5, 6, and 7

Compare Period ADDM report

AWR Compare Period report

Active Session History (ASH) report

taking a new snapshot and comparing it with a preserved snapshot

1, 2, 5, 3, 6, 4

1, 2, 3, 5, 6, 4

2, 1, 5, 7, 3, 4

2, 1, 5, 6, 7, 4, 3

Scheduler jobs for a PDB can be defined only at the container database (CDB) level.

A job defined in a PDB runs only if that PDB is open.

Scheduler attribute setting is performed only at the CDB level.

Scheduler objects created by users can be exported or imported using Data Pump.

Scheduler jobs for a PDB can be created only by common users.

Visibility of the ORA_ARCHIVE_STATE column is controlled by the row archival visibility session parameter.

The ORA_ARCHIVE_STATE column is updated manually or by a program that can reference activity tracking columns, to indicate that a row is no longer considered active.

The row archival visibility session parameter defaults to all rows.

The ORA_ARCHIVE_STATE column is visible if it is referenced in the select list of a query.

The ORA_ARCHIVE_STATE column is updated automatically by the database based on activity tracking columns, to indicate that a row is no longer considered active.

It lists failures only if RMAN is connected to a PDB.

It lists failures for the CDB and all the PDBs in this CDB.

It lists failures for a PDB only when RMAN is connected to a recovery catalog.

It lists failures only for the CDB root database.

Creating and dropping tables in the datafile being moved

Performing file shrink of the data file being moved

Querying tables in the datafile being moved

Performing Block Media Recovery for a data block in the datafile being moved

Flashing back the database

Executing DML statements on objects stored in the datafile being moved

An error is returned because the retention period cannot be reduced

All historical data older than two years, if any, is archived to flashback logs and the flashback archive is set to new retention time

All historical data older than two years, if any, is purged from the flashback archive FDA1.

All the flashback data archives are purged and the subsequently created flashback archives are maintained for two years

Compressed backups can only be written to media.

Binary compression creates performance overhead during a backup operation.

Unused blocks below the high-water mark are not backed up.

Compressed backups cannot have section size defined during a backup operation

It works only for locally managed tablespaces.

The statistics_level parameter is set to all when any of the PDBs is reopened.

The statistics_level parameter is set to all only for PDB2 when it is reopened.

The statistics_level parameter is set to all when the root database is restarted.

The statement is ignored because there is no SPFILE for a PDB.

Only one window can be open at one time.

Consumer groups are associated with windows.

Windows work with job classes to control resource allocation.

A database service name must be provided during window creation.

The Resource Manager can automatically start windowed jobs or change resource allocation among windowed jobs.

loss of a non-critical data file

loss of a control file

physical data block corruption

logical data block corruption

loss of an archived redo log file

Reduced logical I/O

Reduced virtual memory utilization

Improved Serial Execution performance

Reduced physical I/O

Reduced CPU utilization

All metadata pertaining to backups and archived redo log files that have exceeded the age set by the RMAN retention policy are deleted from the repository.

All backups that have exceeded the age set by the RMAN retention policy are deleted.

All metadata, for backups and archived redo log files that are recorded in the repository but do not exist on disk or media, is deleted.

All backups and archived redo log files that are not required for the recovery are deleted and the repository is updated.

The data is decrypted during SORT and JOIN operations.

The data remains encrypted when it is read into memory.

The data remains encrypted when it is stored in the redo logs

The data remains encrypted in the UNDO tablespace provided that the UNDO tablespace was created with the encryption option enabled.

It can contain a nested chain of jobs.

It can be used to implement dependency-based scheduling.

It cannot invoke the same program or nested chain in multiple steps in the chain.

It cannot have more than one dependency.

It can be executed using event-based or time-based schedules.

It helps to reduce disk space used to store an audit trail in a database.

It guarantees zero-loss auditing.

It reduces overhead on a database caused by auditing, by having a single audit trail.

An audit trail cannot be modified because it is read-only.

It automatically audits Recovery Manager (RMAN) events.