Help - Search - Members - Calendar
Full Version: Error while Importing data
Oracle DBA Forums > Oracle > Oracle Forum
Anupama Vadlapudi
Hi All,


while am doing import ,i have got the error that log is not archived.here is the screen shot of the error for you are reference.Please do reply soon...
dave
do you have space?
what version?
is automatic archival turned on
HAL9000
"ORACLE Instance NNNN - Cannot allocate log. Archival required"

Automatic archiving has been disabled.

In this case the database will also appear to hang. This can be verified by issuing the command:

Archive log list;

If this displays ‘Automatic archival Disabled’ then automatic archiving has been disabled. Archive the redo logs manually by issuing the command:

Alter system archive log all;

A better long term solution is to modify the init<SID>.ora file and set the parameter ‘LOG_ARCHIVE_START’ to ‘True’.

The archive log space is exhausted. Check that there is sufficient disk space in the directory receiving the archive logs.

There is very heavy database activity and this activity means that the database is generating redo logs faster than it can archive them. Database activity will still continue - once the archive process ‘catches up’.

If this is the case then the following may help:

Ensure that redo logs and archive logs are being written to different disks.

Add extra redo log groups.

This can be done without taking the database down, for example:

alter database add logfile group 3 'C:\ORANT\DATABASE\LOG3ORCL_1.ORA' SIZE 1M;

Increase the size of the redo logs. Whilst Oracle does not provide a way of resizing the redo logs the same effect can be achieved by deleting a redo log file and then adding it again with the new size, for example:

alter database drop logfile 'C:\ORANT\DATABASE\LOG3ORCL1.ORA';
alter database add logfile 'C:\ORANT\DATABASE\LOG3ORCL1.ORA' SIZE 2M;

Do ensure that there are always at least two available redo logs.

Consider increasing either or both of the initialisation parameters LOG_ARCHIVE_BUFFER_SIZE and LOG_ARCHIVE_BUFFERS.

If this error occurs during one-off loading of data into the database then either ignore the error or consider running the database in non-archive-log mode for the data loading.
Anupama Vadlapudi
QUOTE (dave @ Jul 21 2008, 02:34 PM) *
do you have space?
what version?
is automatic archival turned on


Hi Dave,

Actually my oracle version is 9i & automatic archival is also enabled.What exactly i did is i deleted some of the archives files to free some space in the disk..Then my import process started but am not at satisfied still..i mean still i need to get a better solution to do fast import..





~Cheers
Anupama

QUOTE (HAL9000 @ Jul 21 2008, 02:44 PM) *
"ORACLE Instance NNNN - Cannot allocate log. Archival required"

Automatic archiving has been disabled.

In this case the database will also appear to hang. This can be verified by issuing the command:

Archive log list;

If this displays ‘Automatic archival Disabled’ then automatic archiving has been disabled. Archive the redo logs manually by issuing the command:

Alter system archive log all;

A better long term solution is to modify the init<SID>.ora file and set the parameter ‘LOG_ARCHIVE_START’ to ‘True’.

The archive log space is exhausted. Check that there is sufficient disk space in the directory receiving the archive logs.

There is very heavy database activity and this activity means that the database is generating redo logs faster than it can archive them. Database activity will still continue - once the archive process ‘catches up’.

If this is the case then the following may help:

Ensure that redo logs and archive logs are being written to different disks.

Add extra redo log groups.

This can be done without taking the database down, for example:

alter database add logfile group 3 'C:\ORANT\DATABASE\LOG3ORCL_1.ORA' SIZE 1M;

Increase the size of the redo logs. Whilst Oracle does not provide a way of resizing the redo logs the same effect can be achieved by deleting a redo log file and then adding it again with the new size, for example:

alter database drop logfile 'C:\ORANT\DATABASE\LOG3ORCL1.ORA';
alter database add logfile 'C:\ORANT\DATABASE\LOG3ORCL1.ORA' SIZE 2M;

Do ensure that there are always at least two available redo logs.

Consider increasing either or both of the initialisation parameters LOG_ARCHIVE_BUFFER_SIZE and LOG_ARCHIVE_BUFFERS.

If this error occurs during one-off loading of data into the database then either ignore the error or consider running the database in non-archive-log mode for the data loading.


Hi,

Actually my oracle version is 9i & automatic archival is also enabled.What exactly i did is i deleted some of the archives files to free some space in the disk..Then my import process started but am not at satisfied still..i mean still i need to get a better solution to do fast import..
SteveC
Simple search on Google "oracle speed up import"
http://www.dba-oracle.com/oracle_tips_load_speed.htm
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.