![]() ![]() A database is uniquely identified in the recovery catalog by a DBID and the value of the DB_UNIQUE_NAME initialization parameter. 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. Lists the expired files in listObjectSpec or recordSpec that are exclusively associated with the specified DB_UNIQUE_NAME in a Data Guard environment. Specifies the expired object or objects that you are listing. Query the dba_pdb_history view to determine the GUID, of dropped PDBs. To display backups of PDBs that were dropped, use the GUID option with the LIST command and specify the GUID of the dropped PDB. Specifies the type of expired object or objects that you are listing. If it does not find them, then it updates their repository records to status EXPIRED. When you use a CROSSCHECK command, RMAN searches disk and tape for backups and copies recorded in the repository. To ensure that LIST EXPIRED shows up-to-date output, use a CROSSCHECK command periodically. See Table 2-9 for a description of the output. Lists the DB_UNIQUE_NAME of every database with the specified DB_NAME.ĭisplays backup sets, proxy copies, and image copies marked in the repository as EXPIRED, which means they were not found. Lists the DB_UNIQUE_NAME of every database registered in the RMAN repository. See Also: Table 2-28 for a description of the output The DBID for a primary database is identical to the DBID of its associated standby databases: they are distinguished by DB_UNIQUE_NAME. RMAN must also be connected to a mounted or open target database, or you must identify the target database with the SET DBID command. ![]() RMAN must be connected to a recovery catalog. Lists the DB_UNIQUE_NAME of one or more databases registered in the recovery catalog. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |