Ora-00366 error occurs when running a long batch

[Tarry]

sure

[diwakar]

Hello everyone,

How about taking a complete export backup with consistent=y before resetting the logfiles and then a complete cold back up after the log files are reset.

Correct me if Iam wrong...

K.Diwakar

[nagarjuna]

Originally posted by Tarry
On another note,
you can
Diagnose
________
Check alert log.
query : select * from v$logfile

Repair
______

See if is on yr system
Select * from v$logfile
check it on the OS given directory.

Make the group with corrupt logfile inactive
select group# , status
from v$log;

If active, make him inactive by

alter system switch logfile;

chk

select group# , status
from v$log;

drop the invalid file:

alter database drop logfile member '/blah/blah';

do

select * from v$logfile;

recreate

alter database add logfile member 'blah/blah';

do alter system switch logfile;
asmany time as there are groups atleast.
then query

select * from v$logfile;

there shud be no invalid logfiles anymore.

And also about the checksum story,
If one of your logfile has checksum probs, it'll still look for the other and move on, but if all have checksum trouble the db will hand,
You can also issue to re initialize the redo logfile

alter database clear logfile;(after making it non current, if current).

Cheers!!

noooo way you can switch a log file if it is corrupted. You have to go for in complete media recovery.