| Author |
Message
|
| Erik |
 Posted: Thu Oct 10, 2002 12:59 pm Post subject: MQSI2.1 DB2 7.2 Put problem |
 |
|
Apprentice
Joined: 25 Aug 2002
Posts: 47
Location: Caracas Venezuela
|
Hi all,
I have a problem with MQSI 2.1 running on AIX 4.3.3 and db2 7.2
When we put messages on the mqsi and a db2 table there is a block.
It is like there is a LOCK TABLE IN EXCLUSIVE MODE. This is a random occurenceand we can not se any patterns in messages accepted and messages blocked.
We are really stumbed on this one and if anyone has the sligthest hint of a solution, it will be greatly appreciated
Please Advice
Erik
_________________
Erik |
|
| Back to top |
|
 |
| lillo |
| Posted: Thu Oct 10, 2002 10:06 pm Post subject: |
|
|
Master
Joined: 11 Sep 2001
Posts: 224
|
Are you using CSD2 or CSD3? DB2 7.2 is supported on CSD3.
Cheers,
_________________
Lillo
IBM Certified Specialist - WebSphere MQ |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Oct 10, 2002 11:46 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
| Are you using aggregate nodes? |
|
| Back to top |
|
|
| Erik |
| Posted: Fri Oct 11, 2002 5:20 am Post subject: |
|
|
Apprentice
Joined: 25 Aug 2002
Posts: 47
Location: Caracas Venezuela
|
Hi all,
We are using CSD 3, and no we are not using aggregate nodes.
Erik
_________________
Erik |
|
| Back to top |
|
|
| Nick Lethbridge |
| Posted: Fri Oct 11, 2002 6:26 am Post subject: |
|
|
Voyager
Joined: 13 Aug 2001
Posts: 88
Location: Santander, UK
|
Are you using a globally coordinated flow that invokes the NEON parser ?
(There are some known DB2 transaction lock problems with XA / NEON - but the release notes with CSD03 describe a solution).
Regards,
Nick. |
|
| Back to top |
|
|
| Erik |
| Posted: Fri Oct 11, 2002 6:41 am Post subject: |
|
|
Apprentice
Joined: 25 Aug 2002
Posts: 47
Location: Caracas Venezuela
|
HI all,
We are not using NEON PARSERS...
We are still confused about this and still havent found any pattern for this
seemly random occurence.
Please advice
Erik
_________________
Erik |
|
| Back to top |
|
|
| Nick Lethbridge |
| Posted: Fri Oct 11, 2002 9:41 am Post subject: |
|
|
Voyager
Joined: 13 Aug 2001
Posts: 88
Location: Santander, UK
|
|
| Back to top |
|
|
| Erik |
| Posted: Fri Oct 11, 2002 10:25 am Post subject: |
|
|
Apprentice
Joined: 25 Aug 2002
Posts: 47
Location: Caracas Venezuela
|
Hi all,
Yes we have applied the merant ODBC driver fix...
Problem still here..
Please advice
Erik
_________________
Erik |
|
| Back to top |
|
|
| kirani |
| Posted: Fri Oct 11, 2002 6:54 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Erik,
Are you referring to Broker database or application database? Could you pl explain your problem in more detail?
What DB2 fixpack are you using?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| philip.baker |
| Posted: Wed Oct 16, 2002 2:10 pm Post subject: |
|
|
Voyager
Joined: 21 Mar 2002
Posts: 77
Location: Baker Systems Consulting, Inc. - Tampa
|
You can try setting the isolation level within DB2 with regards to how locks are acquired and released.
To resolve certain DB locking issues, run 'db2set DB2_RR_TO_RS=YES' from the db2 command line.
_________________
Regards,
Phil |
|
| Back to top |
|
|
|
|
