Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: CAN NOT ALLOCATE LOG,ARCHIVAL REQUIRED error
If I understand the problem correctly, the message just means that archive
process is falling behind the rate at which redo log records are generated.
If this is the case then you must be getting this message in separate window
(again I am assuming that you have oracle on NT) just as warning and not
error stalling import operation. The easiest way is to increase no. of redo
log groups.
-----Original Message-----
From: Bunyamin K.Karadeniz [mailto:bunyamink_at_havelsan.com.tr]
Sent: Monday, January 15, 2001 2:15 AM
To: Multiple recipients of list ORACLE-L
Subject: Re: CAN NOT ALLOCATE LOG,ARCHIVAL REQUIRED error
Thanks For your help BUT aS YOU SEE Automatic archival IS Enabled
SQL> archive log list
Database log mode Archive Mode Automatic archival Enabled Archive destination C:\dbmirror\DATABASE\TEST\ARCHIVE Oldest online log sequence 496 Next log sequence to archive 498 Current log sequence 498
>-----Original Message-----
>From: Bunyamin K.Karadeniz [ mailto:bunyamink_at_havelsan.com.tr
<mailto:bunyamink_at_havelsan.com.tr> ]
>Sent: vendredi, 12. janvier 2001 06:56
>
>CAN NOT ALLOCATE LOG,ARCHIVAL REQUIRED
>
>MESSAGE IS DISPLAYED WHEN I want to import a huge table;
>What must I do??? Thanks
Doesn't it mean that some of the logs need to be manually archived? Try typing in "archive log list" in svrmgr. Do you see the following?
SVRMGR> archive log list
Database log mode Archive Mode
Automatic archival Disabled
If Automatic archival is disabled you may need to do an "alter system archive log" (read the documentation for the correct syntax.
e.g.
SVRMGR> alter system archive log all ;
Jacques R. Kilchoer
(949) 754-8816
Quest Software, Inc.
8001 Irvine Center Drive
Irvine, California 92618
Received on Mon Jan 15 2001 - 10:09:20 CST