SVRMGRL> startup mount
ORACLE instance started.
Total System Global Area 57939996 bytes
Fixed Size 75804 bytes
Variable Size 55693312 bytes
Database Buffers 1638400 bytes
Redo Buffers 532480 bytes
Database mounted.
SVRMGR> recover database until cancel;
ORA-00279: change 811845 generated at 08/08/2002 13:04:58 needed for thread 1
ORA-00289: suggestion : C:\ARCHIVEDREDOLOGS\HOUSTON\ARC01266.001
ORA-00280: change 811845 for thread 1 is in sequence #1266
Specify log: {=suggested | filename | AUTO | CANCEL}
Log applied.
ORA-00279: change 811846 generated at 08/08/2002 13:04:59 needed for thread 1
ORA-00289: suggestion : C:\ARCHIVEDREDOLOGS\HOUSTON\ARC01267.001
ORA-00280: change 811846 for thread 1 is in sequence #1267
ORA-00278: log file 'C:\ARCHIVEDREDOLOGS\HOUSTON\ARC01266.001' no longer needed
for this recovery
Specify log: {=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log 'C:\ARCHIVEDREDOLOGS\HOUSTON\ARC01267.001'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'C:\ORADATA\HOUSTON\SYS1HOUSTON.ORA'
the thing is ARC01267.001' never exists un the archive log so why Oracle ask for you??? is it b/c I have uncommit process when the database crash???
Please advise and solutions of how to fix this issues.
Option 1) Can you go from your last backup and apply archive log files up to just before the loss of online redo logs?
Option 2) Do you have a backup control file? You can create new online redo log files/groups/members. You will lose some data because of the loss of the orginal redo logs (otherwise, it would have been a case of instance recovery).
From MetaLink:
You accept the suggested archive log (by pressing Enter) and then receive
the following errors:
ORA-00308: cannot open archived log '%s'
ORA-07260: sfifi: stat error, unable to obtain information about file.
SVR4 Error: 2: No such file or directory
Checking for the file at the OS level confirms that the suggested archive log
does not exist. However, all archive logs prior to the suggested log exist.
Solution Description:
=====================
The change the database needs is most likely located in the current online
redo log. When the recovery process suggests the non-existent archive log,
you need to provide the path to the current online redo log. The current
log can be determined from the following query:
SELECT MEMBER
FROM V$LOGFILE F,
V$LOG L
WHERE L.STATUS = 'CURRENT'
AND L.GROUP# = F.GROUP#;
Once you know the current log, restart the recovery procedure and provide the
path to the log when prompted:
SVRMGR>recover database using backup controlfile;
ORA-00279: Change <#> generated at needed for thread <#>
ORA-00289: Suggestion:
ORA-00280: Change <#> for thread <#> is in sequence <#>
Specify log: {=suggested | filename | AUTO | CANCEL}
********************************************
* At this point, you should type in the *
* path to the current log and press enter. *
********************************************
Log applied.
Media recovery complete.
You should then be able to open the database:
SVRMGR> ALTER DATABASE OPEN RESETLOGS
The resetlogs option must be used to synchronize the controlfile.
Explanation:
============
When recovering using the backup control file, the database has no knowledge
of the current online redo logs. The change necessary is still in the current
online redo log but the database is forced to assume the change is in the next
consecutive archive log. This archive log has not yet been created.
Originally posted by stecal Option 1) Can you go from your last backup and apply archive log files up to just before the loss of online redo logs?
Stecal,
I am a little confused here, I do have the backup but how can I apply the archive log files up to just before the loss on online redo logs. How do I know which archive log is before the system crashed???
Bookmarks