HP3000-L Archives

April 1996, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Gilles Schipper <[log in to unmask]>
Reply To:
Gilles Schipper <[log in to unmask]>
Date:
Mon, 1 Apr 1996 20:57:19 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (22 lines)
This sounds suspiciously like a clustering problem.
 
You do mention that a write is taking place, and glance is showing 50 I/O's
per second.
 
Try to determine which dataset is being written to at the time, and run
HOWMESSY or DBLOADNG against the database in question and look for a large
max.block number associated with a master data set.
 
If this is indeed the problem, use Adager or some other tool to increase the
capacity of the data set in question. From my experience, increasing the
capacity SIGNIFICANTLY offers the best chance of fixing the problem. Some
experimentation may be in order.
 
Hope this helps.
-----------------------------------------------------------------------------
   Gilles Schipper                    Voice:      905/889-3000
   GSA Inc.                           Fax:        905/889-3001
   300 John Street, Box 87651         Internet:   [log in to unmask]
   Thornhill, ON  Canada  L3T 7R4     Compuserve: 71203,474
-----------------------------------------------------------------------------

ATOM RSS1 RSS2