-
Inconsistent archive error
Hi Guys,
I have a database running 8.1.7.4, hit the below error, but db still in working order, cos the archiving was able to complete.It says FAIL and later on SUCCESSFUL. But the error has been coming up very frequent, as much as 3 times daily.
Any idea why this is happening ?
Tue Mar 18 06:08:09 2003
ARC0: Beginning to archive log# 1 seq# 29038
ARC0: Failed to archive log# 1 seq# 29038
Tue Mar 18 06:08:09 2003
ARCH: Completed archiving log# 1 seq# 29038
Tue Mar 18 06:08:09 2003
Thread 1 advanced to log sequence 29040
Current log# 3 seq# 29040 mem# 0: /opt/oracle/oradata/livedb/redo03.log
Tue Mar 18 06:08:09 2003
ARCH: Beginning to archive log# 2 seq# 29039
Tue Mar 18 06:08:09 2003
ARC0: Beginning to archive log# 2 seq# 29039
ARC0: Failed to archive log# 2 seq# 29039
Tue Mar 18 06:08:09 2003
ARCH: Completed archiving log# 2 seq# 29039
Regards
CF
-
Hi
Is there somethin wrong with the disks..whats the size of your online redologs..
how is the placement of your online redologs..
whats the version of opearting system ?
are there any other files being produced in the bdump directory..
regards
Hrishy
-
Hi
Tue Mar 18 06:08:09 2003
ARCH: Beginning to archive log# 2 seq# 29039
Tue Mar 18 06:08:09 2003
ARC0: Beginning to archive log# 2 seq# 29039
ARC0: Failed to archive log# 2 seq# 29039
At Tue Mar 18 06:08:09 2003 ARCH started and before completeing another archiver process ARC0 started at Tue Mar 18 06:08:09 2003. Why there are two archive processor at a time? It seems the second archiver processor fails while the first one is active.
Thomas
-
Hi
Good catch thomasapps..can you please post your init.ora file here..
regards
Hrishy
-
hrishy
I think the %t, (OPS, thread number in log_archive_format) making the issue.
Thomas
-
Hi Thomas
Lets see when he posts the init.ora file..:-)
regards
Hrishy
-
Hi Guys,
very sorry, my mistake in copying the errors : here is the actual copy.
ARCH: Beginning to archive log# 1 seq# 29038
Tue Mar 18 06:08:09 2003
Current log# 2 seq# 29039 mem# 0: /opt/bt1oracle/oradata/citospro/redo02.log
Tue Mar 18 06:08:09 2003
ARC0: Beginning to archive log# 1 seq# 29038
ARC0: Failed to archive log# 1 seq# 29038
Tue Mar 18 06:08:09 2003
ARCH: Completed archiving log# 1 seq# 29038
Tue Mar 18 06:08:09 2003
Thread 1 advanced to log sequence 29040
Current log# 3 seq# 29040 mem# 0: /opt/bt1oracle/oradata/citospro/redo03.log
Tue Mar 18 06:08:09 2003
ARCH: Beginning to archive log# 2 seq# 29039
Tue Mar 18 06:08:09 2003
ARC0: Beginning to archive log# 2 seq# 29039
ARC0: Failed to archive log# 2 seq# 29039
Tue Mar 18 06:08:09 2003
ARCH: Completed archiving log# 2 seq# 29039
Tue Mar 18 07:46:02 2003
Thread 1 advanced to log sequence 29041
Current log# 1 seq# 29041 mem# 0: /opt/bt1oracle/oradata/citospro/redo01.log
Tue Mar 18 07:46:02 2003
ARC0: Beginning to archive log# 3 seq# 29040
ARC0: Completed archiving log# 3 seq# 29040
# Uncommenting the lines below will cause automatic archiving if archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
log_archive_start = true
log_archive_dest = /opt/bt1oracle/admin/citospro/arch
log_archive_format = arch_%t_%s.arc
I have another database ( solaris 2.6 OS patch 105181-32) running the same version(8.1.7.4) with the above init.ora settings and did not hit this problem. The machine having problem is running on solaris 2.6 platform , kernel patch 105181-33
BTW, thanks guys for your propmt attention.
Regards
CF
-
Hi
I see that there are multiple archive process arch0 and arch1 can you do this in your database
ALTER SYSTEM SET LOG_ARCHIVE_MAX_PROCESSES=1
regards
Hrishy
-
log_archive_dest string /opt/bt1oracle/admin/citospro/arch
log_archive_dest_1 string
log_archive_dest_2 string
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_state_1 string enable
NAME TYPE VALUE
------------------------------------ ------- ------------------------------
log_archive_dest_state_2 string enable
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_duplex_dest string
log_archive_format string arch_%t_%s.arc
log_archive_max_processes integer 1
log_archive_min_succeed_dest integer 1
log_archive_start boolean TRUE
log_archive_trace integer 0
As you can see the log_archive_max_processes is set to 1.
Regards
CF
-
remove the thread number
Hi
log_archive_format:string arch_%t_%s.arc change this to
log_archive_format string arch_%s.arc. Since you got a single single instance %t (thread number) is not required. Normally %t or %T is using in OPS. Long back I read this some where, but not remember exactly why this is making the issue. (Try to make the change after a Full database backup ).
Thomas
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|