Message in Alert Log About Archive Logs

[Michael42]

Hello,

On an Oracle 9.2.0.6 database on a Solaris 8 system in my alert log I am getting the following type messages:

Unable to archive log 4 thread 1 sequence 48
Log activity being archived by another process

(...repeats a few times then)

Completed archiving log 4 thread 1 sequence 48

Though everything seems to be working OK, is this anything I should be concerned about?

Thanks,

Michael42

 

[alexhu]

Any hardware messages (disk errors) ?

Alex

 

[sem]

Have you (administrator) changed anything related to logs (add/drop member etc) at that time? If so this message is just a kind of feedback, don't worry.

Regards, Dima

http://seminihin.narod.ru

 

[SantaMufasa]

Michael,

This problem usually occurs because you are generating so much redo that your on-line redo log files are filling and needing to be archived faster than the archive process can archive the log files. A way to avoid this from happening is to recreate your on-line redo log files to be much larger, thus taking longer to fill.

Try that and let us know if the diagnostic disappears.

Mufasa
(aka Dave of Sandy, Utah, USA)

http://www.dasages.com

Do you use Oracle and live or work in Utah, USA?
Then click here to join Utah Oracle Users Group on Tek-Tips.

 

[Michael42]

Hey all,

>> Any hardware messages (disk errors) ?

After checking it seems the disks are ok.

>> Have you (administrator) changed anything related to logs

No - but good point.

>> This problem usually occurs because you are generating so much redo that

Actually I feel my redo log file size is too big (500mb each) and I'd like to bring them down to 250mb or so in time.

Guys, great suggestions. This is a tuff one. I appreciate your feedback. Any other thoughts?

Thanks,

Michael42

 

[hoinz]

Hi,

I have a similar message in my alert log:
Log actively being archived by another process

Is yours cut-and-paste or a typo?

As far as I know my message is due to two archive processes running on my system, and it is just a feedback, not an error.

regards

 

[stefanhei]

You usually see this message when you have more ARCH-processes than log_archive_dest's (check log_archive_max_processes). It's just a warning telling you have "idle" archive-processes.

Stefan