Connecting Tech Pros Worldwide Help | Site Map

Online backup locking out processes...........

  #1  
Old November 17th, 2008, 05:15 PM
heyzulu59@gmail.com
Guest
 
Posts: n/a
I thought that an online backup could always be run while other
processes with the database went about their business. However today I
noticed that certain processes in my production database were in a
lock-wait state because of the online backup. Why is this happening? I
had to kill the online backup to free up about six other processes
that were blocked.

Application handle = 508
Application ID = *LOCAL.hrprod.
081117142526
Sequence number = 0024
Application name = psae
CONNECT Authorization ID = DB2DBO
Application status = Lock-wait
Status change time = Not Collected
Application code page = 1208
Locks held = 14
Total wait time (ms) = 1779179

ID of agent holding lock = 223
Application ID holding lock = *LOCAL.hrprod.
081117121523
Lock name =
0x0079000000000000000000006F
Lock attributes = 0x00000000
Release flags = 0x40000000
Lock object type = Internal Online Backup
Lock
Lock mode = Exclusive Lock (X)
Lock mode requested = Share Lock (S)
Name of tablespace holding lock = TLAPP
Lock wait start timestamp = Not Collected

List Of Locks
Lock Name = 0x00000113000000010001BE0056
Lock Attributes = 0x00000000
Release Flags = 0x40000000
Lock Count = 1
Hold Count = 0
Lock Object Name = 0
Object Type = Internal Variation Lock
Mode = S

Lock Name = 0x53514C55464530374A18812441
Lock Attributes = 0x00000000
Release Flags = 0x40000000
Lock Count = 1
Hold Count = 0
Lock Object Name = 0
Object Type = Internal Plan Lock
Mode = S

Lock Name = 0x53514C55434530346DE2A8B441
Lock Attributes = 0x00000000
Release Flags = 0x40000000
Lock Count = 1
Hold Count = 0
Lock Object Name = 0
Object Type = Internal Plan Lock
Mode = S

Lock Name = 0x000000630015D7065CE9F80043
Lock Attributes = 0x00000000
Release Flags = 0x40000000
Lock Count = 3
Hold Count = 0
Lock Object Name = 0
Object Type = Internal Catalog Cache Lock
Mode = S

Lock Name = 0x53514C55424530339226891241
Lock Attributes = 0x00000000
Release Flags = 0x40000000
Lock Count = 1
Hold Count = 0
Lock Object Name = 0
Object Type = Internal Plan Lock
Mode = S

Lock Name = 0x000000630015D7060000000052
Lock Attributes = 0x00000000
Release Flags = 0x40000054
Lock Count = 10
Hold Count = 0
Lock Object Name = 1431302
Object Type = Row
Tablespace Name = SYSCATSPACE
Table Schema = SYSIBM
Table Name = SYSTABLES
Mode = NS

Lock Name = 0x0000010F000000010001A00056
Lock Attributes = 0x00000000
Release Flags = 0x40000000
Lock Count = 1
Hold Count = 0
Lock Object Name = 0
Object Type = Internal Variation Lock
Mode = S

Lock Name = 0x53514C554B453037C632454441
Lock Attributes = 0x00000000
Release Flags = 0x40000000
Lock Count = 1
Hold Count = 0
Lock Object Name = 0
Object Type = Internal Plan Lock
Mode = S

Lock Name = 0x53514C554F4530303504B43841
Lock Attributes = 0x00000000
Release Flags = 0x40000000
Lock Count = 1
Hold Count = 0
Lock Object Name = 0
Object Type = Internal Plan Lock
Mode = S

Lock Name = 0x53514C4445464C540763DD2841
Lock Attributes = 0x00000000
Release Flags = 0x40000000
Lock Count = 1
Hold Count = 0
Lock Object Name = 0
Object Type = Internal Plan Lock
Mode = S

Lock Name = 0x00000002000000000000000054
Lock Attributes = 0x00000000
Release Flags = 0x00000020
Lock Count = 1
Hold Count = 0
Lock Object Name = 2
Object Type = Table
Tablespace Name = SYSCATSPACE
Table Schema = SYSIBM
Table Name = SYSCOLUMNS
Mode = IS

Lock Name = 0x00790313000000000000000054
Lock Attributes = 0x00000000
Release Flags = 0x40000000
Lock Count = 255
Hold Count = 0
Lock Object Name = 787
Object Type = Table
Tablespace Name = TLAPP
Table Schema = DB2DBO
Table Name = PS_TL_COMP_BAL17
Mode = Z

Lock Name = 0x0000000E000000000000000054
Lock Attributes = 0x00000000
Release Flags = 0x00000010
Lock Count = 1
Hold Count = 0
Lock Object Name = 14
Object Type = Table
Tablespace Name = SYSCATSPACE
Table Schema = SYSIBM
Table Name = SYSRELS
Mode = IS

Lock Name = 0x00000063000000000000000054
Lock Attributes = 0x00000000
Release Flags = 0x40000054
Lock Count = 13
Hold Count = 0
Lock Object Name = 99
Object Type = Table
Tablespace Name = SYSCATSPACE
Table Schema = SYSIBM
Table Name = SYSTABLES
Mode = IS
  #2  
Old November 17th, 2008, 08:25 PM
Troels Arvin
Guest
 
Posts: n/a

re: Online backup locking out processes...........


heyzulu59 wrote:
Quote:
I thought that an online backup could always be run while other
processes with the database went about their business. However today I
noticed that certain processes in my production database were in a
lock-wait state because of the online backup. Why is this happening?
Do you have tables with LOB (BLOB/CLOB) columns stored in SMS tablespace
(s)? - If so, search for the description of "ONLINE" at http://
publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/
com.ibm.db2.luw.admin.cmd.doc/doc/r0001933.html

--
Troels

  #3  
Old November 18th, 2008, 08:35 PM
Jef
Guest
 
Posts: n/a

re: Online backup locking out processes...........


On Nov 17, 11:07*am, heyzul...@gmail.com wrote:
Quote:
I thought that an online backup could always be run while other
processes with the database went about their business. However today I
noticed that certain processes in my production database were in a
lock-wait state because of the online backup. Why is this happening?
Other utilities such as RUNSTATS can also prevent online backup from
acquiring a lock.
Closed Thread