Explore topic-wise InterviewSolutions in .

issue command at RMAN prompt…..

RMAN> configure CONTROLFILE autobackup on;

also we can configure controlfile BACKUP FORMAT……

RMAN> configure controlfile autobackup format for device TYPE disk to ‘$HOME/BACKUP/RMAN/ F.bkp’; — $HOME/BACKUP/RMAN/ this can be any desired location.

issue command at rman prompt…..

RMAN> configure controlfile autobackup on;

also we can configure controlfile backup format……

RMAN> configure controlfile autobackup format for device type disk to ‘$HOME/BACKUP/RMAN/ F.bkp’; — $HOME/BACKUP/RMAN/ this can be any desired location.

DIFFERENTIAL BACKUP: This is the default type of INCREMENTAL backup which BACKS up all blocks changed after the most RECENT backup at level n or lower.

Cumulative backup: Backup all blocks changed after the most recent backup at level n-1 or lower.

Differential backup: This is the default type of incremental backup which backs up all blocks changed after the most recent backup at level n or lower.

Cumulative backup: Backup all blocks changed after the most recent backup at level n-1 or lower.

RMAN backup time CONSUMPTION is very less than COMPARED to regular online backup as RMAN COPIES only MODIFIED BLOCKS.

RMAN backup time consumption is very less than compared to regular online backup as RMAN copies only modified blocks.

Use this SQL to CHECK

SQL> SELECT sid totalwork sofar FROM V$session_longops WHERE sid 153;

Here give SID when back START it will show SID

Use this SQL to check

SQL> SELECT sid totalwork sofar FROM v$session_longops WHERE sid 153;

Here give SID when back start it will show SID

RMAN> LIST BACKUP;

RMAN> List Backup;

The DIFFERENCE is only who maintains the backup RECORDS like when is the last successful backup incremental differential etc.

• In CATALOG mode ANOTHER database (TARGET database) stores all the information.
• In NOCATALOG mode controlfile of Target database is responsible.

The difference is only who maintains the backup records like when is the last successful backup incremental differential etc.

RMAN KEEPS INFORMATION of backups in the CONTROL file.

RMAN keeps information of backups in the control file.

By using catalog COMMAND.You have to catalog that manual backup in RMAN’s repository by command 
RMAN> catalog datafilecopy ‘/DB01/BACKUP/users01.dbf’;
or
RMAN> CATALOG START WITH ‘/tmp/backup.ctl’;
Restrictions:
> ACCESSIBLE on DISK
> A COMPLETE image copy of a single file

By using catalog command.You have to catalog that manual backup in RMAN’s repository by command 
RMAN> catalog datafilecopy ‘/DB01/BACKUP/users01.dbf’;
or
RMAN> CATALOG START WITH ‘/tmp/backup.ctl’;
Restrictions:
> Accessible on disk
> A complete image copy of a single file

USING RMAN BLOCK RECOVER COMMAND

Using RMAN BLOCK RECOVER command

CROSSCHECK will be useful to check whether the catalog INFORMATION is INTACT with OS level information.

Crosscheck will be useful to check whether the catalog information is intact with OS level information.

The term obsolete does not MEAN the same as expired. In short obsolete MEANS “not needed ” whereas expired means “not found.”

A status of “expired” means that the backup piece or backup set is not found in the backup destination. A status of “obsolete” means the backup piece is still available, but it is no LONGER needed. The backup piece is no longer needed since RMAN has been configured to no longer need this piece after so many days have elapsed, or so many backups have been PERFORMED.

The term obsolete does not mean the same as expired. In short obsolete means “not needed ” whereas expired means “not found.”

A status of “expired” means that the backup piece or backup set is not found in the backup destination. A status of “obsolete” means the backup piece is still available, but it is no longer needed. The backup piece is no longer needed since RMAN has been configured to no longer need this piece after so many days have elapsed, or so many backups have been performed.

RC_DATABASE_INCARNATION, RC_BACKUP_COPY_DETAILS, RC_BACKUP_CORRUPTION, RC_BACKUP_DATAFILE_SUMMARY to NAME a few

RC_DATABASE_INCARNATION, RC_BACKUP_COPY_DETAILS, RC_BACKUP_CORRUPTION, RC_BACKUP_DATAFILE_SUMMARY to name a few

Steps to be followed:

• CREATE connection string at CATALOG database.
• At catalog database create one new user or USE existing user and GIVE that user a recovery_catalog_owner PRIVILEGE.
• Login into RMAN with connection string
• export ORACLE_SID
• rman target catalog @connection string
• rman&g ….

Steps to be followed:

1. SHUTDOWN Immediate
2. startup MOUNT 
3. Then, RUN the the DBNEWID UTILITY from command line.
4. nid target =/
5. SQL> alter DATABASE open resetlogs;

• We NEED to LIST the database incarnations by using list incarnation command.
• shutdown the database
• startup mount the database
• Issue reset database to incarnation to reset the incarnation.
• Restore the database using restore command (e.g restore until scn 23243)
• recover database
• Open the database using resetlogs command

RMAN> list incarnation of database;
RMAN>reset database to incarnation 5;
RUN
{
SET until scn 234345;
restore database;
rec ….

RMAN> list incarnation of database;
RMAN>reset database to incarnation 5;
run
{
set until scn 234345;
restore database;
rec ….

• STARTUP MOUNT;
• restore database UNTIL TIME “TO_DATE(’28/12/2012 18:00:00′, ‘DD/MM/YYYY HH24:MI:SS’)”;
• recover database UNTIL TIME “TO_DATE(’28/12/2012 18:00:00′, ‘DD/MM/YYYY HH24:MI:SS’)”;
• alter database OPEN resetlogs;

Obsolete BACKUPS:

• RMAN> report obsolete;

expired backup:

• RMAN> LIST expired backup;
• ACTIVE database: RMAN> list backup;

Obsolete backups:

expired backup:

RECOVERY catalog is a schema stored in a database that tracks BACKUPS and stores of target databases. So BETTER to TAKE a export backup.

Recovery catalog is a schema stored in a database that tracks backups and stores of target databases. So better to take a export backup.

Use below commands :

• rman> CATALOG datafilecopy ‘F:testsystem.dbf’;
• rman> backup validate CHECK logical datafile ‘f:testsystem.dbf’;
• SQL> SELECT * FROM v$database_block_corruption;

Use below commands :

• STARTUP mount;
• RESTORE DATABASE UNTIL SCN 233545;
• recover database UNTIL SCN 233545;
• alter database open resetlogs;

RMAN doesn’t SUPPORT cancel-based RECOVERY LIKE SQL*PLUS does.

RMAN doesn’t support cancel-based recovery like SQL*plus does.

No, table based RECOVERY not POSSIBLE in RMAN duplicate COMMAND.

No, table based recovery not possible in RMAN duplicate command.

An auxiliary channel is a link to auxiliary INSTANCE. If you do not have automatic channels configured, then before issuing the DUPLICATE command, manually allocate at least one auxiliary channel within the same RUN command. When a Duplicate Database CREATED or table space point in time RECOVERY is performed Auxiliary database is used. This database can either on the same host or a different host.

An auxiliary channel is a link to auxiliary instance. If you do not have automatic channels configured, then before issuing the DUPLICATE command, manually allocate at least one auxiliary channel within the same RUN command. When a Duplicate Database created or table space point in time recovery is performed Auxiliary database is used. This database can either on the same host or a different host.

Use the ALLOCATE CHANNEL command to manually allocate a channel, which is a connection between RMAN and a database instance. To enable the parallel backups, allocate multiple MANUAL channels in the RUN block or configure parallelism

CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO BACKUPSET;

Use the ALLOCATE CHANNEL command to manually allocate a channel, which is a connection between RMAN and a database instance. To enable the parallel backups, allocate multiple manual channels in the run block or configure parallelism

CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO BACKUPSET;

RMAN can store backup data in a logical STRUCTURE CALLED a backup set, which is the smallest unit of an RMAN backup. A backup set contains the data from one or more data files, archived redo logs, or control files or SERVER parameter FILE.

RMAN can store backup data in a logical structure called a backup set, which is the smallest unit of an RMAN backup. A backup set contains the data from one or more data files, archived redo logs, or control files or server parameter file.

Online redo logs should never, ever be included in a backup, regardless of whether that backup is performed hot or cold. The reasons for this are two-fold. First, you physically cannot backup a hot online redo LOG, and second there is PRECISELY zero need to do so in the first place because an archive redo log is, by DEFINITION, a backup copy of a formerly on-line log. There is, however, a more PRACTICAL reason: backing up the online logs yourself INCREASES the risk that you will lose.

Online redo logs should never, ever be included in a backup, regardless of whether that backup is performed hot or cold. The reasons for this are two-fold. First, you physically cannot backup a hot online redo log, and second there is precisely zero need to do so in the first place because an archive redo log is, by definition, a backup copy of a formerly on-line log. There is, however, a more practical reason: backing up the online logs yourself increases the risk that you will lose.

The restore/validate and validate backupset commands test whether you can restore backups or COPIES.

You should use:

• restore : validate when you want RMAN to choose which backups or copies should be tested.
• validate backupset when you want to SPECIFY which BACKUP sets should be tested.

The restore/validate and validate backupset commands test whether you can restore backups or copies.

You should use:

You can use the CONTROL_FILE_RECORD_KEEP_TIME PARAMETER to specify the minimum NUMBER of DAYS that Oracle keeps this information in the control FILE.

You can use the CONTROL_FILE_RECORD_KEEP_TIME parameter to specify the minimum number of days that Oracle keeps this information in the control file.

CONFIGURE channel as SBT_TAPE and use “ENV” parameter to SET the tape CONFIGURATIONS.

Configure channel as SBT_TAPE and use “ENV” parameter to set the tape configurations.

• A level 0 incremental backup, which is the BASE for subsequent incremental backups, copies all blocks containing data, backing the data file up into a backup set just as a FULL backup would. A level 1 incremental backup can be either of the following types:
• A differential backup, which backs up all blocks CHANGED after the most recent incremental backup at level 1 or 0
• A cumulative backup, which backs up all blocks changed after the most recent incremental backup at level 0