T o t a l n u m b e r o f l o c k s
a l l o c a t e d f o r t h e d a t a b a s e
D a t a b a s e L o c k S n a p s h o t
ion
D a t a b a s e n a m e = S A M P L E
D a t a b a s e p a t h =
/ h o m e / d b 2 i n s t 1 / d b 2 i n s t 1 / N O D E 0 0 0 0 / S Q L 0 0 0 0 1 /
I n p u t d a t a b a s e a l i a s = S A M P L E
e sect
L o c k s h e l d = 1 1 5 1
A p p l i c a t i o n s c u r r e n t l y c o n n e c t e d = 2
A g e n t s c u r r e n t l y w a i t i n g o n l o c k s = 0
databas
S n a p s h o t t i m e s t a m p = 0 2 1 0 2 0 0 4 1 6 : 3 8 : 5 8 . 7 5 9 8 9 0
A p p l i c a t i o n h a n d l e = 2 1
A p p l i c a t i o n I D = * L O C A L . d b 2 i n s t 1 . 0 C 3 B 3 2 1 8 2 8 0 8
S e q u e n c e n u m b e r = 0 0 0 1
A p p l i c a t i o n n a m e = d b 2 b p
C O N N E C T A u t h o r i z a t i o n I D = D B 2 I N S T 1
A p p l i c a t i o n s t a t u s = U O W W a i t i n g
T o t a l n u m b e r o f
S t a t u s c h a n g e t i m e = N o t C o l l e c t e d
l o c k s h e l d b y
A p p l i c a t i o n c o d e p a g e = 8 1 9
t h e a p p l i c a t i o n
L o c k s h e l d = 1 3
ection
T o t a l w a i t t i m e ( m s ) = N o t C o l l e c t e d
L i s t O f L o c k s
tion s
L o c k N a m e = 0 x 0 0 0 3 0 0 0 5 0 0 1 0 5 2 5 4 0 0 0 0 0 0 0 0 5 2
L o c k A t t r i b u t e s = 0 x 0 0 0 0 0 0 0 0
ption
R e l e a s e F l a g s = 0 x 4 0 0 0 0 0 0 0
applica
L o c k C o u n t = 2 5 5
H o l d C o u n t = 0
descri
L o c k O b j e c t N a m e = 1 0 6 9 6 5 2
O b j e c t T y p e = R o w
T h i s l o c k w a s p l a c e d o n a r o w i n
T a b l e s p a c e N a m e = D A T A S P A C E
locks
t a b l e " T A B L E 0 1 " b y a p p l i c a t i o n
T a b l e S c h e m a = D B 2 I N S T 1
* L O C A L . d b 2 i n s t 1 . 0 C 3 B 3 2 1 8 2 8 0 8
T a b l e N a m e = T A B L E 0 1
M o d e = X
[ . . . t h e l i s t i n g w a s c u t h e r e . . . ]
Figure 9 9 Explaining lock snapshot information
To check lock escalations occurrences look at the
db2diag.log
file. The lock
escalation message should look like Example 9 35.
Example 9 35 Lock escalation message in db2diag.log file
2004 02 10 19.05.05.888741 Instance:db2inst1 Node:000
PID:56408(db2agent (SAMPLE) 0) TID:1 Appid:*LOCAL.db2inst1.0DB5F2004313
data management sqldEscalateLocks Probe:3 Database:SAMPLE
ADM5502W The escalation of "1136" locks on table "DB2INST1.TABLE01" to lock
intent "X" was successful.
Logical log buffer
The default size for logical log buffer is eight pages (32 KB), which is often too
small for an OLTP database, and not big enough for long running batch
processes. In most cases the log records are written to disk when one of the
transactions issue a
COMMIT
, or the log buffer is full. Increasing the size of the log
buffer may result in more efficient I/O operations, especially when the buffer is
306
MySQL to DB2 UDB Conversion Guide
footer
Our partners:
PHP: Hypertext Preprocessor Cheap Web Hosting
JSP Web Hosting
Ontario Web Hosting
Jsp Web Hosting
Cheapest Web Hosting
Java Hosting
Cheapest Hosting
Visionwebhosting.net Business web hosting division of Vision Web Hosting Inc.. All rights reserved