| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Deadloack occured while accessing the NOTIFICATION_ITEM tabl |
« View previous topic :: View next topic » |
| Author |
Message
|
| christadimai |
 Posted: Wed Sep 27, 2006 10:00 pm Post subject: Deadloack occured while accessing the NOTIFICATION_ITEM tabl |
 |
|
Newbie
Joined: 27 Sep 2006
Posts: 6
Location: Malaysia
|
Hi,
I am getting deadlocks in DB2, This is the dealock details:
Deadlocked Connection ...
Appl Id: *LOCAL.db2inst1.060926155412
Appl Seq number: 0001
Appl Id of connection holding the lock:
*LOCAL.db2inst1.060926155407
Seq. no. of connection holding the lock: 0001
Lock wait start time: 09-27-2006 14:11:37.989860
Requesting lock as part of escalation: FALSE
Deadlock detection time: 09-27-2006 14:12:00.138022
Table of lock waited on : NOTIFICATION_ITEM
Schema of lock waited on : FMC
Tablespace of lock waited on : NTFYITEM
Type of lock: Row
Mode of lock: X
Mode application requested on lock: U
Node lock occured on: 0
Lock object name: 218143
Application Handle: 10
I have interpreted this as deadlock occured wile accessing the NOTIFICATION_ITEM table.
This is the configuration details for the scheduling server.
> > - Scheduling server settings
> > - Check interval PT6H
> >- Start mode Deferred
> >- Server start time Everyday at 06:00
> >- Server stop time 00:00
> >- Notification check interval PT1H
> >- Suspension check interval PT1H
> >- Create notification items threshold 10
> >- Delete notification items threshold 100
Although, I have 9000 records in NOTIFICATION_ITEM table , in this around 8000 records (activites) to be notified for future time period and 1000 records with notification period (to_be _notified) less than current time.
My question is,
What value should I specify for the notification check interval to avoid this deadlocks? .
[P.S. I believe deadlock occured in this particular table is becoz of the notification check interval ].
Thankx in advance,
Christ. |
|
| Back to top |
|
 |
| mzg |
| Posted: Thu Sep 28, 2006 5:33 am Post subject: |
|
|
Newbie
Joined: 01 Oct 2003
Posts: 8
|
Hi,
you may want to run some database optimizations (runstats/rebind), which can be invoked through "fmczutil".
If that doesn't help to remove the deadlocks you might want to try to increase the DB2 parameters MAXLOCKS and LOCKLIST.
Good Luck!
_________________
Cheers,
Richard.
-----------------------
IBM Websphere MQ Workflow & Process Choreographer Performance Focal Point |
|
| Back to top |
|
|
| christadimai |
| Posted: Thu Sep 28, 2006 6:24 pm Post subject: |
|
|
Newbie
Joined: 27 Sep 2006
Posts: 6
Location: Malaysia
|
Hi,
Thank you for reply. Two days back we have done index reorg in database. These are the database configuration entries for MAXLOCKS and LOCKLIST:
Percent. of lock lists per application (MAXLOCKS) = 20
Max storage for lock list (4KB) (LOCKLIST) = 2500
We have lot of records in the NOTIFICATION_ITEM table and we were configured schedule server notification time interval to 1H. Every one hour schedule server will take exclusive lock of this table and not allow any other processes to access to this table.
To avoid this I want to increase to the notification check interval to 1:30 hrs. Now, Can you tell what will be the impact if I assign this value ?
Thanks,
Christ. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
