cannot allocate log, archival required

[jee]

Hi friends,

ORACLE 8, WIN NT

database in archivelog mode

When i am inserting 50,000 records in a table , i am getting the following message continuously

cannot allocate log, archival required.

press enter to acknowledge the message

why i am getting this error. what is the use or remedy for the same?

Thanks in advance

Regards,
Jee

[aracnid]

check the space in your disk where the logs are alocated.

[drishti]

I was also encountering the same error while heavy data inserts.i think this is because archiver process r not being able to write all redologs before redologs get filled up.you can also remove some arc files from archive directory and see.

[Halo]

Increase the size of the redo log files, you may want to add more groups(s).

[tamilselvan]

If REDO is not important while 50000 rows are inserted, change table to nologging. This will generate minimum redo info and also needs minimum rollback segment.

Otherwise, increase the size of REDO LOG and ROLLBACK SEGMENT.

[Mark_Woz]

I was doing an import (commit=y)
of a number of tables, some small,
some large. I got the same error
when it imported a table with 500 000 records.

I added a redo log group - no success

I attempted to solve the problem by increasing
LOG_ARCHIVE_BUFFERS and decreasing
LOG_ARCHIVE_BUFFER_SIZE to speed up the
ARCH process - no success.

Luckily, the error does not abort the import - it
just seems to slow it down.

[jmodic]

Check the alert file to see the accompaniing ORA error message. Most probably your archiving destination disk is full or you have archiving process set to manual archiving and all your redo-logs are full, so oracle can not switch to new redo-log. In this case you have to perform archiving manualy.

HTH,

[Mark_Woz]

Oracle 8, WIN NT

Archive disk is not full.
Archiving was set to automatic.
I will check the alert log.
My next try will be to make the redo log files
REALLY big.
Why is it I can't increase LOG_ARCHIVE_BUFFERS
greater than 5 ?

[Mark_Woz]

Interesting - no ORA ERROR message appears
in the ALERT LOG, just a 'warning' that a log cannot
be allocated.

Adding a few groups of redo logs works
AND/OR
Making your redo logs bigger also helps.