If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Locks at OS/390's DB2 REORG

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 10-14-08, 18:23
linakichi linakichi is offline
Registered User
 
Join Date: Aug 2008
Posts: 45
Locks at OS/390's DB2 REORG

Hi all,

I'm doing study in OS/390's DB2 REORG process. Since I don't have the OS/390, I'm doing research by reading manuals only. And it occurs to me that there aren't any information concerning the locks held when :

SHRLEVEL NONE : sort, build,srtbld processes
SHRLEVEL REFERENCE : reload, sort, build, srtbld, and switch processes
SHRLEVEL CHANGE : reload, sort, build, srtbld, switch and log processes

If anyone have any clue about it, I'll appreciate it very much.
Reply With Quote
  #2 (permalink)  
Old 10-15-08, 02:41
Peter.Vanroose Peter.Vanroose is offline
Registered User
 
Join Date: Sep 2004
Location: Belgium
Posts: 1,079
Quote:
Originally Posted by linakichi
SHRLEVEL NONE : sort, build,srtbld processes
SHRLEVEL REFERENCE : reload, sort, build, srtbld, and switch processes
SHRLEVEL CHANGE : reload, sort, build, srtbld, switch and log processes
This is my understanding of it. Please correct me if I'm wrong:

SHRLEVEL NONE: after the unload phase, no access possible, so essentially the tablespace is "exclusively locked".
SHRLEVEL REFERENCE & CHANGE:
with the FASTSWITCH option on, at (almost) all times access is possible, be it to the old version of the data. During the switch phase, no access allowed, i.e., essentially an "exclusive lock".
For SHRLEVEL CHANGE, during the last iteration of the LOG phase, no writes possible, so essentially a "read lock". And no "massive delete" possible during the unload phase.

(Actually, the used locking mechanism is known as "claim and drain"; in some phases only the writers are drained, in some other phases also the readers are drained.)

Separate claims & drains happen for the indexes; general no index access is allowed during any of the phases, exceptions being the partitioned or partitioning indexes.

For details, see pages 471-473 of the v8 Utility Guide; for version 9, this is pages 491-493.
__________________
--_Peter Vanroose,
__IBM Certified Database Administrator, DB2 9 for z/OS
__IBM Certified Application Developer
__ABIS Training and Consulting
__http://www.abis.be/
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On