See Also: Table 2-25 for a description of the output and Example 3-19 for an illustration. The log sequence number of the archived log. Sample output of LIST BACKUP follows: Specify the desired objects with the listObjList or recordSpec clause (refer to Oracle Database Backup and Recovery Reference).
The media manager's handle for the proxy copy. 28.LIST BACKUPSET 109; REPORT NEED BACKUP REDUNDANCY=3; Contact Us, . Lists the expired files in listObjectSpec or recordSpec that are exclusively associated with the specified DB_UNIQUE_NAME in a Data Guard environment.
If RMAN is connected to a recovery catalog, then BP Key is the primary key of the backup piece in the catalog. Therefore, CRITICAL and HIGH failures are always listed in the command output if they exist.
RMAN--List command.
Lists only critical failures with status OPEN. Specifies the type of expired object or objects that you are listing. Lists the DB_UNIQUE_NAME of every database registered in the RMAN repository. Refer to the CHANGE, CROSSCHECK, and DELETE commands for an explanation of each status. Lists backups of each data file, archived redo log file, control file, and server parameter file. Specifies an end time, SCN, or log sequence number. Specifies datafile backups or copies that are available and that can be restored and recovered in the current database incarnation. The checkpoint of this data file when it was copied. 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. 25.LIST COPY OF CONTROLFILE; Specify the desired objects with the listObjList clause. 30.LIST ARCHIVELOG; Excludes the specified failures from the list. The DBID of the database. Because the limit is inclusive, RMAN only lists files that are recoverable up to and including the SCN corresponding to the restore point. GUARANTEED if a guaranteed restore point; null if a normal restore point. (listObjectSpec::=, recordSpec::=, maintQualifier::=, forDbUniqueNameOption::=, untilClause::=), (completedTimeSpec::=, deviceSpecifier::=), (listObjList::=, listBackupOption::=, archivelogRecordSpecifier::=, foreignlogRecordSpecifier::=). In a Data Guard environment, LIST displays those files that are accessible to the connected target database.
7.LIST BACKUP SUMMARY; See Also: "Oracle RAC and Data Recovery Advisor". Otherwise, the value ranges from 2 to 4.
4.LIST DB_UNIQUE_NAME ALL; LIST BACKUP SUMMARY;
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 checkpoint of this control file when it was copied. 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. 23.LIST COPY OF TABLESPACE appl_idx; If RMAN is connected to a recovery catalog, then Key is the primary key of the backup set in the catalog.
Each time an OPEN RESETLOGS operation is performed on a database, this operation creates a new incarnation of the database. The file number of the data file from which this copy was made. The LIST output includes the primary keys of all database incarnation records for the specified database name (in the column Inc Key, which contains the incarnation key). Failures with LOW priority are listed only if no CRITICAL or HIGH priority failures exist. An asterisk (*) indicates that backup pieces have different tags within the same backup set, which occurs when a user changes the tag when using CATALOG or BACKUP BACKUPSET. See Also: Table 2-21 and Table 2-23 for an explanation of the column headings of the LIST COPY output tables. Examples of such failures include physical data block corruptions, nonfatal I/O errors, missing archived redo log files or backup files, and so on. Table 2-24 List of Database Incarnations. This subclause specifies the type of object or objects that you are listing. 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). Oracle Database Backup and Recovery User's Guide to learn how to make lists and reports, and REPORT.
If no options are specified on LIST FAILURE, then the command lists only the highest priority failures that have status OPEN. Scripting on this page enhances content navigation, but does not change the content in any way.
The low SCN of the next archived log sequence. Displays restore points known to the RMAN repository. For example, enter any of the following commands: You can also restrict the search by specifying the maintQualifier or RECOVERABLE clause. Failures are sorted in reverse order of occurrence, with the most recent failure listed first. The backup level: F for nonincrementals, level 0 or 1 for incrementals.
If RMAN is connected to a recovery catalog, then Key is the primary key of the data file copy in the catalog. The type of backup: Full or Incr (incremental). The following example lists all data file, control file, and archived redo log copies known to RMAN: Example 2-111 Listing Database Incarnations. The time at which the incarnation was created. 
Sample output follows: The preceding output indicates that a RESETLOGS was performed on database trgt at SCN 164378, resulting in a new incarnation. When combined with the Inc Key, the unique key by which RMAN identifies the database incarnation in the recovery catalog. ICP16024965-8 11010802021510 niuxiaotong@pcpop.com 17352615567 , Script--How to record user login on oracle database. 
This will list the backupset of datafile 1
Table 2-10 List of Backup Pieces (for sets with only one piece). For example, if multiple block corruptions existed in a file, then specifying the DETAIL option would list each of the block corruptions. If you do not specify an object, then LIST defaults to OF DATABASE CONTROLFILE ARCHIVELOG ALL. Fill in your details below or click an icon to log in: You are commenting using your WordPress.com account. Table 2-17 List of Backup Pieces (LIST BACKUPPIECE ). RMAN must also be connected to a mounted or open target database, or you must have run the SET DBID command. Physical corruptions are typically caused by faulty I/O subsystems or human error. 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. Lists only failures with LOW priority with status OPEN. 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. 34.LIST ALL SCRIPT NAMES; Table 2-18 List of Datafile Backups (LIST BACKUP BY FILE). The checkpoint of the data file at the time it was backed up. The DB_NAME of the database. 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). RMAN prints the LIST output to either standard output or the message log, but not to both at the same time. The file name of the archived redo log copy.
The checkpoint of the data file at the time it was backed up. If the piece is stored on SBT, then the Handle and media ID are displayed. LIST BACKUPSET OF DATAFILE 1; The status of a failure is OPEN (not repaired) until the appropriate repair action is invoked. This command report the backup need based on given retention policy The LIST FAILURE command does not initiate checks to diagnose new failures; rather, it lists the results of previously executed assessments. The number is 1 if no duplexing was performed. 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. See Also: Table 2-18, Table 2-19, and Table 2-20 for a description of LIST BACKUP BY FILE output. Restricts the list to 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. The status of the copy: A (available), U (unavailable), or X (expired). When you use a CROSSCHECK command, RMAN searches disk and tape for backups and copies recorded in the repository.
If the backup piece is on SBT, then the Media ID is displayed with the name.
Lists backups that are obsolete under the configured retention policy. The output also shows one SBT backup containing archived redo log files.
For example: You can also specify the EXPIRED keyword to identify those backups that were not found during a crosscheck: Refer to Oracle Database Backup and Recovery Reference for an explanation of the various column headings in the LIST output. Each check can diagnose one or more failures, which are mapped to a set of repairs. LIST BACKUP BY FILE; Displays information about backup sets (including detail on backup pieces) and proxy copies. LIST BACKUP OF DATABASE BY BACKUP; You can also list backups by file. YES if the backup was compressed by RMAN; NO if not compressed by RMAN. If RMAN is connected in NOCATALOG mode, then BP Key displays the RECID from V$BACKUP_PIECE. You can specify several different conditions to narrow your LIST output. If you do not specify an object, then RMAN displays copies of all database files and archived logs. The checkpoint of this data file when it was copied.
See Also: Table 2-28 for a description of the output. The typical use case is to run LIST FAILURE to list any failures, then use ADVISE FAILURE to display repair options, and REPAIR FAILURE to fix the failures. You can use the output of LIST to identify specific backups you wish to use with other RMAN commands. This example groups all backups by file. This list includes all backups and copies except the incremental backups that have no valid parent to which the incremental can be applied. Specifies the name of the database. It corresponds to BS_KEY in the RC_BACKUP_SET view. RMAN must be connected to a recovery catalog. The backup piece status: AVAILABLE, UNAVAILABLE, or EXPIRED (refer to the CHANGE, CROSSCHECK, and DELETE commands for an explanation of each status). If RMAN is connected to a recovery catalog, then the target database instance must be started. Typically, critical failures bring down the instance and are diagnosed during the subsequent startup. All database changes prior to this time have been written to this data file.
Note: The LIST BACKUP LIKE command is not valid. RMAN REPORT COMMAND Oracle Database Backup and Recovery Reference, Oracle Database Backup and Recovery Advanced User's Guide. The SCN of the backup control file checkpoint.
To ensure that LIST EXPIRED shows up-to-date output, use a CROSSCHECK command periodically. Use optional REDUNDANCY and RECOVERY WINDOW parameters to specify criteria.
YES if the backup set was compressed by RMAN; NO if not compressed by RMAN. 16LIST BACKUP OF ARCHIVELOG FROM TIME sysdate-1; It corresponds to BP_KEY in the RC_BACKUP_PIECE view. It corresponds to AL_KEY in the RC_ARCHIVED_LOG view. CURRENT for the current incarnation, PARENT for the parent incarnations of the current incarnation, and ORPHAN for orphaned incarnations. 20.LIST EXPIRED BACKUP OF ARCHIVELOG ALL SUMMARY; 21.LIST COPY; 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. The location where this file would be restored now if it were restored from this backup set and no SET NEWNAME command was entered. Change), You are commenting using your Facebook account.
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. The database identification number, which the database generates automatically at database creation. Failures with CRITICAL priority require immediate attention because they make the whole database unavailable. Primary and standby databases share the same DBID. 13.LIST BACKUP OF DATAFILE 11 SUMMARY; Either of the following conditions must be met: RMAN must be connected to a target database. Displays information about the incarnations of a database.
Both usable and unusable image copies are included in the output, even those that cannot be restored or are expired or unavailable. The file name or handle of the backup piece. ******************** LIST COPY OF DATAFILE 1, 2, 3; FAQ 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). PRIMARY if the database is a primary database; STANDBY if it is a standby database. When performing incremental backups, RMAN can use a backup from a previous incarnation or the current incarnation as a basis for subsequent incremental backups. Whenever you open a database with the RESETLOGS option, you create a new incarnation of the database. Specifies a restore point, with the SCN at which the restore point was created as the upper, inclusive limit. The output shows two backup sets on disk: one containing data files and the other containing autobackups. For example, you can list: Backups and proxy copies of a database, tablespace, datafile, archived redo log, or control file, Backups restricted by time, path name, device type, tag, or recoverability. If RMAN is connected in the default NOCATALOG mode, then BS Key displays the RECID from V$BACKUP_SET. Use the LIST INCARNATION command to see the incarnations of your database.
The REPORT command performs more complex analysis than LIST All database changes prior to this SCN have been written to this data file. Failures with LOW priority can be ignored until more important failures are fixed.
This example lists all database incarnations recorded in the recovery catalog. After connecting to the target database and recovery catalog (if you use one), execute LIST BACKUP, specifying the desired objects and options. All database changes before the time were written to the file; changes after the specified time were not written to the file.
The unique identifier for the control file copy. See Table 2-9 for a description of the output. This will report which files needs incremental level 1 backup, This will report which files needs backup as per given time. Tag names are not case sensitive and appear in all uppercase. The tag applied to the data file copy. > If RMAN is connected to a catalog, then BP Key is the primary key of the backup piece in the catalog. 10.LIST BACKUP OF DATABASE BY BACKUP; A control file is included in the backup. RMAN must be connected to a recovery catalog and SET DBID must have been run. 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 SCN at which the incarnation was created. LIST CONTROLFILECOPY /tmp/cf.cpy; 26.LIST EXPIRED COPY; 27.LIST BACKUPSET SUMMARY;
The comment provided when the script was created. Table 2-28 List of Databases (LIST DB_UNIQUE_NAME). Displays only information about data file copies, archived redo log files, and image copies of archived redo log files. RMAN LIST COMMANDS The status of the backup: A (available), U (unavailable), or X (all backup pieces in set expired). See Also: Table 2-16 for a description of LIST BACKUP SUMMARY output and Example 2-108 for sample output. The value of this field is sensitive to the NLS_LANG and NLS_DATE_FORMAT environment variables. A database is uniquely identified in the recovery catalog by a DBID and the value of the DB_UNIQUE_NAME initialization parameter. 18.LIST BACKUP RECOVERABLE; If RMAN is connected to a recovery catalog, then Key is the primary key of the control file copy in the catalog. This subclause specifies recoverable backups. Lists failures recorded by the Data Recovery Advisor. You can control how the output is displayed by using the BY BACKUP and BY FILE options of the LIST command and choosing between the SUMMARY and VERBOSE options.
Lists local and global scripts that can be executed on the current target database. Specify the desired objects with the listObjectList or recordSpec clause. By default, RMAN lists backups by backup, which means that it serially lists each backup or proxy copy and then identifies the files included in the backup.
Copy (if multiple pieces). LIST BACKUP OF ARCHIVELOG FROM SEQUENCE 1437; Restricts the list of objects operated on to the object type specified in the listObjList clause. Organizes the output by backup set. It corresponds to CCF_KEY in the RC_CONTROLFILE_COPY view.
RMAN must also be connected to a mounted or open target database. If RMAN is connected to a recovery catalog, then BS Key is the primary key of the backup set in the catalog. The absolute data file number of the file that was copied. Linux > It corresponds to BS_KEY in the RC_BACKUP_SET view. 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. The only valid exception is LIST BACKUP OF ARCHIVELOG LIKE. If you do not specify the OF DATABASE option, then LIST displays all databases registered in the recovery catalog. Use the key in a RESET DATABASE command to change the incarnation that RMAN considers to be current to a previous incarnation. 8LIST BACKUP BY FILE; 3.LIST INCARNATION OF DATABASE vis;
Data failures are detected by checks, which are diagnostic procedures that assess the health of the database or its components. 