HP3000-L Archives

November 2007, 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:
Cathlene Mc Rae <[log in to unmask]>
Reply To:
Cathlene Mc Rae <[log in to unmask]>
Date:
Tue, 6 Nov 2007 10:36:22 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
Stalled transaction could be caused by tpi.  If you disable tpi from xm, the 
stalled transactions may go away.

Removing tpi from the database before the repack will also do the the job.

repack, then re-index.  In some cases this is not possible which is why disable 
tpi from xm is the way to go.

 
TPI by Omnidex does the DBPUT as follows: 

The DBPUT uses empty records from delete chain, than a reshuffle of the index 
records is done in order to keep the RRNs in sorted order.  This can apparently 
take up lots of XM buffer space. 


Omnidex suggests that customers do a REPACK of detail set and 
REINDEX.  If the delete rate is high a REPACK of the detail set 
and REINDEX should be done often.  Workaround: Disable TPI XM: 

Turn off XM for TPI (Omnidex) 

RUN DBINSTAL.PUB.DISC   
Data base name: mydb 
Cmd: SET TPI NOXM 


 Cathlene Mc Rae
 HP SR. Response Center Engineer
 [log in to unmask]

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2