| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| PubSubControlMsgFlow |
« View previous topic :: View next topic » |
| Author |
Message
|
| paustin_ours |
 Posted: Thu Jul 20, 2006 8:05 am Post subject: PubSubControlMsgFlow |
 |
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
whenever the broker started up, we see this error
BIP2628E XXXXBRK XXXXEX01 25 EXCEPTION CONDITION DETECTED ON INPUT NOD
E 'PubSubControlMsgFlow.InputNode'. : ImbMqInputNode(2083)
BIP2230E XXXXBRK XXXXEX01 25 ERROR DETECTED WHILST PROCESSING A MESSAG
E IN NODE 'PubSubControlMsgFlow.ControlNode'. : ImbPubSubControlNode(5
93)
BIP2230E XXXXBRK XXXXEX01 25 ERROR DETECTED WHILST PROCESSING A MESSAG
E IN NODE 'PubSubControlMsgFlow.ControlNode'. : ImbPubSubControlNode(4
97)
BIP2371E XXXXBRK XXXXEX01 25 DATABASE STATEMENT 'UPDATE XXXXBRK.BROKER
RESOURCES SET ResourceData = ? WHERE BrokerUUID = ? AND ExecGroupUUID
= ? AND ResourceType = ? AND ResourceName = ?' COULD NOT BE EXECUTED.
: ImbOdbc(1455)
+BIP2321E XXXXBRK XXXXEX01 25 DATABASE ERROR: ODBC RETURN CODE '-1'. : ImbOdb
+BIP2322E XXXXBRK XXXXEX01 25 DATABASE ERROR: SQL STATE '23505'; NATIVE
ERROR CODE '-803'; ERROR TEXT '{DB2 FOR OS/390}{ODBC DRIVER}{DSN08015
} DSNT408I SQLCODE = -803, ERROR: AN INSERTED OR UPDATED VALUE IS I
NVALID BECAUSE INDEX IN INDEX SPACE BROK1LE7 CONSTRAI
NS COLUMNS OF THE TABLE SO NO TWO ROWS CAN CONTAIN DUPLICAT
E VALUES IN THOSE COLUMNS. RID OF EXISTING ROW IS X'000000
8501 DSNT418I SQLSTATE = 23505 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNXRUID SQL PROCEDURE DETECTIN
G ERROR DSNT416I SQLERRD = -150 13172739 0 1
3814229 -489488384 0 SQL DIAGNOSTIC INFORMATION
+BIP2648E XXXXBRK XXXXEX01 25 MESSAGE BACKED OUT TO A QUEUE; NODE 'PubSubCont
it also leaves an uncommitted UR on the db2 subsystem.
any thoughts on this? |
|
| Back to top |
|
 |
| paustin_ours |
| Posted: Fri Jul 21, 2006 9:14 am Post subject: |
|
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
i see that the message is backed out but not sure why the db2 call is not geting backed out.
any suggestions?thoughts?ideas...more than welcome |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jul 21, 2006 10:06 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Looks to me the DB2 call is being backed out.
The problem seems to be you are trying to insert values into DB2 which would result in having a dupplicate entry in an index that has been declared as Unique.... Thus the rollback and the illusion that the DB2 entry was not. The fact is it was there before...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| iceage |
| Posted: Fri Jul 21, 2006 1:35 pm Post subject: |
|
|
Acolyte
Joined: 12 Apr 2006
Posts: 68
|
| open up a PMR , flow that you are refering is "internal" to the product , if it leaves uncommite unit of recovery , most likely you might have found an issue or it might be your configuration. |
|
| 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
|
|
|
|
