參考教程說明tspitr

1、Performing Tablespace Point-in-Time RecoveryObjectivesAfter completing this lesson, you should be able to:List what operations occur when you perform tablespace point-in-time recovery (TSPITR)Define the terminology used with TSPITRIdentify the circumstances where TSPITR is a good solutionDetermine t

2、he correct target time for the point-in-time recoveryIdentify those situations where TSPITR cannot be used, and how to work around themPerform automated TSPITRTablespace Point-in-Time Recovery (TSPITR): Concepts TSPITR enables you to quickly recover one or more tablespaces to an earlier time.TSPITR

3、does not affect the state of other tablespaces or objects in the database.Tablespace Point-in-Time Recovery (TSPITR): Terminology Target time: The point in time or SCN that the tablespace will be recovered toRecovery set: Data files that compose the tablespaces to be recoveredAuxiliary set: Data fil

4、es required for the TSPITR of the recovery set that are not part of the recovery set. It typically includes:SYSTEM tablespaceUndo segment tablespacesTemporary tablespaceAuxiliary destination: Disk location to store filesTablespace Point-in-Time Recovery: ArchitectureTarget databaseAuxiliary instance

5、RMANData filebackupsArchived redo log filesRecovered tablespace12Control fileRestoreRecoverRestoreTablespace Point-in-Time Recovery: ArchitectureTarget databaseAuxiliaryinstanceRMANRecoveredtablespace43ExportfileControl file5ExportmetadataPoint to recovered tablespaceImport metadataWhen to Use TSPIT

6、RTSPITR can be used in the following situations:To recover data lost after an erroneous TRUNCATE TABLE statementTo recover from logical corruption of a tableTo undo the effects of a batch job or DML statements that have affected only a part of the databaseTo recover a logical schema to a different p

7、oint from the rest of the physical databaseTSPITR cannot be used to:Recover a dropped tablespaceRecover a renamed tablespace to a point before it was renamedPreparing for TSPITRTo prepare for TSPITR, perform the following steps:Determine the correct target time.Determine what is needed in the recove

8、ry set.Identify and preserve objects that will be lost after TSPITR.Determining the Correct Target TimeYou cannot perform TSPITR a second time unless you are using a recovery catalog.After you perform TSPITR and bring the tablespace online, you cannot use a backup from an earlier time.Use the follow

9、ing methods to determine the correct target time:Flashback QueryFlashback Transaction QueryFlashback Version QueryDetermining the Tablespaces for the Recovery SetUse the TS_PITR_CHECK view to identify relationships that span recovery set boundaries.If objects in the tablespace that you are recoverin

10、g have relationships with objects in other tablespaces, you can:Add the tablespace that contains the related objects to the recovery setSuspend the relationship for the duration of TSPITRRemove the relationshipIdentifying Objects That Will Be LostObjects created in the tablespace after the target re

11、covery time are lost.Query TS_PITR_OBJECTS_TO_BE_DROPPED to determine which objects will be lost following TSPITR.Use Export prior to TSPITR and Import following TSPTIR to preserve and re-create the lost objects.Performing Basic RMAN TSPITRFully automated TSPITR Specify an auxiliary destination.RMAN

12、 manages all aspects of TSPITR.This is the mended method.Customized TSPITR with an automatic auxiliary instanceThis is based on fully automated TSPITR.Customize the location of files.Specify initialization parameters.Specify channel configurations.TSPITR using your own auxiliary instanceConfigure an

13、d manage the auxiliary instance.Performing Fully Automated TSPITRConfigure channels required for TSPITR on the target instance.Specify the auxiliary destination using the AUXILIARY DESTINATION option.Back up the recovered tablespaces and bring them online.RMAN CONNECT TARGETRMAN RECOVER TABLESPACE u

14、sers, example UNTIL TIME 2007-06-29:08:00:00 AUXILIARY DESTINATION /u01/app/oracle/oradata/aux; Using Enterprise Manager to Perform TSPITRRMAN TSPITR ProcessingRMAN performs the following steps:Creates the auxiliary instance, starts it, and connects to itTakes the tablespaces that will be recovered

15、offlineRestores a backup control file from a point in time before the target time to the auxiliary instanceRestores the data files from the recovery set and the auxiliary set to the auxiliary instanceRecovers the restored data files to the specified timeOpens the auxiliary database with the RESETLOG

16、S optionRMAN TSPITR ProcessingExports the dictionary metadata about objects in the recovered tablespaces to the target databaseShuts down the auxiliary instanceImports the dictionary metadata from the auxiliary instance to the target instanceDeletes all auxiliary set filesPerforming RMAN TSPITR with

17、 an RMAN-Managed Auxiliary InstanceRename or relocate your recovery set data files.Specify a location other than the auxiliary destination for some or all of the auxiliary set data files.Create image copy backups of your data files in advance of TSPITR.Use a different channel configuration for the a

18、uxiliary instance.Specify different initialization parameters for your RMAN-managed auxiliary instance.Performing RMAN TSPITR Using Your Own Auxiliary InstanceNot mended, but supportedPerform the following steps:Create an Oracle password file for the auxiliary instance.Create an initialization param

19、eter file for the auxiliary instance.Verify Oracle Net connectivity to the auxiliary instance.Start the auxiliary instance in NOMOUNT mode.Connect the RMAN client to the target and auxiliary instances.Execute the RECOVER TABLESPACE command.Troubleshooting RMAN TSPITRFile name conflicts: Ensure that there are no name conflicts when using SET NEWNAME, CONFIGURE AUXNAME, and DB_FILE_NAME_CONVERT.RMAN cannot identify tablespaces with