Tag: databases

NOT NULL

PRIMARY KEY

FOREIGN KEY

CHECK

UNIQUE

8

2

3

4

5

There is no such criteria

TRUNCATE * from TABLE Sales

TRUNCATE TABLE Sales

TRUNCATE Sales TABLE

TRUNCATE * FROM Sales

Once created a sequence belongs to a specific schema.

Once created, a sequence is linked to a specified table.

Once created a sequence is automatically available to all users.

Only the DBA can control which sequence is used by a certain table.

Once created a sequence is automatically used in all INSERT and UPDATE statements.

If the datafile resides on only one disk, there is no advantage of using parallel backups

The size of all the sections of a datafile involved in “Parallel backup” are always same

The size of all the sections of a datafile involved in “Parallel backup” are always same except the size of the last section

All the sections of one datafile are backed up by the same channel

All the sections of one datafile are backed up by different channels

COMMITTED UNDO data is NEVER backed up

COMMITTED UNDO data is backed up depending on the status of the transaction

COMMITTED UNDO data is backed up always

UNCOMMITTED UNDO data is never backed up

UNCOMMITTED UNDO data is backed up depending on the status of the transaction

UNCOMMITTED UNDO data is backed up always

Create one catalog database per Database Administrator to share the maintenance workload

Restrict SYSDBA and SYSOPER access from Database Administrators and yet allow them to perform database backup and recovery related tasks i.e. Virtualization of the SYSDBA and SYSOPER access

Maintain only one database for the RMAN repository catalog yet establish secure boundaries for individual database owners to manage their own virtual repositories

Make Oracle 11g database compliant with global Backup and Recovery standards

It is used to consolidate multiple catalog database repositories into a single catalog database

Once the import is successful, it unregisters the database from the destination catalog database i.e. the database where the metadata is imported

Once the import is successful, it unregisters the database from the source catalog database i.e. the database which holds the original metadata

If NO UNREGISTER clause is used, it will not unregister the database from the destination catalog database i.e. the database where the metadata is imported

If NO UNREGISTER clause is used, it will not unregister the database from the source catalog database i.e. the database which holds the original metadata

Duplicating the database from its backup has been available since Oracle8i Database

Duplicating the database from its backup has been available since Oracle9i Database

Duplicating the database from its backup has been available since Oracle10g Database

Duplicating the database from its backup has been available since Oracle11g Database

from target database

from live database

from source database

from active database