Pokrewne
- Strona Główna
- Andrzejewski Jerzy Ciemnosci kryja ziemie
- eBooks.PL.AutoCad.2005. (3)
- George R.R. Martin 3 Nawałnica mieczy cz.1
- Etiquette in Society, in Business, in Politics and at Home
- Farrel Joseph P. Wojna nuklearna sprzed 5 tysicy lat
- Brown Dan Anioly i demony
- Corel DRAW (4)
- Campbell Joseph The Masks Of God Primitive Mythology
- Ludlum Robert Tozsamosc Bourne'a (2)
- Dzieła ÂŚw. Jan od Krzyża
- zanotowane.pl
- doc.pisz.pl
- pdf.pisz.pl
- oh-seriously.htw.pl
[ Pobierz całość w formacie PDF ]
.The time is always specified using the following format,delimited by single quotation marks: YYYY-MM-DD:HH24:MI:SS.11.Oracle begins the roll forward phase of media recovery by applying thenecessary redo log files (archived and online) to reconstruct the restoreddatafiles.Unless the application of files is automated, Oracle suppliesthe name it expects to find from LOG_ARCHIVE_DEST and requestsyou to stop or proceed with applying the log file.If the control file is abackup file, you must supply names of online logs.Oracle continues toapply redo log files.12.Continue applying redo log files until the last required redo log file hasbeen applied to the restored datafiles.Oracle automatically terminatesthe recovery when it reaches the correct time, and returns a messageindicating whether recovery is successful.Opening the Database After Successful Time-based RecoveryThe first time you open the database subsequent to incomplete mediarecovery, you must explicitly specify whether to reset the log sequencenumber by including either the RESETLOGS or NORESETLOGS option.Resetting the redo log:" discards any redo information that was not applied during recovery,ensuring that it will never be applied" reinitializes the control file information about online redo logs and redothreadsRecovering a Database 11-27 " clears the contents of the online redo logs" creates the online redo log files if they do not currently exist" resets the log sequence number to 1Warning: Resetting the redo log discards all changes to the database madesince the first discarded redo information.Updates entered after that timemust be re-entered manually.Use the following rules when deciding to specify RESETLOGS orNORESETLOGS:" Reset the log sequence number if you used a backup of the control filein recovery, no matter what type of recovery was performed (completeor incomplete)." Reset the log sequence number if the recovery was actually incomplete.For example, you must have specified a previous time or SCN, not onein the future." Do not reset logs if recovery was complete (unless you used a backupcontrol file).This applies when you intentionally performed completerecovery and when you performed incomplete recovery but actuallyrecovered all changes in the redo logs anyway.See the explanation instep 12 for how to examine the ALERT file to see if incomplete recoverywas actually complete." Do not reset logs if you are using the archived logs of this database for astandby database.If the log must be reset, then you will have to re-createyour standby database.To preserve the log sequence number when opening a database afterrecovery, use the SQL command ALTER DATABASE with the OPENNORESETLOGS option.To reset the log sequence number whenopening a database after recovery, use the SQL command ALTERDATABASE with the OPEN RESETLOGS option.(If you attempt toreset the log when you should not, or if you neglect to reset the log whenyou should, Oracle returns an error and does not open the database.Correct the error and try again.)If the log sequence number is reset when opening a database, differentmessages are returned, depending on whether the recovery wascomplete or incomplete.If the recovery was complete, the followingmessage appears in the ALERT file:RESETLOGS after complete recovery through change scn11-28 Oracle8 Backup and Recovery Guide If the recovery was incomplete, the following message is reported in theALERT file:RESETLOGS after incomplete recovery UNTIL CHANGE scnIf you reset the redo log sequence when opening the database, immediatelyshut down the database normally and make a whole database backup.Otherwise, you will not be able to recover changes made after you reset thelogs.Until you take a whole database backup, the only way to recover will beto repeat the procedures you just finished, up to resetting the logs.(You do notneed to back up the database if you did not reset the log sequence [ Pobierz całość w formacie PDF ]
zanotowane.pl doc.pisz.pl pdf.pisz.pl agnieszka90.opx.pl
.The time is always specified using the following format,delimited by single quotation marks: YYYY-MM-DD:HH24:MI:SS.11.Oracle begins the roll forward phase of media recovery by applying thenecessary redo log files (archived and online) to reconstruct the restoreddatafiles.Unless the application of files is automated, Oracle suppliesthe name it expects to find from LOG_ARCHIVE_DEST and requestsyou to stop or proceed with applying the log file.If the control file is abackup file, you must supply names of online logs.Oracle continues toapply redo log files.12.Continue applying redo log files until the last required redo log file hasbeen applied to the restored datafiles.Oracle automatically terminatesthe recovery when it reaches the correct time, and returns a messageindicating whether recovery is successful.Opening the Database After Successful Time-based RecoveryThe first time you open the database subsequent to incomplete mediarecovery, you must explicitly specify whether to reset the log sequencenumber by including either the RESETLOGS or NORESETLOGS option.Resetting the redo log:" discards any redo information that was not applied during recovery,ensuring that it will never be applied" reinitializes the control file information about online redo logs and redothreadsRecovering a Database 11-27 " clears the contents of the online redo logs" creates the online redo log files if they do not currently exist" resets the log sequence number to 1Warning: Resetting the redo log discards all changes to the database madesince the first discarded redo information.Updates entered after that timemust be re-entered manually.Use the following rules when deciding to specify RESETLOGS orNORESETLOGS:" Reset the log sequence number if you used a backup of the control filein recovery, no matter what type of recovery was performed (completeor incomplete)." Reset the log sequence number if the recovery was actually incomplete.For example, you must have specified a previous time or SCN, not onein the future." Do not reset logs if recovery was complete (unless you used a backupcontrol file).This applies when you intentionally performed completerecovery and when you performed incomplete recovery but actuallyrecovered all changes in the redo logs anyway.See the explanation instep 12 for how to examine the ALERT file to see if incomplete recoverywas actually complete." Do not reset logs if you are using the archived logs of this database for astandby database.If the log must be reset, then you will have to re-createyour standby database.To preserve the log sequence number when opening a database afterrecovery, use the SQL command ALTER DATABASE with the OPENNORESETLOGS option.To reset the log sequence number whenopening a database after recovery, use the SQL command ALTERDATABASE with the OPEN RESETLOGS option.(If you attempt toreset the log when you should not, or if you neglect to reset the log whenyou should, Oracle returns an error and does not open the database.Correct the error and try again.)If the log sequence number is reset when opening a database, differentmessages are returned, depending on whether the recovery wascomplete or incomplete.If the recovery was complete, the followingmessage appears in the ALERT file:RESETLOGS after complete recovery through change scn11-28 Oracle8 Backup and Recovery Guide If the recovery was incomplete, the following message is reported in theALERT file:RESETLOGS after incomplete recovery UNTIL CHANGE scnIf you reset the redo log sequence when opening the database, immediatelyshut down the database normally and make a whole database backup.Otherwise, you will not be able to recover changes made after you reset thelogs.Until you take a whole database backup, the only way to recover will beto repeat the procedures you just finished, up to resetting the logs.(You do notneed to back up the database if you did not reset the log sequence [ Pobierz całość w formacie PDF ]