From: Andre.van.Benthem@achmea.nl
Date: Thu Dec 23 2004 - 06:58:10 EST
Dear managers,
We are facing quite a while problems with our oracle archive-filestore.
The wait Q's for those disks are very high compared to other disks with much higher WKB/s then the archive-filestore.
When I do an "alter system switch logfile" even then there is WAITQ for the disk.
We have 2 archive-disks which are both striped-mirrorsets on different controllers on our HSG80īs,
both disks have the the same problem.
Non-archive disk have most of the time a WAITQ between 0 and 0.3
We regulary get oracle messages in the alert-file. see below:
Wed Dec 22 00:02:04 2004
ARC6: Beginning to archive log# 2 seq# 1208880
ARC6: Failed to archive log# 2 seq# 1208880
ARC6: Beginning to archive log# 7 seq# 1208881
ARC6: Failed to archive log# 7 seq# 1208881
ARC6: Beginning to archive log# 5 seq# 1208882
ARC6: Failed to archive log# 5 seq# 1208882
ARC6: Beginning to archive log# 9 seq# 1208883
ARC6: Failed to archive log# 9 seq# 1208883
Wed Dec 22 00:02:12 2004
ARC0: Completed archiving log# 2 seq# 1208880
and sometimes we get the message below , in this case the database stands still. (Filesystem is NOT full)
Wed Dec 15 07:34:24 2004
ORACLE Instance pvfpbp - Can not allocate log, archival required
Wed Dec 15 07:34:24 2004
ARCH: Connecting to console port...
Thread 1 cannot allocate new log, sequence 1201212
All online logs needed archiving
Wed Dec 15 07:34:24 2004
ARC9: Beginning to archive log# 8 seq# 1201202
Wed Dec 15 07:34:24 2004
Current log# 5 seq# 1201211 mem# 0: /u019/oracle/log/pvfpbp/redo05a.log
Wed Dec 15 07:34:24 2004
Below output from collect:
# DISK Statistics
#DSK NAME B/T/L R/S RKB/S W/S WKB/S AVS AVW ACTQ WTQ %BSY
7 dsk8 1/10/3 0 1 45 707 5.76 284.62 0.26 12.64 1.33
#DSK NAME B/T/L R/S RKB/S W/S WKB/S AVS AVW ACTQ WTQ %BSY
7 dsk8 1/10/3 0 0 0 1 1.25 0.00 0.00 0.00 0.00
#DSK NAME B/T/L R/S RKB/S W/S WKB/S AVS AVW ACTQ WTQ %BSY
7 dsk8 1/10/3 0 0 0 0 0.00 0.00 0.00 0.00 0.00
#DSK NAME B/T/L R/S RKB/S W/S WKB/S AVS AVW ACTQ WTQ %BSY
7 dsk8 1/10/3 0 1 86 1415 5.49 358.53 0.48 30.46 2.27
#DSK NAME B/T/L R/S RKB/S W/S WKB/S AVS AVW ACTQ WTQ %BSY
7 dsk8 1/10/3 0 0 0 0 0.00 0.00 0.00 0.00 0.00
#DSK NAME B/T/L R/S RKB/S W/S WKB/S AVS AVW ACTQ WTQ %BSY
7 dsk8 1/10/3 0 0 0 0 0.00 0.00 0.00 0.00 0.00
#DSK NAME B/T/L R/S RKB/S W/S WKB/S AVS AVW ACTQ WTQ %BSY
7 dsk8 1/10/3 0 0 27 442 5.47 117.70 0.15 3.05 0.75
#DSK NAME B/T/L R/S RKB/S W/S WKB/S AVS AVW ACTQ WTQ %BSY
7 dsk8 1/10/3 0 9 7 118 3.87 31.69 0.03 0.16 0.35
Did anyone has seen this problem and eventualy knows the cause an maybe the solution ?
Regards A. van Benthem
********************* DISCLAIMER *********************
De informatie in dit e-mail bericht is uitsluitend
bestemd voor de geadresseerde. Verstrekking aan
en gebruik door anderen is niet toegestaan.
Door de electronische verzending van het bericht
kunnen er geen rechten worden ontleend aan de
informatie.
************************************************************
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:13 EDT