| Author |
Message
|
| mqwbiwf |
 Posted: Fri Aug 18, 2006 7:03 am Post subject: errors during broker startup |
 |
|
Centurion
Joined: 21 Jul 2006
Posts: 126
|
Hi,
We use WMQI 2.1 CSD 9 on AIX 5.3. We were trying to send a file (some 30MB) though one of our flows. Since it was throwing out of memory errors, we increased the number of memory segments being used from the default 2 to 4. It was still throing some error messages. till this point, when i restarted the broker, no error messages had appeared. but we tried to increase the memory segments to 7 from 4. and when restarted the broker it was throwing some database errors:
BIP7075E: Unable to find client id '344489000' for subscription registered to topic '$ISYS/Broker/Broker Name/MQPubSub/Update'.
BIP2121E: The thread bootstrap code caught an unhandled exception on thread '4113'.
BIP2322E: Database error: SQL State '08001'; Native Error Code '-1224'; Error Text '[IBM][CLI Driver] SQL1224N
But when I unset the LDR_CNTRL variable or keep it less than or equal to 4, i do not get the BIP2121E & BIP2322E errors but get a series of BIP7075E errors.
Could someone throw some light on this issue please? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Aug 18, 2006 7:09 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Search the broker info center for the 1224 error.
Hint - you need to use TCP/IP to connect to DB2.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqwbiwf |
| Posted: Fri Aug 18, 2006 7:23 am Post subject: |
|
|
Centurion
Joined: 21 Jul 2006
Posts: 126
|
The main concern is why are we getting the other 2 errors only when increased the memory segments being used from 4 to any number higher. Can't we increase the memory segments more than 4?
We have DB2 on the same machine, not on the remote machine.
I could not find much info on the series of BIP7075E error messages. It would be greatly appreciated if some one can provide me a fix for this error message. Broker seems to be running fine, but it's just these error messages in the log. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Aug 18, 2006 7:56 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I did not say "search on the BIP error".
I said "search on the 1224 error". This is the "SQL1224N" error!
And, it does not matter than you are using DB2 locally. In fact, that's part of the problem.
There is a direct fix for this issue, that is directly spelled out in the Information Center, that is easily findable by the error code I have indicated.
The high level understanding of the fix for this error is that you must use TCP/IP to connect to DB2.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqwbiwf |
| Posted: Fri Aug 18, 2006 8:11 am Post subject: |
|
|
Centurion
Joined: 21 Jul 2006
Posts: 126
|
But jefflowrey, We are getting this SQL 1224N error only when LDR_CNTRL variable is set to a value greater than 4. Else, we are not getting this error. When searched about this 1224 error, it says to delete the broker, which I do not want to do because currently it is being used by some other countries too!
Isn't there any other alternative? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Aug 18, 2006 8:28 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You will be recreating the exact same broker. You only have to delete it so you can drop and recreate the database from backup.
I'm not entirely sure that it's actually necessary to drop and recreate the database, you might just be able to update the instance. On the other htand, that might require you to drop and recreate teh database?
If you want a different fix than what's in the manual, I suggest you open a PMR with IBM.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
