When performing restore and recovery, RMAN can use backups from a previous incarnation in restore and recovery operations just as it would use backups from the current incarnation, as long as all archived logs are available. The Data Recovery Advisor can detect and repair a wide variety of physical problems that cause data loss and corruption. Displays backup sets, proxy copies, and image copies marked in the repository as EXPIRED, which means they were not found. Otherwise, the value ranges from 2 to 4.

To list preplugin backups, you must connect to the root as a common user with the SYSDBA or SYSBACKUP privilege. The time that the restore point was created.

30.LIST ARCHIVELOG; If you do not specify an object, then LIST defaults to OF DATABASE CONTROLFILE ARCHIVELOG ALL. The checkpoint of this control file when it was copied. The following example lists all data file, control file, and archived redo log copies known to RMAN: Example 2-111 Listing Database Incarnations. After connecting to the target database and recovery catalog (if you use one), execute LIST BACKUP, specifying the desired objects and options. Change), You are commenting using your Facebook account. All database changes before the time were written to the file; changes after the specified time were not written to the file. LIST BACKUP OF DATABASE BY BACKUP; LIST BACKUP OF ARCHIVELOG FROM SEQUENCE 1437; This command will list the controlfile copy Sample output follows: The preceding output indicates that a RESETLOGS was performed on database trgt at SCN 164378, resulting in a new incarnation. You can specify several different conditions to narrow your LIST output. Oracle Database Backup and Recovery User's Guide to learn how to make lists and reports, and REPORT.

All database changes prior to the time have been written to the file; changes after the specified time have not been written to the file. Displays information about the incarnations of a database.

It corresponds to BS_KEY in the RC_BACKUP_SET view. The backup level: F for nonincrementals, level 0 or 1 for incrementals.

RMAN REPORT COMMAND If the backup piece is on SBT, then the Media ID is displayed with the name. The number of the backup piece in the backup set. The only valid exception is LIST BACKUP OF ARCHIVELOG LIKE. The LIST FAILURE command displays failures against which you can run the ADVISE FAILURE and REPAIR FAILURE commands. The SCN of the proxy copy control file checkpoint. 7.LIST BACKUP SUMMARY; Examples of such failures include physical data block corruptions, nonfatal I/O errors, missing archived redo log files or backup files, and so on. Because the limit is inclusive, RMAN only lists files that are recoverable up to and including the SCN corresponding to the restore point. If RMAN is connected to a target database in NOCATALOG mode, then Key displays the RECID from V$BACKUP_SET. The comment provided when the script was created. REPORT NEED BACKUP RECOVERY WINDOW OF 7 DAYS; Lists only failures with HIGH priority and status OPEN. The time of the backup control file checkpoint. The backup piece status: AVAILABLE, UNAVAILABLE, or EXPIRED (refer to the CHANGE, CROSSCHECK, and DELETE commands for an explanation of each status). All database changes recorded in the redo records before the specified time are reflected in this control file. The file name or handle of the backup piece. Copy (if multiple pieces). 15LIST BACKUP OF ARCHIVELOG FROM SEQUENCE 2222; 35.LIST GLOBAL SCRIPT NAMES; 36.LIST FAILURE; 11g R1

If RMAN is connected in NOCATALOG mode, then Key displays the RECID from V$ARCHIVED_LOG. 1.LIST INCARNATION; If RMAN is connected in NOCATALOG mode, then PC Key displays the RECID from V$PROXY_DATAFILE. It corresponds to BP_KEY in the RC_BACKUP_PIECE view. If the piece is stored on SBT, then the Handle and media ID are displayed. If RMAN is connected to a recovery catalog, then BS Key is the primary key of the backup set in the catalog. This example lists all failures regardless of their priority. If the backup piece is stored on SBT, then the media ID is also displayed. *********************** 10.LIST BACKUP OF DATABASE BY BACKUP; 37.LIST FAILURE 420 DETAIL; 11g R1 If no options are specified on LIST FAILURE, then the command lists only the highest priority failures that have status OPEN. 12.LIST BACKUP OF DATAFILE 65; The priority of the failure: CRITICAL, HIGH, or LOW. For incremental backups, the incremental backup level (0 or 1). Typically, critical failures bring down the instance and are diagnosed during the subsequent startup. The status column of the archived log backup indicates that the backup set is unavailable. The database identification number, which the database generates automatically at database creation. Displays information about backup sets (including detail on backup pieces) and proxy copies. The repair status of the failure. 01 list incarnation===========================01.01 list incarnation;list incarnation of database;list incarnation of database 'ORA9I'; ===================================================02 list backup example===========================02.01list backup;02.02list backup of database;02.03list backup of tablespace 'SYSTEM','USERS';02.04list backup of datafile 1,3,7;list backup of datafile 'e:oracleoradataora9isystem01.dbf','e:oracleoradataora9iusers01.dbf';02.05list backup of controlfile;02.06list backup of spfile;02.07list backup of archivelog all;list backup of archivelog like '%.log';list backup of archivelog from time 'sysdate-14';list backup of archivelog until time 'sysdate-7';list backup of archivelog from time 'sysdate-14' until time 'sysdate-7';list backup of archivelog from scn 10000;list backup of archivelog until scn 11000;list backup of archivelog from scn 10000 until scn 11000;list backup of archivelog from logseq 135;list backup of archivelog until logseq 139;list backup of archivelog from logseq 135 until logseq 139;02.08list backup completed after 'sysdate -14';list backup completed before 'sysdate -7';list backup completed between 'sysdate -14' and 'sysdate-7';02.09list backup tag=WHOLE_COLDBACK;02.10list backup recoverable;02.11list backup device type disk;02.12list backup completed after 'sysdate-14'tag=WHOLE_COLDBACKdevice type diskrecoverable;===================================================03 list copy example===========================03.01list copy;03.02list copy of database;03.03list copy of tablespace 'SYSTEM','USERS';03.04list copy of datafile 1,3,7;list copy of datafile 'e:oracleoradataora9isystem01.dbf','e:oracleoradataora9iusers01.dbf';03.05list copy of controlfile;03.06list copy of spfile;03.07list copy of archivelog all;list copy of archivelog like '%.log';list copy of archivelog from time 'sysdate-14';list copy of archivelog from time "to_date('07-11-2004','mm-dd-yyyy')";list copy of archivelog until time 'sysdate-7';list copy of archivelog from time 'sysdate-14' until time 'sysdate-7';list copy of archivelog from scn 10000;list copy of archivelog until scn 11000;list copy of archivelog from scn 10000 until scn 11000;list copy of archivelog from logseq 135;list copy of archivelog until logseq 139;list copy of archivelog from logseq 135 until logseq 139;03.08list copy completed after 'sysdate -14';list copy completed before 'sysdate -7';list copy completed between 'sysdate -14' and 'sysdate-7';03.09list copy tag=WHOLE_COLDBACK;03.10list copy recoverable;03.11list copy device type disk;03.12list copy completed after 'sysdate-14'tag=WHOLE_COLDBACKdevice type diskrecoverable; ================================================04. If the object is on sbt, then the media ID is also displayed. Lists only failures whose priority cannot be determined until the database is mounted. After connecting to the target database and the recovery catalog if applicable, run LIST INCARNATION: If you are using a recovery catalog, and if you register multiple target databases in the same catalog, then you can distinguish them by using the OF DATABASE option: Refer to Oracle Database Backup and Recovery Reference for an explanation of the various column headings in the LIST output). The tag column of the data file backup indicates that one backup set contains backup pieces with different tags. Command list the data files copy Use this value in a CHANGE command to alter the status of the copy. RMAN must also be connected to a mounted or open target database.

32.LIST CONTROLFILECOPY /tmp/cntrlfile.copy; 33.LIST SCRIPT NAMES; The media manager's handle for the proxy copy. You must be connected to a target database and a recovery catalog to use this form of the command. For Data Recovery Advisor, a failure is a persistent data corruption that is mapped to a set of repair actions. Restricts the list to expired data file backups or copies whose status in the repository is AVAILABLE and which can be used for restore and recovery in the current incarnation of the target database. Lists failures with all priorities and status OPEN. This list includes all backups and copies except the incremental backups that have no valid parent to which the incremental can be applied. Specifies whether to summarize backups or list the backups for a particular data file. Specifies whether to list summary information about backups or detailed information. Table 2-10 List of Backup Pieces (for sets with only one piece). Lists only failures with LOW priority with status OPEN. It corresponds to BS_KEY in the RC_BACKUP_SET view. All database changes recorded in the redo records before the specified SCN are reflected in this control file. It corresponds to XDF_KEY in the RC_PROXY_DATAFILE view or XCF_KEY in the RC_PROXY_CONTROLFILE view. The number of backup pieces in the backup set. RMAN must also be connected to a mounted or open target database, or you must have run the SET DBID command. RMAN must be connected to a recovery catalog. YES if the backup set was compressed by RMAN; NO if not compressed by RMAN. It corresponds to BS_KEY in the RC_BACKUP_SET view. 11.LIST BACKUP OF TABLESPACE test SUMMARY; You can use the output of LIST to identify specific backups you wish to use with other RMAN commands. The number of copies made of each backup piece in the set. ICP16024965-8 11010802021510 niuxiaotong@pcpop.com 17352615567 , Script--How to record user login on oracle database.

Specifies an end time, SCN, or log sequence number. The low SCN of the next archived log sequence. 39.LIST RESTORE POINT ALL; *********************** RMAN lists only global scripts defined in the connected recovery catalog, along with any descriptive comments. Failures with HIGH priority make a database partially unavailable or unrecoverable, and usually have to be repaired in a reasonably short time. (LogOut/ If you do not specify the OF DATABASE option, then LIST displays all databases registered in the recovery catalog. The number is 1 if no duplexing was performed. You can also list backups in a summary mode if the verbose mode generates too much output. 26.LIST EXPIRED COPY; 27.LIST BACKUPSET SUMMARY; The checkpoint of the data file at the time it was backed up.

See Also: Table 2-16 for a description of LIST BACKUP SUMMARY output and Example 2-108 for sample output. Lists local and global scripts that can be executed on the current target database. The status of the copy: A (available), U (unavailable), or X (expired). If RMAN is connected in NOCATALOG mode, then Key displays the RECID from V$DATAFILE_COPY. 25.LIST COPY OF CONTROLFILE; This subclause specifies recoverable backups. Change), You are commenting using your Twitter account. The date and time that the backup set completed. This command list the backups of database A server parameter file is included in the backup. All database changes prior to the SCN have been written to the file; changes after the specified SCN have not been written to the file. The incarnation is distinguished by incarnation key (represented in the Inc Key column). If RMAN is not connected to a recovery catalog, and if you are not executing the LIST FAILURE command, then the target database must be mounted or open. By default, RMAN lists in verbose mode. See Also: Table 2-28 for a description of the output. 16LIST BACKUP OF ARCHIVELOG FROM TIME sysdate-1; Use this key to unregister a database from a recovery catalog, that is, delete all the rows associated with that database from the recovery catalog. Failures with CRITICAL priority require immediate attention because they make the whole database unavailable. The time specified in the CREATE RESTORE POINT statement; otherwise null. Note: The values for KEY in the recovery catalog and the control file are different. The SCN of the backup control file checkpoint. This example lists all backups. LIST BACKUP RECOVERABLE; Database incarnations and their effect upon database recovery with RMAN are explained in more detail in Oracle Database Backup and Recovery Advanced User's Guide. If RMAN is connected in NOCATALOG mode, then BP Key displays the RECID from V$BACKUP_PIECE. About RMAN Reports Generated by the LIST Command. The type of backup: backup set (B) or proxy copy (P). Specify the desired objects with the listObjectList or recordSpec clause. Displays all restore points known to the RMAN repository. Whenever you open a database with the RESETLOGS option, you create a new incarnation of the database. document.getElementById( "ak_js_1" ).setAttribute( "value", ( new Date() ).getTime() ); ARCHIVELOG BACKUP & BACKUPSET & IMAGECOPY, Configure the Gateway to Access Multiple SQL ServerDatabases, Configuring Oracle Gateway To Connect SQL SERVERDatabase-1, Different type of DB recoveryscenarios-1, Different type of DB recoveryscenarios-2, Different type of DB recoveryscenarios-3, Different type of DB recoveryscenarios-4, Different type of DB recoveryscenarios-5, Different type of DB recoveryscenarios-6, Different type of DB recoveryscenarios-7, Install Oracle 10g Release 2 on RHEL(Red Hat Enterprise Linux 5.1)5-1, Install Oracle 10g Release 2 on RHEL(Red Hat Enterprise Linux 5.1)5-2, Resolving Gaps in Data Guard Apply Using Incremental RMANBAckup-1, Resolving Gaps in Data Guard Apply Using Incremental RMANBAckup-2, rMAN $Views AND Deleting Backups and Copies & Catalogingcommands, RMAN All major Restoration and RecoveryScenarios-1, RMAN All major Restoration and RecoveryScenarios-2, RMAN All major Restoration and RecoveryScenarios-3, RMAN All major Restoration and RecoveryScenarios-4, RMAN DELETE-DROP-DUPLICATE-SWITCH-BLOCKRECOVER-ADVISE FAILURE-REPAIR FAILURE-VALIDATE COMMANDS, RMAN SHOW-SET-CHANGE-CROSSCHECK-CHANGE COMMANDS, RMAN-REPORT-UNREGISTER-REGISTER-GRANT-REVOKE-COMMAND, step by step oracle database 10g upgrade from 10.2.0.1 to10.2.0.4, uic_project_Configuring and Accessing Oracle Discoverer andMOD_PLSQL-1, uic_project_Configuring Oracle Database 11g withOID-1, uic_project_Creating DB Schema For GlobalAuthentication, uic_project_forms_menu_library files compilation, uic_project_Integrating Forms with OAM11g, uic_project_Integrating OID & Microsoft ActiveDirectory, Upgrade Oracle 10g from 10.2.0.1 to 10.2.0.4 (SingleInstance)-LINUX, PHYSICAL STANDBY DATABASE ISSUES AND SOLUTIONS-part11, PHYSICAL STANDBY DATABASE ISSUES AND SOLUTIONS-part10, PHYSICAL STANDBY DATABASE ISSUES ANDSOLUTIONS-part9, PHYSICAL STANDBY DATABASE ISSUES ANDSOLUTIONS-part8, PHYSICAL STANDBY DATABASE ISSUES ANDSOLUTIONS-part7, PHYSICAL STANDBY DATABASE ISSUES ANDSOLUTIONS-part6, PHYSICAL STANDBY DATABASE ISSUES ANDSOLUTIONS-part5, PHYSICAL STANDBY DATABASE ISSUES ANDSOLUTIONS-part4, PHYSICAL STANDBY DATABASE ISSUES ANDSOLUTIONS-part3, PHYSICAL STANDBY DATABASE ISSUES ANDSOLUTIONS-part2. Lists backups that are obsolete under the configured retention policy. 9LIST BACKUP OF DATABASE; Displays reduced output. The tag applied to the backup set. If you do not specify ALL, then LIST FAILURE output does not include failures with LOW priority. PRIMARY if the database is a primary database; STANDBY if it is a standby database. The tag applied to the backup set. For example, a block corruption is initially assigned a high priority, but if this block is not important for the database availability, you can use CHANGE FAILURE to change the priority to LOW. Refer to the CHANGE, CROSSCHECK, and DELETE commands for an explanation of each status. LIST BACKUP SUMMARY; The Data Recovery Advisor may not detect or handle some types of logical corruptions. All database changes before the SCN were written to the file; changes after the specified SCN were not written to the file. The unique identifier for the data file copy. Otherwise, the value ranges from 2 to 4. The date and time that the copy completed. Use optional REDUNDANCY and RECOVERY WINDOW parameters to specify different criteria. Sample output of LIST BACKUP follows: Specify the desired objects with the listObjList or recordSpec clause (refer to Oracle Database Backup and Recovery Reference). "RMAN Backups in a Data Guard Environment" explains how RMAN handles backups in a Data Guard environment. list backup summary===========================04.01list backup summary;04.02list backup of database summary;04.03list backup of tablespace users summary;04.04list backup of datafile 9 summary;04.05list backup of archivelog all summary;04.06list backup of controlfile summary;04.07list backup of spfile summary; =======================================================05. It corresponds to CDF_KEY in the RC_DATAFILE_COPY view. The unique identifier for the control file copy. Thus, repeatedly executing LIST FAILURE reveals new failures only if the database automatically diagnosed them in response to errors that occurred in between command executions. Whether the backup piece is compressed (YES or NO). 28.LIST BACKUPSET 109;

CURRENT for the current incarnation, PARENT for the parent incarnations of the current incarnation, and ORPHAN for orphaned incarnations. Lists the expired files in listObjectSpec or recordSpec that are exclusively associated with the specified DB_UNIQUE_NAME in a Data Guard environment. The value of this field is sensitive to the NLS_LANG and NLS_DATE_FORMAT environment variables. If you do not specify an object, then LIST BACKUP displays all backups. The level of the backup: NULL for nonincrementals, level 0 or 1 for incrementals. If it does not find them, then it updates their repository records to status EXPIRED. The file name of the archived redo log copy. See Also: Table 2-25 for a description of the output and Example 3-19 for an illustration. The unique identifier for this archived redo log copy. Displays information about a range of foreign archived redo log files. Note that the V$BACKUP_FILES also contains list information for backups. Each check can diagnose one or more failures, which are mapped to a set of repairs. The level of the backup: NULL for nonincrementals, level 0 or level 1 for incrementals.

(LogOut/ 20.LIST EXPIRED BACKUP OF ARCHIVELOG ALL SUMMARY; 21.LIST COPY; 4.LIST DB_UNIQUE_NAME ALL; 29.LIST BACKUPSET OF DATAFILE 1; The checkpoint of this data file when it was copied. The checkpoint of this data file when it was copied. The following command use to report the file need to be backup, This command report the files need backup for the given days, This command report the backup need files based on redundancy Oracle Database Backup and Recovery User's Guide, List of Control File Backups (LIST BACKUP BY FILE), Description of the illustration maintqualifier.eps, Description of the illustration listobjectspec.eps, Description of the illustration recoverableclause.eps, Description of the illustration listbackupoption.eps. If RMAN is connected to a recovery catalog, then the target database instance must be started. Specifies the expired object or objects that you are listing. The database is not available until all critical failures are fixed (see ADVISE FAILURE). For example, you can enter: Optionally, specify EXPIRED to identify backups not found during a crosscheck: Examine the output (refer to Oracle Database Backup and Recovery Reference for an explanation of the various column headings in the LIST output). Failures are sorted in reverse order of occurrence, with the most recent failure listed first.

Each time an OPEN RESETLOGS operation is performed on a database, this operation creates a new incarnation of the database. All database changes recorded in the redo records before the specified SCN are reflected in this control file. Displays restore points known to the RMAN repository. If RMAN is connected to a recovery catalog, then BP Key is the primary key of the backup piece in the catalog. Table 2-18 List of Datafile Backups (LIST BACKUP BY FILE). RMAN prints the LIST output to either standard output or the message log, but not to both at the same time. (LogOut/ When performing incremental backups, RMAN can use a backup from a previous incarnation or the current incarnation as a basis for subsequent incremental backups. See Also: Table 2-27 for an explanation of the column headings of the LIST FAILURE output table and Example 2-112 for an illustration. You can specify a database with db_unique_name or use ALL for all uniquely named databases recorded in the catalog for a particular DBID. The low time of the next archived log sequence. The tag applied to the proxy copy. This is the default mode of presentation.

This will list the backupset of datafile 1

The checkpoint of the data file at the time it was backed up. To list backups by file, connect the RMAN client to the target database and recovery catalog (if you use one), and then execute LIST with the BY FILE option, specifying the desired objects to list and options.For example, you can enter: For another example, you could specify the EXPIRED option to identify backups not found during a crosscheck: Examine the output (refer to Oracle Database Backup and Recovery Reference for an explanation of the various column headings in the LIST output).