2 simultaneous reorgs work with DMS temp...see below and last email.
Further comments,
perhaps your OS is getting in the way (NT is allowing).  Perhaps, you do not
have enough tempspace allocated (you get obscure messages when tempspace
fills deeply nested in your logs.  

In UNIX: If you see OS locks, try creating the DMS tempspace on a raw
partition.
  You'll get even faster performance.  

On any platform, you can put tempspace on a SAN.  
While the SAN software is limiting access of specific SAN luns to certain
servers, perhaps this software has an impact on the multiple table reorgs? 
-----Original Message-----
From: Fortier, Christi (PCA) 
Sent: Monday, March 26, 2001 2:57 PM
To: '[EMAIL PROTECTED]'
Subject: RE: DB2EUG: Mirroring your Tempspace


I just verified on DB2 7.1 fp2 NT EEE.  I was able to reorg 2 multi-gigabyte
tables with no problems.  There were only the following locks (none on
tempspace tablespace) and not errors in the diag log.

NS locks on syscatspace 
Z lock on both reorg tables
IX lock on reorg tablespaces

-----Original Message-----
From: Goldberg, Howard (SOM400A) [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 23, 2001 1:23 PM
To: [EMAIL PROTECTED]
Subject: RE: DB2EUG: Mirroring your Tempspace


I think, If you use DMS then you can not reorg two tables at the same time.

-----Original Message-----
From: Fortier, Christi (PCA) [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 23, 2001 8:38 AM
To: [EMAIL PROTECTED]
Subject: RE: DB2EUG: Mirroring your Tempspace


For heavy uses of tempspace, and optimal  performance we create tempspace on
a SAN Fibre disk array with 1 huge DMS tempspace (per node), then drop the
1st one that IBM creates for you (on your install drive).  
 
Using a DMS serves the following purposes:

*       You save yourself the dynamic allocations at run time (can be
physical, physical disk IO is an expensive performance hit) 

*       You are reserving space on a drive that might otherwise be thought
of as available

Fibre controllers over a SAN offer 100 MB/sec throughput as opposed to
10MB/sec SCSI.  SANs work best when you have more concurrent traffic; so
using a SAN especially appeals to DB2 EEE.

-----Original Message-----
From: Chris Bonin [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 21, 2001 11:34 AM
To: [EMAIL PROTECTED]
Subject: DB2EUG: Mirroring your Tempspace


We need to increase our tempspace to accomadate creating indexes. We would
like to create a large tempspace and not mirror it. Are there any
implications? Also, if you have two tempspaces does DB2 use both of them via
striping? 

Thanks in advance.. 
Chris Bonin 
Database Administrator 
North Carolina Dept. of Revenue ===== To unsubscribe, send 'unsubscribe' to
[EMAIL PROTECTED] For other info (and scripts), see
http://people.mn.mediaone.net/scottrmcleod 



=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod



=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod

Reply via email to