Top Tips for Passing the Oracle 1z0-497 Exam on Your First Try

SQL> conn c##usr/pwd@pdb1

You are connected to PDB1 successfully.

SQL> conn c##usr/pwd@pdb2

You are connected to PDB2 successfully.

SQL> conn c##usr/pwd@pdb2

You are unable to create a connection. You first need to sync PDB2 by executing:

SQL> conn / as sysdba

SQL>exec DBMS_PDB.SYNC_PDB;

SQL> conn c##usr/pwd@pdb2

You are unable to create a connection. You need to create the common user c# #usr explicitly in PDB2 by executing:

SQL>conn system/pwd@pdb2

SQL> CREATE USER c##usrIDENTIFIED BYpwd CONTAINER=CURRENT;

Now you are able to connect as common user c##usr to PDB2.

Oracle Database alert.log file

object-level statistics

Automatic SGA Memory Management

Oracle Database Trace files

all server-generated alerts

They find a pattern of nine digits; break the digits into three groups that contain the first three, the next two and then the last four digits; and replace all digits with XXXXX concatenated with the last four digits.

They find a pattern of six digits; break the digits into two groups that contain the first five, and then the last digit; and replace all digits with XXXXX concatenated with the last digit.

They find a pattern of nine digits and display the digits as XXXXX XX XXXX.

They find a pattern of nine digits and display the first five digits as XXXXX and the last four digits as 3333.

Moving a data file online prevents DML operations on segments stored in the data file.

Flashing back a database to a point in time before a data file had been renamed online retains the new name.

Moving a data file online can be performed if the data file is in OFFLINE mode.

Moving a data file online cannot be performed if the data file is under BEGIN BACKUP.

A snapshot standby can be the target of a switchover or fast-start failover operation.

Neither a switchover nor a failover is possible to a far sync instance.

For fast-start failover, you must preselect the target standby database that will be used.

You can activate a standby database to test whether it is being updated correctly.

Oracle-supplied metadata resides only in the root container.

A seed PDB can sometimes be opened for particular operations.

Multiple PDBs with the same name can reside in the same CDB.

A CDB can have an infinite number of PDBs.

You can create common users in PDBs.

You can perform complete recovery by using the command:

RESTORE DATABASE

FROM TAG“consistent_whole_backup”;

RECOVER DATABASE;

You can perform incomplete recovery by using the command:

RESTORE DATABASE;

FROM TAG "consistent_whole_backup";

RECOVER DATABASE NOREDO;

Only consistent backups can be used for restoring a database in NOARCHIVELOG mode.

Media recovery is possible in most cases.

It is ignored by the query optimizer.

It is not used while the index is being rebuilt.

The index cannot be rebuilt, and has to be re-created.

The index is automatically rebuilt when used the next time.

A CHECK constraint is created on the OID column.

A NOT NULL constraint is created on the OID column.

The ORDERS table is the only object created in the USERS tablespace.

The ORDERS table and a unique index are created in the USERS tablespace.

The ORDERS table is created in the USERS tablespace and a unique index is created on the OID column in the SYSTEM tablespace.

when upgrading from Oracle Database 12c to the first patch set of Oracle Database 12c

when upgrading from Oracle Database 10g to Oracle Database 12c

when upgrading from Oracle Database 11g to Oracle Database 12c

when upgrading from any previous version of Oracle Database to Oracle Database 12c