Tag: databases

It performs a merge join of the row from T2 only if it does'nt exist in the T1 table.

It creates a natural join of table T1 and T2 for all columns that have the same name.

It creates a Cartesian prodcut of table T1 and table T2 for all columns that have the same name.

For each row from T2, it updates the row if it exists witin table T1, otherwise it inserts the row into T1.

The contents and data files belonging to the IND2 tablespace are dropped.

The statement will only succeed if the IND2 tablespace was built using Oracle-Managed Files (OMF) data files.

The statement will only succeed if the data files belonging to the IND2 tablespace are Oracle Managed Files (OMF) or of the database was created using OMF.

The contents of the tablespace are dropped along with all its data files except those identical with Oracle-Managed Files (OMF) naming convention.

Do nothing, the PMON process handles everything.

Shut down the database and restore all the tables the user was updating.

Log in as DBA, clean up the partial updates in those tables, and do another manual backup.

Use LogMiner to find out which records are changed based on the user’s ID, then roll back all those changes.

The data file needs to be restored by using operating system commands, because a data file movement must take place, and then the database can be recovered from RMAN.

The data file needs to be restored by using operating system commands, since a data file movement must take place, and then the database must be recovered manually.

From RMAN you can issue the commands RESTORE and RECOVER. RMAN automatically restores the data file on DISK 3 to another disk, based upon utilization statistics.

From RMAN you can issue a SET NEWNAME command to update the data file location information in the control file, and then issue the RESTORE and RECOVER commands to recover the database.

All of the data files must be from a backup taken prior to the point in time to which you want to recover.

Only the data files belonging from the SYSTEM tablespace must be from a backup taken prior to the point in time to which you want to recover.

Only the data files that need recovery must be from a backup taken prior to the point in time which you want to recover.

Only the data files belonging to the SYSTEM tablespace and the data files that need recovery must be from a backup taken prior to the point in time to which you want to recover.

Set the LOG_ARCHIVE_START parameter to TRUE in the initialization parameter file.

Automatic archive is the default when ARCHIVELOG mode is set. No further actions are required.

Set the LOG_ARCHIVE_MAX_PROCESSES parameter to n (where n is the number of Archiver process) in the initialization parameter file.

Immediately after setting the database in ARCHIVELOG mode, in SQL*Plus select automatic archiving using the syntax : ALTER DATABASE SET LOG_ARCHIVE_START=TRUE

A text copy of the control file.

A binary copy of the control file.

A file containing a SQL statement which will re-create the database.

A file containing a SQL statement which will re-create the control file.

Each target database requires its own recover catalog.

RMAN scripts can be stored in the recovery catalog or the targer control file.

A channel is a stream of data to a device type and corresponds to one server session.

The RMAN executable interprets server session commands and establishes connections to the target database.

Only when the new master site already has existing replication groups.

By issuing a single command to create , populate, and activate the new master.

When the master definition site is not the same for all of the master grouups.

Without impacting end users who are executing data manipulation language (DML) commands on the replicated tables.

Data encryption

User authentication

Transparent data conversion

Configuration and administration mechanisms

Support for multiple network transport protocols