ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » BIP1205E While Deploying - WMQI 2.1

Post new topic  Reply to topic
 BIP1205E While Deploying - WMQI 2.1 « View previous topic :: View next topic » 
Author Message
CoolDude
PostPosted: Sat Dec 10, 2005 1:44 pm    Post subject: BIP1205E While Deploying - WMQI 2.1 Reply with quote

Apprentice

Joined: 17 Jan 2004
Posts: 39
All:

I am recieving the two below errors in Event log when I'm trying to perform a Broker Level Delta Deploy.


Quote:
2005-12-10-16.19.51.568000 Instance:DB2 Node:000
PID:3648(db2syscs.exe) TID:328 Appid:*LOCAL.DB2.051210211423
data management sqldEscalateLocks Probe:4 Database:CONFIGDB

ADM5503E The escalation of "333" locks on table "MQSI.CMSGFLOW" to lock
intent "X" has failed. The SQLCODE is "-911".


Quote:
( ConfigMgr ) Unexpected exception accessing configuration repository; exception text: '[IBM][CLI Driver][DB2/NT] SQL0911N The current transaction has been rolled back because of a deadlock or timeout. Reason code "2". SQLSTATE=40001 '.

While attempting a database operation on the configuration repository, a SQL exception was caught by the Configuration Manager. The database operation did not complete successfully. If this message was issued by the Configuration Manager, then it will continue if it is safe to do so. The exception text is: [IBM][CLI Driver][DB2/NT] SQL0911N The current transaction has been rolled back because of a deadlock or timeout. Reason code "2". SQLSTATE=40001 .


I then looked at the db2diaglog.txt and I found this

Quote:
PID : 3648 TID : 328 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : CONFIGDB
APPHDL : 0-351 APPID: *LOCAL.DB2.051210211423
FUNCTION: DB2 UDB, data management, sqldEscalateLocks, probe:3
MESSAGE : ADM5502W The escalation of "350" locks on table "MQSI
.CPROPERTIES" to lock intent "X" was successful.

2005-12-10-16.19.51.568000-300 E175236H476 LEVEL: Error
PID : 3648 TID : 328 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : CONFIGDB
APPHDL : 0-351 APPID: *LOCAL.DB2.051210211423
FUNCTION: DB2 UDB, data management, sqldEscalateLocks, probe:4
MESSAGE : ADM5503E The escalation of "333" locks on table "MQSI.CMSGFLOW"
to lock intent "X" has failed. The SQLCODE is "-911".


How do we determine how much locklist/heapsize is required to deploy a certain(100) amount of message flows to the broker across 10(Execution Groups)

I found this but couldnot figure out any.

http://www-1.ibm.com/support/docview.wss?rs=0&q1=sqldEscalateLocks&uid=swg21053602&loc=en_US&cs=utf-8&cc=us&lang=en
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » BIP1205E While Deploying - WMQI 2.1
Jump to:  



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
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.