-
pando, this is your response for "lost all control file, all redo logs"
=========================
1. shutdown the database
2. Recover latest backup
3. startup nomount
4. create control file
5. recover database until cancel using backup controlfile;
this will recover using the archived logs until you stop it
6. alter database open resetlogs;
database should open successfully
You dont need to drop/recreate redo logs sicne resetlogs will create the log groups
==========================
could you please give some idea why need step 4, "recreate controlfile", since there is a backup controlfile and "resetlogs" will resync controlfile there is no need to recreate it. In face, I tried, without step 4, db can be openned but will complain password file, why?
thanks in advance
Jim
-
I suggested step 4 because I assumed the person had a backup controlfile with to trace option and not binary.
The password file error you are getting has nothing to do with this, that is because you have remote_password_file=shared in your initSID.ORA which requires a password file when Oracle starts, the error is indicating you that there isnt such password file, simply change remote_password_file=none should work
-
pando,
thanks for your response.
I check my init.ora,
remote_login_passwordfile = EXCLUSIVE
when I start oracle, it works. the password error happened when I try to use rman (nocatalog) do backup. if I do the step 4, no password error.
if I change to NONE, this error will disappear?
thanks
-
well check if you have a password file before you try it, I havent faced a problem with password files and RMAN together so I cant say anything here but normally when I see the password file error most of the times its because of that parameter and lack of a password file.
EXCLUSIVE is similar as SHARED but for Parallel Server. if you use EXCLUSIVE only user SYS can connect as SYSDBA or SYSOPER.
-
thanks, let me try few more times. hopfully I can figure out what I did wrong.