Printable View
hi,
One of my Redolog group is corrupted and unfortunately
it has only one member. My database is running in
Archivelog mode, but i don't have any old backup. How
can i open my database. I guess now i cannot do incomplete
recovery becoz i don't have any old backup. But all my
datafiles are intact. What can i do in this situation.
Regards
Try clearing the logfile..
Execute...
if it works successfully, take the hot/cold backup immediately..Code:ALTER DATABASE CLEAR LOGFILE GROUP n;
or
ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP n;
do what sameer said...
is the whole group corrupted or one of the files ??
what does your alert log file say ??
if it gives error then...
try to shutdown the database normally
startup mount and then try
ALTER DATABASE CLEAR UNARCHIVED LOGFILE '/u6/oradata/sid/redo_1a.log';
then try to open it and then do a nomal shutdown...
take a backup...
hi
i am getting following errors
SQL> alter database clear logfile group 2;
alter database clear logfile group 2
*
ERROR at line 1:
ORA-01624: log 2 needed for crash recovery of thread 1
ORA-00312: online log 2 thread 1: 'D:\ORADATA\LOG\LOG02.LOG'
SQL> alter database clear unarchived logfile group 2;
alter database clear unarchived logfile group 2
*
ERROR at line 1:
ORA-01624: log 2 needed for crash recovery of thread 1
ORA-00312: online log 2 thread 1: 'D:\ORADATA\LOG\LOG02.LOG'
hi,
I tried this option as well....
but it is not workingSQL> alter database clear logfile group 2 unrecoverable datafile;
SQL>alter database clear logfile group 2 unrecoverable datafile
*
ERROR at line 1:
ORA-01624: log 2 needed for crash recovery of thread 1
ORA-00312: online log 2 thread 1: 'D:\ORADATA\LOG\LOG02.LOG'
I think i this situation it is not possible to recover the database..
if its not then try shutting it down...
and do as i told you earlier....
im waiting for ur reply ....
How many groups you have? and How many members? If the DB is running then add new groups with 2 members... and then switch the log files till it uses the new one and then drop the old one... shutdown the DB take care complete backup...
Hope this is Helpfull:rolleyes:
Additional information:
Because log group 2 is the current log group, it will not have been archived. Using the CLEAR LOGFILE command is of no use because:
SQL> alter database clear unarchived logfile group 2;
ORA-01624: log 2 needed for crash recovery of thread 1
ORA-00312: online log 2 thread 1: 'disk1/archive/log2a.rdo'
Try Performing Incomplete recovery therefore, First you must note the current log sequence number by issuing this statement
SQL> select * from v$log;
Use the ALTER DATABASE DROP LOG GROUP and ALTER DATABASE ADD LOG GROUP commands to create the log files manually. Because you performed incomplete recovery, the database should now be backed up.
nabeel,
As i don't have old backup, now i can't do anything.
I think, Nothing can be done at this point.
Try :
ALTER DATABASE RECOVER DATABASE UNTIL CANCEL;
or
ALTER DATABASE RECOVER DATABASE USING BACKUP CONTROLFILE.
then
ALTER DATABASE OPEN RESETLOGS;
----
XD
Hei,
It seems that your instance crashed, and your lost redo log is needed by instance recovery.
In such case, the only solution is restore backup(no matter hot or cold) and do incomplete recovery.
If you really have no any backup, the only final solution is use undocumented parameter:
_allow_resetlogs_corruption= true.
and startup mount database,
Recover database until cancel
Cancel
Alter database open resetlogs.
Do full exp and rebuild your database.
Good luck.
I think _allow_resetlogs_corruption is the only solution you have since you have no backups. But it should be used only with Oracle's guidance. If you have Oracle support, then better take their help.
But if you want to do it on your own, then better take backup of current database, before using this parameter.
Do you realize this thread was TEN years old? :)Quote:
Originally Posted by DBAtom
I don't think that spammer's care. I would not buy from soaring turkey consulting, just because they spam a forum... :rolleyes:Quote:
Originally Posted by PAVB
How tacky is that!
SQL> startup
ORACLE instance started.
Total System Global Area 285212672 bytes
Fixed Size 1218992 bytes
Variable Size 117442128 bytes
Database Buffers 163577856 bytes
Redo Buffers 2973696 bytes
Database mounted.
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1:
'/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/redo01.log'
shut immediate
then again create the control file
SQL> startup nomount
Create controlfile reuse set database "chaitu"
MAXINSTANCES 8
MAXLOGHISTORY 1
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
Datafile
'/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/system01.dbf',
'/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/undotbs01.dbf',
'/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/sysaux01.dbf',
'/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/users01.dbf',
'/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/tb1.dbf',
'/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/tb2.dbf',
'/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/tb3.dbf'
LOGFILE GROUP 1 ('/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/redo01.log') SIZE 51200K,
GROUP 2 ('/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/redo02.log') SIZE 51200K,
GROUP 3 ('/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/redo03.log') SIZE 51200K
RESETLOGS;
Control file created.
SQL> alter database mount;
SQL> alter database open resetlogs;
try this it will work