Sometime ORACLE just make you crazy and this is one of those scenarios. Here I share with one of my dirty hour with ORACLE.
cmd> sqlplus /nolog
sql> connect / as sysdba
sql> startup mount
if ORA-01081: cannot start already-running ORACLE - shut it down first
sql> shutdown abort
sql> startup mount
sql> alter database archivelog
sql> alter database open
if not successful and getting extra error like:
ORA-16038: log 1 sequence# blah blan cannot be archived
ORA-19809: limit exceeded for recovery files
and more ....
sql>e exit
cmd> sqlplus /nolog
sql> connect / as sysdba
sql> alter database open
if error like:
ORA-16014
ORA-00312
sql> recover database using backup controlefile until cancel;
some stuff appear
ORA - ...
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Press ENTER and wait till it finishes and you get sql>!!!
sql> alter database open resetlogs;
Congratulation your in.!!!
cmd> sqlplus /nolog
sql> connect / as sysdba
sql> startup mount
if ORA-01081: cannot start already-running ORACLE - shut it down first
sql> shutdown abort
sql> startup mount
sql> alter database archivelog
sql> alter database open
if not successful and getting extra error like:
ORA-16038: log 1 sequence# blah blan cannot be archived
ORA-19809: limit exceeded for recovery files
and more ....
sql>e exit
cmd> sqlplus /nolog
sql> connect / as sysdba
sql> alter database open
if error like:
ORA-16014
ORA-00312
sql> recover database using backup controlefile until cancel;
some stuff appear
ORA - ...
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Press ENTER and wait till it finishes and you get sql>!!!
sql> alter database open resetlogs;
Congratulation your in.!!!
No comments:
Post a Comment