| Need to bypass recovery when opening database. [message #51462] |
Thu, 23 May 2002 13:32  |
cobus
Messages: 3
Registered: May 2002
|
Junior Member |
|
|
Hi all,
We have lost all redo, archive, control files. I managed to get database mounted but when I open it I get an ORA-0600. Is there a way to bypass recovery and open database files without recovery.
|
|
|
|
|
|
|
|
| Re: Need to bypass recovery when opening database. - Solution [message #51477 is a reply to message #51462] |
Fri, 24 May 2002 06:37  |
cobus
Messages: 3
Registered: May 2002
|
Junior Member |
|
|
Hi all,
Thanks for the interest in my problem.
I have however managed to solve the problem by doing the following (The database is inconsistent but in this specific case it does not matter):
Do these steps to recover.
1. Restore original online backups files from backup media. System,Rollback and 1 or more User tablespaces.
2. Make sure this is not in the init file:
#_allow_resetlogs_corruption = true
#_allow_read_only_corruption = true
3. In svrmgrl - Create controlfile
connect internal
STARTUP NOMOUNT
CREATE CONTROLFILE DATABASE "ORCL" RESETLOGS NOARCHIVELOG
MAXLOGFILES 32
MAXLOGMEMBERS 2
MAXDATAFILES 32
MAXINSTANCES 16
MAXLOGHISTORY 1815
LOGFILE
GROUP 1 'D:ORACLEORADATAORCLREDO03.LOG' SIZE 1M,
GROUP 2 'D:ORACLEORADATAORCLREDO02.LOG' SIZE 1M,
GROUP 3 'D:ORACLEORADATAORCLREDO01.LOG' SIZE 1M
DATAFILE
'D:ORACLEORADATAORCLSYSTEM01.DBF',
'D:ORACLEORADATAORCLrbs01.DBF',
'D:ORACLEORADATAORCLUSERS01.DBF'
CHARACTER SET WE8ISO8859P1
;
4. Recover database
recover database until cancel using backup controlfile;
5. Cancel the recovery
CANCEL
6. Open with resetlogs
alter database open resetlogs;-- Should get ORA-01195
7. Stop db.
shutdown;
8. Now add this to init file
_allow_resetlogs_corruption = true
_allow_read_only_corruption = true
9. In svrmgrl
startup mount
10. Do resetlogs again (and hope for success here)
alter database open resetlogs;
Cobus
|
|
|
|
| Re: Need to bypass recovery when opening database. [message #51479 is a reply to message #51475] |
Fri, 24 May 2002 06:53 |
cobus
Messages: 3
Registered: May 2002
|
Junior Member |
|
|
Hi all,
Thanks for the interest in my problem.
I have however managed to solve the problem by doing the following (The database is inconsistent but in this specific case it does not matter):
Do these steps to recover.
1. Restore original online backups files from backup media. System,Rollback and 1 or more User tablespaces.
2. Make sure this is not in the init file:
#_allow_resetlogs_corruption = true
#_allow_read_only_corruption = true
3. In svrmgrl - Create controlfile
connect internal
STARTUP NOMOUNT
CREATE CONTROLFILE DATABASE "ORCL" RESETLOGS NOARCHIVELOG
MAXLOGFILES 32
MAXLOGMEMBERS 2
MAXDATAFILES 32
MAXINSTANCES 16
MAXLOGHISTORY 1815
LOGFILE
GROUP 1 'D:ORACLEORADATAORCLREDO03.LOG' SIZE 1M,
GROUP 2 'D:ORACLEORADATAORCLREDO02.LOG' SIZE 1M,
GROUP 3 'D:ORACLEORADATAORCLREDO01.LOG' SIZE 1M
DATAFILE
'D:ORACLEORADATAORCLSYSTEM01.DBF',
'D:ORACLEORADATAORCLrbs01.DBF',
'D:ORACLEORADATAORCLUSERS01.DBF'
CHARACTER SET WE8ISO8859P1
;
4. Recover database
recover database until cancel using backup controlfile;
5. Cancel the recovery
CANCEL
6. Open with resetlogs
alter database open resetlogs;-- Should get ORA-01195
7. Stop db.
shutdown;
8. Now add this to init file
_allow_resetlogs_corruption = true
_allow_read_only_corruption = true
9. In svrmgrl
startup mount
10. Do resetlogs again (and hope for success here)
alter database open resetlogs;
Cobus
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
