Ora-00366 error occurs when running a long batch

Ora-00366 error occurs when running a long batch .

Redo Log File size is around 50MB .

what's the cause ?

It looks like you may have a corrupt redo log file

Regards

That's the error desc , if you missed checking it.

ORA-00366 log string of thread string, checksum error in the file header

Cause: The file header for the redo log contains a checksum that does not match the value calculated from the file header as read from disk. This means the file header is corrupted.

Action: Find and install correct version of the log or reset the logs

Can "alter system switch logfile' helpful in this case

Hey Jim,

Gave a new look to your website, I see!

cheers!!

Tarry

Hi Tarry,

I took a look a PHP and went a bit mad-for-it :)

Regards

Hey , gurus , Please advise ,

I want to create new redo log group and drop all the current redo log group . How do you think ?

to drop
ALTER DATABASE xxxx DROP LOGFILE GROUP x1;
to make
ALTER DATABASE xxxx
ADD LOGFILE GROUP x1
('diska/logx.log',
'diskb/logx.log',
'diskc/logx.log' );

I wonder what effect it might have forcing archiving of that corrupted file.

since it deals with corruption, take care in checking all pros and cons.

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!!

The Redo log group(3 groups) has only one log file , in this case , can do switch on corrupt log file ?

sure

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

Quote:

---

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.