1)
A- An offline (Allow READ/NO access) will lock up the table for no
change transactions. Read only os the most you can get
B- An online (INPLACE allow READ/WRITE access) will allow insert,
update, delete, select transactions but is much slower and requires more log
space.
2) Tbalespace level is not supported in DB2 UDB V9. For LUW.

3) F4 pertains to the degree of clustering of an index. If the
recommendation shows as F4>80, ot means that you should maintain tge degree
of clustering for an index above 80%. Note that, typically, you can do this
for on or two indexes at most. If one of your indexes is defined with the
cluster clause then that's the one where the degree of clustering (also F4)
should show in the 90%.

Regards, Pierre.
Pierre Saint-Jacques
SES Consultants Inc.
-----Message d'origine-----
De : ado [mailto:db2udbdba-ezmlmshield-x91196717.[Email address protected]
Envoyé : 17 janvier 2008 09:53
À : LazyDBA Discussion
Objet : REORG locks up table?

Hi,

1. Will "reorg on table" lock up active and new transactions?

2. Does reorg also work on tablespace level?

3. REORGCHK reports F1, F2,..., F8. Say, F4 > 80. Does it mean F4 should be
above 80? Or does it mean F4 should be below 80?

Thanks!
Ado


---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html


DB2 & UDB email list listserv db2-l LazyDBA home page