Practice Free 1z0-497 Oracle Database 12c Essentials Exam Questions Answers With Explanation

The average active sessions were more than three times the number of CPU cores.

Active sessions were more than 10% of total load and CPU utilization was more than 50%.

Memory allocations were more than 95% of physical memory.

Hung sessions were more than 10% of total sessions.

A deadlock was detected.

The session limit was close to 100%.

Multiple PDBs on a single server need multiple database instances and multiple sets of database files.

Although consolidated into a single physical database, PDBs mimic the behavior of non-CDBs.

A PDB administrator can use Oracle Flashback or point-in-time recovery to retrieve lost data from a PDB, only by shutting down all the PDBs from the CDB.

It is easier to collect performance metrics for many databases in a CDB than individual non-CDB databases.

It takes more time to apply a patch to one CDB that holds hundreds of PDBs than to hundreds of non-CDB databases.

Oracle Enterprise Manager Cloud Control

Oracle Data Guard monitor

Oracle Data Guard command-line interface (DGMGRL)

Oracle Data Guard Broker Manager

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.

Process Monitor process (PMON)

Listener Registration process (LREG)

System Monitor process (SMON)

Database Writer process (DBW)

Log Writer process (LGWR)

Checkpoint process (CKPT)

when multiple databases are to be registered with the listener

when DBAs need to connect remotely to start up the database instance

when users need to connect the database instance by using the host naming method

when the database instance to be registered with the listener is configured in shared server mode

The DML operations re-create the bitmap index blocks.

The bitmap index is rebuilt automatically after a DML operation.

The smallest amount of a bitmap that can be locked is a bitmap segment.

Additional time is taken to remove NULL values from the bitmap index alter a DML operation.

serializable

read-only

read committed

read uncommitted

durability

consistency

concurrency

isolation

scalability

manageability

Multiple transactions can use the same undo segment.

A transaction is assigned an undo segment when it is started.

Multiple transactions cannot share the same extent in an undo tablespace.

If all the segments in an undo tablespace are used, transactions use system undo segments to store undo data.

multitenant< schema consolidation< dedicated database< VMs

schema consolidation< VMs< dedicated databases< multitenant

dedicated databases< VMs< schema consolidation< multitenant

VMs< dedicated databases< schema consolidation< multitenant

A common user is created in the root container.

A local user is created in the root container.

A local user is created in all the PDBs.

The second SQL statement fails because a local user cannot be created in the root container.

The Oracle Streams information flow consists of three components: capture, redo transfer, arid consumption.

Oracle Streams is deprecated in Oracle Database 12c Release 1.

Oracle Database Advanced Replication is deprecated in Oracle Database 12c Release 1, including multimaster replication, updatable materialized views, multitier materialized views, and deployment templates.

Oracle Database Advanced Queuing is independent of Oracle Streams.

The Oracle GoldenGate software architecture is composed of three primary components: capture, propagate, and trail files.

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE statement with the FINISH keyword

ALTER DATABASE PREPARE TO SWITCHOVER and ALTER DATABASE COMMIT TO SWITCHOVER statements

ALTER DATABASE RECOVER TO STANDBY DATABASE statement with the FINISH keyword

D) ALTER DATABASE PREPARE SWITCHOVER and ALTER DATABASE COMMIT TO SWITCHOVER Statements

addition or removal of nodes, memory, or disks

changing configuration parameters, upgrading, or patching Oracle software

file deletion

migrating to cluster architecture

dropped database object

table definition changes

runaway processes that consume system resources

SYSBKP

SYSBKPRMAN

SYSRMAN

SYSBACKUP

You should check the patch conflict with installed patches before applying the patch.

You should make sure that you have a good backup of the software, database, and configuration files.

You should install the latest O patch before applying the patch.

You should check the fifth digit of the release information to confirm that the Patch Set Update (PSU) is applied successfully.

You should stop all applications running from the software directory that is being patched.

Process Monitor Process (PMON)

Flashback Data Archive process (FBDA)

Space Management Coordinator process (SMCO)

Recoverer process (RECO)

Listener Registration process (LREG)

Checkpoint Process

You can unplug a PDB from a development CDB and plug it into a production CDB, which allows for easier and more rapid movement of data and code.

You can consolidate shared database memory by combining multiple PDBs in a single CDB.

Patching individual PDBs requires the same amount of time as patching individual databases.

Consolidating separate databases into a single CDB requires the same amount of storage allocation.

In multitenant architecture, a PDB behaves the same as a non-CDB as seen from a client connecting with Oracle Net. No client modification is required.

Oracle GoldenGate

Oracle Advanced Replication

Oracle Active Data Guard

Oracle Streams

renaming the control files

re-creating the control files

dropping a user in your database

dropping a tablespace in your database

configuring the database instance to operate in ARCHIVELOG or NOARCHIVELOG mode

RMAN> VALIDATE CHECK LOGICAL

RMAN> VALIDATE BACKUP

RMAN> VALIDATE CORRUPT BLOCKS

RMAN> VALIDATE DATABASE

Extend the logical volume by 10 MB where the data files are stored;

# lvextend -L+10M /diskl

Add a data file:

SQL>ALTER TABLESPACE MYTBS ADD DATAFILE ' /disk1/mytbs_2 .dbf SIZE 10M;

Move a partition to another tablespace:

SQL> CREATE TABLESPACE ADDITIONAL_TBS DATAFILE '/disk1/additional_tbs_1 .dbf' SIZE 10M;

SQL> ALTER TABLE MYTAB MOVE PARTITION P2 TABLESPACE ADDlTIONAL_TBS;

Resize the existing data file:

SQL> ALTER DATABASE DATAFILE '/diskl/mytbs_l .dbf' RESIZE 20M;

E) Remove a data file:

SQL> ALTER TABLESPACE MYTBS DROP DATAFILE '/diskl/mytbs_l - dbf';

615 MB

2.5 GB

4 GB

12 GB

22 GB

It has commands for performing database administration operations.

It can be used in interactive but not batch mode for SQL commands.

It has to be installed separately after the Oracle Database 12c installation.

Operating system commands can be executed from the SQL*Plus command prompt.

It is used to retrieve installed patch information from a SQL prompt.

It uses the PREPROCESSOR feature, which allows users to preprocess input data before it is sent to the access drivers.

DBMS_QOPATCH provides a PL/SQL or SQL interface to view the database patches installed.

It works in an Oracle database instance that is mounted. Therefore, it works in ASM instances and DG instances.

The GDS catalog database of its listener may be down. Verify that the GDS catalog database and its local listener are running.

The GDS pool database may be down. Make sure that the GDS pool databases are up and the service is enabled and started.

The GDS pool database's local listener may be down. Make sure that it is running.

The global service may be down. Verify that the pool databases are up and the service is started.

The global service may be disabled. Make sure that the pool databases are up and the service is enabled and started.

select patch from vSoption where opatch_data=' 333333' ;

select xmltransform(dbms_qopatch.get_opatch_data(3333333), dbms_qopatch.GET_OPATCH_XSLT()) from dual

select opatch from vSpatchsets where opatch_number = '333333';

opatchlsinventory -xml

It enables you to use third-party technologies to take a storage snapshot of your database without putting the database in BACKUP mode. You can then use the snapshot to recover all or part of the database.

It enables you to use RMAN to take a storage snapshot of your database. The database must be in BACKUP mode. You can then use the snapshot to recover all or part of the database.

It enables you to use RMAN to take a storage snapshot of your database. The database doesn't have to be in BACKUP mode. You can then use the snapshot to recover all or part of the database.

It enables you to use third-party technologies to take a storage snapshot of your database. The database must be in BACKUP mode. You can then use the snapshot to recover all or part of the database.

The database stops (shutdown abort).

B) The database Stops (shutdown immediate).

You activate Automatic Shared Memory Management.

You get an error message.

The analyzed result is lost when the database instance is restarted.

It runs every 1 hour automatically.

It is shipped only with Oracle Enterprise Manager 12c.

It analyzes high CPU trend and identifies problems before they can threaten application performance.

It is created for the SALES database in the network domain ACME on the SALESDATA server.

It is created for the SALESDATA database on the SALES server in the network domain called ACME.

It generates an error because the connect identifier name cannot be a part of SERVICE_NAME.

It generates an error because the server configuration mode (dedicated or shared) is not specified.

when a transaction ID is allocated for it.

when a user explicitly issues a "begin" statement

when a transaction is assigned to an available undo data segment to record undo entries for the new transaction

when the first executable SQL statement is encountered

database files and parameter file (initialization parameter file or server parameter file)

System Global Area (SGA) and background processes

a listener process, server processes, and background processes

System Global Area (SGA), server processes, and background processes

database files, System Global Area (SGA), and background processes

The online redo log files and archived redo log files are required to accomplish a recovery.

The uncommitted transaction is committed at the next startup of the database instance.

The uncommitted transaction is rolled back automatically at the next opening of the database.

The DBA has to perform a recovery on the database to recover the uncommitted transaction.

The database is open and registered with a global service manager.

The service has been disabled on that database.

The database role is different from the role attribute of the service.

The replication lag on the database does not exceed the maximum value specified for the service.

The service has reached its cardinality defined by the number of preferred databases.

No other database in the pool is a better candidate for starting the service.

You can drop the PDB only if it is closed.

You can drop the seed PDB, but you cannot create any other PDB within the CDB.

You can drop the PDB and keep the data files to be reused by another PDB.

When you drop the PDB, the data files and redo log files are automatically removed from the storage file system.

It replaces the first four digits of the value from the SALARY column with the number 9.

It replaces the first digit of the value from the SALARY column with the number 4.

It replaces the first digit of the value from the COMMISSION_PCTcolumn with 9.

It replaces the first nine digits of the value from the COMMISSION_PCTcolumn with 1.

It uses the full data redaction method.

It uses the random redaction method.

You copy all the PDBSSEEDdata files from the production CDB into the development CDB and execute this on the development CDB;

SQL> CREATE PLUGGABLE DATABASE salesdev ADMIN USER salesdm IDENTIFIED by password;

You alter the salesprd source database to open in read-only mode, and start cloning the source database:

SQL> ALTER PLUGGABLE DATABASE salesprd OPEN READ ONLY;

SQL> CREATE PLUGGABLE DATABASE salesdev FROM salesprd;

You alter the salesprd source database to open in read-only mode:

SQL> ALTER PLUGGABLE DATABASE salesprd OPEN READ ONLY;

In the development CDB, you create a databaselink "PRD" that connects to the root of the source CDB, and start cloning the source PDB:

SQL> CREATE PLUGGABLE DATABASE salesdevFROM salesprd@prd;

Connected as the salesprd local DBA, you create an XML using:

SQL> ALTER PLUGGABLE DATABASE salespdb UNPLUG INTO ' /tmp/salesprd-xml' ;

Copy the XML file and all salesprd-related files to the target CDB and start plugging the copy into the development CDB using:

SQL> CREATE PLUGGABLE DATABASE salesdev USING' /tmp/salesprd.xml';

Index

Partitioning

Triggers

Row-level security

Database vault