[ Pobierz całość w formacie PDF ]
.validate command.This command validates that the specifiedbackup pieces, file copies and archived logs which should be available on disk,are physically there; if a file is not there, the reference to that file is removedfrom the recovery catalog and the control file.The unavailable operand is provided for cases when the file cannot be foundor has migrated off site.A file that is marked unavailable will not be used in arestore or recover command.If the file is later found or returns to the main site,then it can be marked available again by using the available operand.The change command operates only on files that are recorded in the recoverycatalog (or the control file) and belong to the current database incarnation.Thesame is true for other commands except catalog and resync fromcontrolfilecopy.Deleting a Catalog Record: ExampleIf a cataloged file is deleted through some means other than RecoveryManager, or is otherwise lost or damaged, then the catalog record should bedeleted.If the file is on disk:change datafilecopy delete;change archivelog delete;Performing Backup and Recovery with Recovery Manager 8-7If the file is stored by a Media Manager:allocate channel for delete type  tape ;change backuppiece delete;release channel;You can obtain the primary keys of the records to be deleted by issuing a listcommand.Deleting many Catalog Records: ExampleIf you need to reconcile the recovery catalog with what is on disk when a largenumber of files have already been deleted, you may wish to use the change.validate command:change datafilecopy validate;change archivelog all validate;Cataloging User-Created Backup FilesOften it is useful to make Recovery Manager aware of the existence of filecopies which are created via means other than Recovery Manager.You can use the catalog command to add information to the recovery catalogand control file about a datafile copy, archivelog, or controlfile copy.Note that Oracle 8.x continues to support the ALTER TABLESPACE BEGIN/END BACKUP which allows open database operating system backups to bemade.Although Recovery Manager does not create such backups, they can beadded to the recovery catalog so that Recovery Manager is aware of them.Any such backup must be accessible on disk, and must be a complete imagecopy of a single file.A datafile backup may be either a consistent orinconsistent whole database, tablespace or datafile backup.Recovery Mangertreats all such backups as datafile copies.For example, if datafiles are stored on mirrored disk drives, then it is possibleto create an operating system copy by simply breaking the mirror.In thisscenario, the catalog command is used to notify Recovery Manager of theexistence of the operating system copy after breaking the mirror.Before themirror is reformed, a change.uncatalog command should be issued tonotify Recovery Manager that the file copy is being deleted.The catalog command is restricted to cataloging only those files associatedwith the current incarnation of the database.Archivelogs and control filecopies that were created from version 7.x or earlier cannot be cataloged.8-8 Oracle8 Backup and Recovery GuideDatafile copies which were created from version 7.x or earlier can be catalogedif the file belongs to a tablespace which was offline normal or read-only whenthe database was migrated to Oracle8.Recovering a Lost or Damaged Recovery Catalog DatabaseIf the recovery catalog database is lost or damaged, and recovery of therecovery catalog database via the normal Oracle recovery mechanisms is notpossible, then there are two options for partially re-creating its contents:1.Issue catalog commands to re-catalog archivelogs, backup control files,and datafile copies.2.Use the resync catalog from backup controlfile command to extractinformation from a backup control file and rebuild the recovery catalogfrom it [ Pobierz całość w formacie PDF ]