1z0-083 Sample Questions Answers

The UNDO TABLESPACE clause is always required when no connection exists to the recovery catalog and the TARGET database is closed.

RMAN disk-based backups of the database to be duplicated can be used by the auxiliary instance.

The UNDO TABLESPACE clause is always required when no connection exists to the TARGET instance.

The UNDO TABLESPACE clause is never required.

RMAN "pushes" the backups of the database to be duplicated over the network to the auxiliary instance.

It succeed

It fails because no parallel channels are allocated for the auxiliary databa

It fails because connection to the AUXILIARY instance must be as SYSD

Itsucceeds only if the target database is greater than 40

No catalogued backup of the TARGET is used to duplicate the databa

If an RMAN BACKUP VALIDATE command takesroughly the same time as an actual backup, then both read and write I/O are likely bottlenecks.

Setting DBWR_IO_SLAVES to a non zero value can improve backup performance when using synchronous I/O.

If an RMAN BACKUP VALIDATE command takes noticeably lessthan an actual backup, then write I/O is a likely bottleneck.

If an RMAN BACKUP VALIDATE command takesroughly the same time as an actual backup, then read I/O is a likely bottleneck.

Data files with a high value in V$BACKUP_SYNC_IO.DISCRETE_BYTES_PER_SECOND are a potential performance bottleneck when synchronous I/O is used.

Setting DBWR_IO_SLAVES to a non zero value can improve backup performance when using asynchronous I/O/

Data files with a high value in V$BACKUP_ASYNC_IO.SHORT_WAITS are a potential performance bottleneck when asynchronous I/O is used.

using Database Replay

using SQL Developer

using Oracle Data Pump

using operating system file copy utilities

using Database Upgrade Assistant

using the CREATE TABLE AS SELECT SQL statement

The database must have FLASHBACK DATABASE ON to perform Database Point-in-Time Recovery.

The database must be in MOUNT state when performing Database Point-in-Time Recovery.

Database Point-in-Time Recovery is performed by the Managed Recovery Process (MRP)

The Database must be in ARCHIVE LOG mode.

The target point for the recovery must be specified as a stime or System Change Number (SCN).

The database must be open RESETLOGS after Database Point-in-Time Recovery.

All archive redo log files are automatically copied to the duplicate database.

The duplicate database has the same directory structure as the source database.

The duplicate database is created by using the backups created during the execution of

he duplicate command.

The password file and SPFILE for the duplicate database dup1 are created in their respective default locations.

The duplicate database is created without using RMAN backups and prod1 is allowed to remain open during duplication.

By default, members of the OSASM group can access Automatic Storage Management and RDBMS instances.

The primary group for the Oracle Grid Infrastructure and Oracle Database owners must be the Oracle Inventory group.

The Oracle Grid Infrastructure installation must be owned by the grid user.

The Oracle Grid Infrastructure owner owns Oracle Restart and Oracle Automatic Storage Management binaries.

The Oracle Grid Infrastructure owner must have OSOPER, OSBACKUPDBA, and OSKMDBA as secondary groups.

The same OSDBA group must be used for Automatic Storage Management and the Oracle Database.

Uncommitted transactions in PDB1 have been rolled back.

PDB1 is closed.

Uncommitted transactions in CDB1 and PDB1 have been rolled back.

CDB1 is shut down.

CDB1 is in MOUNT state

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.

A supplemental log must be enabled for the primary key.

Decreasing PCTUSED

Decreasing PCTFREE

Increasing the number of DBWN process

Using Automatic Segment Space Management (ASSM)

Increasing db_buffer_cache based on t he V$DB_CACHE_ADVICE recommendation

A direct upgrade can be performed only from the immediately preceding Oracle Grid Infrastructure version.

The newer version is installed in a separate Oracle Grid Infrastructure home on the same server as the existing version.

An existing Oracle base can be used.

The upgrade process will automatically install all mandatory patches for the current version of Oracle Grid Infrastructure.

Existing Oracle Database instances must be shut down before starting the upgrade.

Only the grid user can perform the upgrade.

They are generated if STATISTICS_LEVEL is set to TYPICAL.

They are always created manually.

They are always created automatically.

They are generated if STATISTICS_LEVEL is set to BASIC.

They are generated if STATISTICS_LEVEL is set to ALL.

They can be retained forever.

Reduced logical I/O

Reduced virtual memory utilization

Improved Serial Execution performance

Reduced physical I/O

Reduced CPU utilization

Decreased use ofstorage to store audit trail rowsin the database.

It improves overall auditing performance.

It guarantees zero-loss auditing.

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

It automatically audits Recovery Manager (RMAN) events.

It is enabled by performing a software-only Oracle Database installation and then running the roohctl ¬enable script.

It requires the Rapid Home Provisioning service.

Its configuration data and log files reside in subdirectories under the Oracle home.

It is enabled by performing an Oracle Database installation with database creation and then running the roohctl -enable script.

It contains an image that can be distributed across multiple servers.

Recovery begins from the beginning of the CURRENT redo log group.

Recovery begins from the last checkpoint position that was calculated by the Database Writer before instance failure.

Recovery begins from the start of any ACTIVE redo log group or the start of the CURRENT log group if no other group is ACTIVE.

Recovery reads redo until the end of the redo thread. SMON rolls back any dead transactions, and then the datanase is opened.

Recovery begins from the last checkpoint position that was recorded in the control file by the checkpoint process (CKPT).

Recovery reads redo until the end of the redo thread, and then opens the database. SMON then rolls back any dead transactions.

TheC# # B_ADMIN user can perform all back up and recovery operation susing RMAN only.

The C # # C_ADMIN user can perform the data guard operation with Data Guard Broker.

The C # # A_ADMIN user can perform wallet operations.

The C # # D_ADMIN user can perform backup and recovery operations for Automatic Storage Management (ASM).

The C # # B_ADMIN user can perform all backup and recovery operations using RMAN or SQL* Plus.

all backups prior to 10th of August

all backups prior to 22nd of August

all backups prior to 20th of August

all backups prior to 24th of August

all backups prior to 17th of August

If Automatic Memory Management is enabled, no memory advisors are available.

If Automatic Memory Management is enabled, the Shared Pool Advisor and Buffer Cache Advisor are available to set the maximum size for these individual System Global Area components.

All memory advisors use data from Automatic Workload Repository.

If Automatic Shared Memory Management is enabled, both the SGA Advisor and PGA Advisor are always available.

If Manual Shared Memory Management is enabled, only the Shared Pool Advisor and Buffer Cache Advisor are available.

They are never considered obsolete by RMAN.

They can optionally be written to a fast recovery area (FRA).

All archive logs are retained after an archival backup is taken, until the next archival backup is taken of the same database.

Archive logs are retained if they are necessary to allow the database to be recovered to a consistent state when an archival backup is restored.

The SPFILE is included in the archival backup.

Use of a recovery catalog is always required to support the creation and use of archival backups. G)The ARCHIVAL attribute for a backup overrides the RMAN retention policy.

3,4,6

2,3,4,5,6,7

1,3,4,6,8

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

All files in any previous FRA that have not yet been backed up, are backed up.

All files in the current fast recovery area (FRA) that have not yet been backed up, are backed up. C)All files in the current FRA that have been backed up already, are backed up.

All Oracle recovery files normally written to the FRA and which have been backed up already to the current FRA, are backed up.

All files in any previous FRA that have been backed up already, are backed up.

All Oracle recovery files normally written to the FRA and which have not yet been backed, are backed up.

All Oracle recovery files normally written to the FRA and which have been backed up already to in any previous FRA, are backed up.

The inserts on USER1.EMP remain uncommitted when the session connected to PDB2.

The inserts on USER1.EMP were committed when the session inserted a row into USER2. DEPT.

The insert on USER2.DEPT fails because of the active transaction in the parent container.

The insert on USER2.DEPT is a recursive autonomous transaction by the child session and is committed.

The inserts on USER1.EMP were rolled back when the session connected to PDB2

The insert on USER2.DEPT is uncommitted.

The inserts on USER1.EMP were committed when the session connected to PDB2.

A lost PFILE can be re-created from alert.log using SQL*PLUS.

A lost index tablespace can be re-created without performing any recovery.

A lost password file can be manually re-created with the orapwd utility.

A lost password file can be re-created with SQL*PLUS.

A lost SPFILE can be recovered from memory using SQL*PLUS.

A lost TEMPFILE must always be re-created manually.

Tracking the most recent read time for a table segment in a user tablespace

Tracking the most recent write time for a table segment in a user tablespace

Tracking insert time by row for table rows

Tracking the most recent write time for a table block

Tracking the most recent read time for a table segment in the SYSTEM tablespace

Tracking the most recent write time for a table segment in the SYSAUX tablespace Correct

Tablespaces from different PDBs with identical names must be backed up by connecting RMAN separately to each PDB to back up the tablespaces.

The BACKUP DATABASE command will create a pluggable database (PDB) backup when RMAN is connected to a PDB.

SPFILE backups can be created while connected to an application root PDB.

The BACKUP DATABASE PLUS ARCHIVE LOG command will back up archive logs when RMAN is connected to a PDB.

The BACKUP PLUGGABLE DATABASE command can be used to back up CDB$ROOT.

It always analyzes all schemas in the database.

It can recommend changes to improve the statistics gathering process.

It can be run only manually.

It runs automatically every night by default. E) It can be run only automatically.

when any archived log from, before, or after the most recent backup is corrupt.

after losing all copies of the control file

after losing an archived log from after the most recent backup

after losing an archived log from before the most recent backup

after losing the SYSTEM tablespace

redo logs

control files

all data dictionary metadata

user-defined PL/SQL packages

temporary tablespaces

mandatory Oracle-supplied PL/SQL packages

undo tablespaces

Create SQL plan directives for each of the regressed statements.

Use The SQL Tuning Advisor for each of the regressed statements.

Create an adaptive execution plan for each of the regressed statements

Use the SQL Access Advisor for each of the regressed statements.

It can be run only manually.

It is part of the DBMS_ADVISOR package.

It can recommend changes to improve the statistics gathering process.

It always analyzes all schemas in the database.

It runs automatically every night by default.

It is part of the DBMS_STATS package.

Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to CDB$ROOT gathers object statistics in all open PDBs except PDB$SEED.

Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to a PDB opened in read/ write mode gathers object statistics for that PDB.

Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to CDB$ROOT gathers object statistics only in CDB$ROOT.

System statistics can be gathered only while connected to CDB$ROOT.

Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to CDB$ROOT gathers object statistics in all open pluggable databases (PDBs)

All metrics are instance related.

Cleared stateful alerts are displayed by querying DBA_ALERT_HISTORY.

A space usage management alert is automatically cleared after the underlying problem is resolved

They are generated by SMON when a tablespace is 97% full.

Metrics are statistical counts for a specific unit.

STATISTICS_LEVEL must be set to ALL to generate alerts.

Automatic conversion of endianess occurs.

The source and target platforms must have the same endianess.

The source PDB can be in MOUNT or OPEN state.

The source PDB must not be an application root.

The source PDB must be in MOUNT state.

A backup of the PDB must exist, taken using the BACKUP command with the To PLATFORM clause.

an operating system user to own this installation

the Oracle Inventory group oinstall

an operating system account called grid

a group called dba

the installation of Oracle ASMLIB

Application-common Transparent Security Data Protection (TSDP) policies can be created only if all the PDBs in the application container are closed.

Application-common TSDP policies are always container specific.

Application-common OLS policies can be created only if all the PDBs in the application container are closed.

Unified auditing can be automatically synchronized to all application PDBs in an application container.

Fine-grained auditing (FGA) policies in an application root are automatically synchronized to all application PDBs contained in the application container when they are updated.

to specify a default tablespace in a PDB cloned from another PDB in the same CDB

to exclude all tablespaces except SYSTEM, SYSAUX, and TEMP when plugging in a PDB

to include specific user tablespaces only when relocating a PDB

to specify the list of user tablespaces to include when moving a non-CDB to a PDB

to exclude a temp tablespace when plugging in a PDB

to specify the list of tablespaces to include when creating a PDB from the CDB seed

Duplication can be done by having the auxiliary database instance pull backup sets from the target database instance.

A connection to an auxiliary instance is always required.

A subset of the target database can be duplicated.

A new DBID is always created for the duplicated database.

A connection to the recovery catalog instance is always required.

A backup of the target database is always required.

Duplication can be done by having the target database instance push copies to the auxiliary database instance.

Execute FLASHBACK PLUGGABLE DATABASE PDB1 TO RESTORE POINT R1by using RMAN while connected to PDB1.

Execute FLASHBACK PLUGGABLE DATABASE PDB1 TO RESTORE POINT R1by using SQL while connected to PDB1.

Execute FLASHBACK PLUGGABLE DATABASE PDB1 TO RESTORE POINT R1by using SQL while connected to CDB$ROOT.

Execute FLASHBACK PLUGGABLE DATABASE PDB1 TO RESTORE POINT R1by using RMAN while connected to CDB$ROOT.

This cannot be done due to the lack of a clean restore point.

mounting disk groups

acting as an I/O server to read data file blocks from ASM disks on behalf of database server processes

managing extent allocation for Oracle database segments

managing Allocation Units (AUs) for disk group content

managing space allocation for Oracle ASM files

acting as an I/O server to write data file blocks to ASM disks on behalf of Database Writer processes (DBWn)

It recompiles all stored PL/SQL code by using utlrp.sql.

It empties the RECYCLE BIN.

It performs prerequisite checks to verify if the Oracle database is ready for upgrade.

It sets all user tablespaces to “read-only” before starting the upgrade.

It removes the AUDSYS schema and the AUDIT_ADMIN and AUDIT_VIEWER roles

It increases tablespace size, if required, to meet upgrade requirements.

Online Redo Log backups can be created while connected to CDB$ROOT

Control file backups can be created while connected to CDB$ROOT.

The BACKUP TABLESPACE command can back up a pDB tablespace even if RMAN is connected to CDB$ROOT.

Archived Redo Log backups can be created while connected to PDB

Control file backups can not be created while connected to a PDB

to allow database duplication without a connection to the target instance.

to store backup metadata that would cause the controlfile to become too large.

to store backups that would cause the controlfile to become too large.

to report on the database schema at an earlier point in time.

to allow database duplication without a connection to the auxiliary instance.

It is used in both clustered and non-clustered environments.

You can add and remove components from an Oracle Restart configuration with Server Control (SRVCTL) commands.

It runs from the Oracle Grid Infrastructure home.

If you shut down a database instance with SQL*Plus, Oracle Restart interprets this as a database failure and attempts to restart the instance.

The Server Control (SRVCTL) utility can be used to start and stop Oracle Restart.

It can manage Oracle Database instances, Oracle Net Listeners, and Oracle Automatic Storage Management instances.

Transparent encryption of backups uses an encryption wallet.

Image copy backups can be created by using password encryption.

A password encryption of backups uses the password while creating and restoring backups.

Encrypted backups can only be written to disk.

A database uses the same encryption key for every encrypted backup.

Tune individual SQL statements using the SQL Tuning Advisor.

Identify poorly tuned SQL statements using Automatic Database Diagnostic Monitor.

Test the application as a whole using tuned SQL statements.

Test tuned SQL statements one at a time for all statements in the application.

Identify poorly tuned SQL statements using the SQL Tuning Advisor.

Tune SQL statements as a group using the SQL Tuning and SQL Access Advisors.

Media Management messages for SBT devices are always written to sbtio.log.

RMAN error stacks should be read from the bottom up as that is the order in which errors are generated.

RMAN error stacks should be read from the top down as that is the order in which errors are generated.

The RMAN LOG command line clause causes output issued during RMAN command compilation to be written to a log file and to standard output.

The RMAN LOG command line clause causes output issued during RMAN command compilation to be written to a log file only.

Media Management messages for SBT devices are written to an Oracle trace file.

connecting to the target database and a recovery catalog to execute the duplicate command

creating a password file for an auxiliary instance

connecting to an auxiliary instance

matching the database identifier (DBID) of the source database and the duplicate database

creating an SPFILE for the target database

when the duplicate ... from active database command contains the section size clause

when you perform active database duplication on a database with flashback disabled

when you specify set encryption before the duplicate ... from active database command

when the number of auxiliary channels allocated is equal to or greater than the number of target channels

when you perform active database duplication on a database that has readonly tablespaces

To use it, Flashback Database must be enabled.

A block being recovered is not accessible.

It cannot repair logical corruption.

It can be performed on noncorrupt blocks.

The target database for which one or more blocks are to be recovered must be in the OPEN state.

The data file containing the block being recovered remains online.

Re-create or migrate the password file to the Oracle Database 12c format

Grant the SYSBACKUP, SYSDG, and SYSKM privileges to the intended users.

Copy the password file from a sample file in the DBS dierectory

Assign appropriate operating system groups to SYSBACKUP, SYSDG, and SYSKM.

PDB-level resource plans can limit uncommitted UNDO per consumer group.

A PDB-level resource plan can limit session PGA memory.

A CDB-level resource plan can limit PDB UNDO use.

A CDB-level resource plan can limit session CPU utilization.

A CDB-level resource plan is mandatory when using PDB-level resource plans.

A CDB-level resource plan can limit PDB CPU utilization

It is a set of recommendations by the optimizer to change the access methods used.

It is auxiliary information collected by the optimizer for a SQL statement to eliminate estimation error.

It is a set of recommendations by the optimizer to restructure a SQL statement to avoid suboptimal execution plans.

It is auxiliary information collected by the optimizer for a SQL statement to help use better joins orders.

It is a set of recommendations by the optimizer to create new indexes.

You can

You can

You can

You can

You can

It succeeds and needs to be enabled to capture all SQL statements that require either the specified privileges or any privilege granted to the HR_ADMIN or OE_ADMIN role.

It fails because the command does notspecify when the unified audit policy should be enforced.

It succeeds and starts capturing only successful SQL statements for all users who have either the specified privileges or roles granted to them.

It fails because system privileges cannot be granted with roles in the same audit policy.

poorly trained users who do not commit transactions

the number of tablespaces containing tables updated by a transaction

issuing multiple savepoints during a transaction

the number of data files containing extents belonging to tables updated by a transaction

poorly written SQL

CDB1 and CDB2 must be in shared undo mode.

A common user must exist in CDB2 with the CREATE PLUGGABLE DATABASE privilege.

All transactions in HR_PDB1 of CDB1 must commit before the cloning process starts.

Cloning HR_ROOT automatically clones HR_PDB1.

The HR_PDB1clone created in CDB2 will be in mount state when cloning ends.

oracle will be an owner of the Oracle Inventory.

oracle must be the owner of every Oracle Database installation.

oracle can own an Oracle Database installation but not an Oracle Grid Infrastructure installation.

oracle will be granted the SYSASM privilege when installing the Oracle Database software.

The user account, oracle, and group, oinstall, can be used for all Oracle software installations.

the backup retention policy

the backup optimization policy

the DB_CREATE_ONLINE_LOG_DEST_n parameter setting

the archived log deletion policy

the DB_RECOVERY_FILE_DEST parameter setting

using guaranteed UNDO retention

It fails because PDB$SEED is in MIGRATE state.

Only CDB$ROOT, PDB$SEED, and PDB1 are upgraded.

Only CDB$ROOT, PDB$SEED, and PDB2 are upgraded.

It fails because PDB2 is not in UPGRADE state.

CDB$ROOT, PDB$SEED, PDB1, and PDB2 are upgraded.

Only CDB$ROOT and PDB$SEED are upgraded.

Automatic block repair can repair blocks with no standby database if DB_BLOCK_CHECKING = TRUE.

Real-Time Query must be enabled on a physical standby database for automatic block repair to be done on that physical standby database.

Real-Time Query must be enabled on a primary database for automatic block repair to be done on any of its physical standby databases.

It is not possible for media corrupt blocks.

Real-Time Query must be enabled on a physical standby database for automatic block repair to be done on its primary database.

If an RMAN command fails, the output will only identify the command that failed.

Some messages in the error stack are not errors.

If an RMAN command fails, the output will identify the channel ID where the failure occurred. D)Media Management errors appear as a line with "Additional information" and a number.

Media Management errors appear as a line with "sbtio" and a number.

Media Management errors appear as a line with "sbtio".

Re-enableredactionpoliciesthatuseFULLdataredaction.

Re-createredactionpoliciesthatuseFULLdataredaction.

Re-connect the sessions that access objects with redaction policies defined on them.

Flushthesharedpool.

Restart the database instance. Correct

All AWR tables belong to the SYSTEM schema.

The AWR data is stored in memory and in t he database.

The snapshots collected by AWR are used by the self-tuning components in the database

AWR computes time model statistics based on time usage for activities, which are displayed in the v$SYS time model and V$SESS_TIME_MODEL views.

AWR contains system wide tracing and logging information.

ADDM can recommend shrinking the buffer cache.

ADDM can recommend extending the buffer cache.

By default, MMON creates an AWR snapshot every 30 minutes.

ADDM performs its analysis only when a DBA requests it.

By default, AWR snapshots are automatically purged after eight days.

AWR snapshots must be deleted when no longer required by ADDM.

AWR snapshots can be created in CDB$ROOT.

ADDM can run in a nonroot container.

AWR reports can be generated while connected to any container.

All AWR data is stored in the CDB$ROOT SYSAUX tablespace.

AWR snapshots can be created in a PDB.

No AWR data is stored in the CDB$ROOT SYSAUX tablespace.

If a row lock is held by a nonexistent transaction, the block containing the row is media corrupt.

DB_BLOCK_CHECKING=TRUE causes a check sum to be added to each data block to help detect physical or media corruption.

A media corrupt block is one where the block is not formatted correctly.

The ANALYZE TABLE VALIDATE STRUCTURE CASCADE command verifies that each table row has an index entry pointing to it.

If a row lock is held by a nonexistent transaction, the block containing the row is logically corrupt.

DB_LOST_WRITE_PROTECT=TYPICAL causes extra logging overhead on the standby database.

CDB1_TAB, APP_ROOT_TAB, and APP_PDB1_TAB

CDB1_TAB and APP_PDB1_TAB

CDB1_TAB and APP_ROOT_TAB

CDB1_TAB only

none of the tables, because all three tables will be dropped

RESYNC CATALOG

CROSSCHECK BACKUP OF ARCHIVELOG ALL

LIST ARCHIVELOG ALL

LIST EXPIRED

LIST ARCHIVELOG

REPORT OBSOLETE

It can contain a single application

Two application containers can share an application seed PDB.

It must have an application root PDB.

An application PDB can belong to multiple application containers.

It must have an application seed PDB.

It can contain multiple applications.

With Automatic Shared Memory Management, the database instance can increase the Large Pool size by reducing the Shared Pool size.

With Automatic Memory Management, the database instance can increase the System Global Area size by reducing the Program Global Area size.

Automatically tuned and resized System Global Area components will always revert to their initial sizes after an instance restart.

Automatic Memory Management must be used together with locking the System Global Area into physical memory.

With Automatic Shared Memory Management, the database instance can increase the Program Global Area size by reducing the System Global Area size.

On Line Transaction Processing systems often use less Program Global Area than Decision Support Systems.

The ORCL database, the Oracle ASM instances, the +DATA and +FRA disk groups, and the LISTENER are started.

Only the ORCL database instance is started.

Only the ORCL database and the ASM instances are started.

Only the ORCL database instance, the Oracle ASM instance, and the +DATA and +FRA disk groups are started.

Only the ORCL database instance and the +DATA and +FRA disk groups are started.

CDB1, PDB$SEED, PDB1, and PDB2

PDB$SEED, PDB1, and PDB2 only

CDB1 and PDB$SEED only

CDB1, PDB1, and PDB2 only

CDB1, PDB$SEED, and PDB1 only

SAL will be added to APP_PDB1.EMP, with 0 in columns of existing rows.

SAL will be added to APP_PDB1.EMP, with NULLs in columns of existing rows.

It will return an error because the SYNC operation is not allowed when constraints are added to common objects.

It will return an error because EMP is not empty in APP_ROOT.

It will return an error because EMP.SAL is empty in APP_ROOT.

Increase the size of tape I/O buffers.

Disable FORCE LOGGING for the database.

Increase the size of the database buffer cache.

Enable asynchronous disk I/O.

Increase the level of RMAN multiplexing.

after losing all members of the CURRENT online redo log group

after losing all copies of the control file

after losing an UNDO tablespace that is in use

after losing all members of an INACTIVE online redo log group

after losing a SYSAUX tablespace data file

FLASHBACK DATABASE only uses FLASHBACK LOGS to get the database to the desired flashback time.

It requires that the target database be in ARCHIVELOG mode.

FLASHBACK LOGS are archived after a log switch.

A database can be flashed back using SQL*PLUS.

It always generates REDO and UNDO.

Queries and DML have the same FLASHBACK LOG overhead when flashback is enabled for a database.

1,2,4,5,7,8

1,2,4,6,7,8

1,2,3,4,5,7,8

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

2,4,5,6,7

Open the CDB instance in restricted mode. In CDB$ROOT, drop the UNDO tablespace. Execute ALTER DATABASE LOCAL UNDO ON in each PDB, and then restart the CDB instance.

Open the CDB instance in upgrade mode. In CDB$ROOT, execute ALTER DATABASE LOCAL UNDO ON, and then restart the CDB instance.

Open the CDB instance in upgrade mode. In each PDB, execute ALTER DATABASE LOCAL UNDO ON, create an UNDO tablespace, and then restart the CDB instance.

Open the CDB instance in restricted mode. In CDB$ROOT, execute ALTER DATABASE LOCAL UNDO ON. create an UNDO tablespace in each PDB, and then restart the CDB instance.

Open the CDB in read-only mode. In CDB$ROOT, execute ALTER DATABASE LOCAL UNDO ON, and then change the CDB to read/write mode.

the data dictionary in CDB$ROOT

the log writer process (LGWR)

SYSAUX tablespaces

temporary tablespaces

the Process Monitor Process (PMON)

undo tablespaces

They can view data from any data dictionary view or dynamic performance view.

They can drop any tablespace.

They can view data from any user-defined tables.

They can create any table.

They cannot create restore points.

They cannot drop tablespaces.

Tablespaces always remain in read/write mode during transportable tablespace operations.

Tablespaces never remain in read/write mode during transportable tablespace operations.

A transportable data pump import can leave a plugged-in tablespace in read-only mode.

Simultaneous data pump jobs can be limited at the pluggable database (PDB) level.

A transportable data pump import can leave a plugged-in tablespace in read/write mode.

An ordinary data pump export of a table with encrypted columns will always encrypt the same columns when imported.