| Author |
Message
|
| mrlazy |
 Posted: Tue Jun 20, 2006 10:52 am Post subject: Database error when started the broker |
 |
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
Hi, We have Broker 2.1 (AIX5.3) in our environment. I deleted the broker today once and recreated it. When I start the broker, though it shows that the broker is started, it's showing the following error msg in broker logs:
BIP2111E , BIP2321E, and BIP2322E
Could someone please let me know why is this happening?
These are the steps done while deleting/recreating broker:
Stopped the broker.
Deleted including flags q,w.
Recreated with same name and same database.
When I deploy the topology(no msg flows, no msg sets), no error is being displayed in Control Center logs. |
|
| Back to top |
|
 |
| mrlazy |
| Posted: Tue Jun 20, 2006 11:56 am Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
Hi,
I tried to create an execution group and add a mesage flow(from production) to this box, but it shows the following errors:
BIP4041E, BIP2086, BIP2241E & BIP 1536S
Someone please respond with your valuable suggestions. |
|
| Back to top |
|
|
| mrlazy |
| Posted: Tue Jun 20, 2006 1:04 pm Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
Now though I do not see any errors in Control center when deployed an execution group, I see the follwoing messages in broker log:(is it something seriously wrong??)
Jun 20 15:30:32 hostname user:info WMQIv210[880712]: (NEW_BROKER.ExecGrp)
[1]BIP2201I: Execution Group started: process '880712'; thread '1'; additi
onal information: brokerName 'NEW_BROKER'; executionGroupUUID '3ee411f3-0b0
1-0000-0080-8b571131c7c8'; executionGroupLabel 'ExecGrp'; defaultExecuti
onGroup 'false'; queueManagerName 'NEW_BROKER'; trusted 'false'; dataSource
Name 'MQSIBKDB'; userId 'mqm'; migrationNeeded 'false'; brokerUUID '846799f
2-0b01-0000-0080-8b571131c7c8'; filePath '/usr/opt/wmqi'; workPath '/var/wmqi'.
: NEW_BROKER.3ee411f3-0b01-0000-0080-8b571131c7c8: /build/S210_BP/src/DataF
lowEngine/ImbMain.cpp: 215: main: :
Jun 20 15:30:32 hostname user:err|error WMQIv210[880712]: (NEW_BROKER.ExecGrp)
[1]BIP2111E: Message broker internal error: diagnostic information 'D
ynamicSubscriptionEngine'. : NEW_BROKER.3ee411f3-0b01-0000-0080-8b571131c7c
8: /build/S210_BP/src/DataFlowEngine/ImbPubSubDatabase.cpp: 184: ImbPubSubDataba
se::ImbPubSubDatabase: DynamicSubscriptionEngine: DynamicSubscriptionEngine
Jun 20 15:30:32 hostname user:err|error WMQIv210[880712]: (NEW_BROKER.ExecGrp)
[1]BIP2321E: Database error: ODBC return code '-1'. : NEW_BROKER
.3ee411f3-0b01-0000-0080-8b571131c7c8: /build/S210_BP/src/DataFlowEngine/ImbOdbc
.cpp: 160: ImbOdbcHandle::checkRcInner: :
Jun 20 15:30:32 hostname user:err|error WMQIv210[880712]: (NEW_BROKER.ExecGrp)
[1]BIP2322E: Database error: SQL State '42724'; Native Error Code '-4
44'; Error Text '[IBM][CLI Driver][DB2/6000] SQL0444N Routine "SQLTABLES" (spec
ific name "TABLES") is implemented with code in library or path ".../sqllib/func
tion/unfenced/db2schema", function "sqltables" which cannot be accessed. Reason
code: "5". SQLSTATE=42724 '. : NEW_BROKER.3ee411f3-0b01-0000-0080-8b57113
1c7c8: /build/S210_BP/src/DataFlowEngine/ImbOdbc.cpp: 286: ImbOdbcHandle::checkR
cInner: :
Jun 20 15:30:34 hostname user:info WMQIv210[880712]: (NEW_BROKER.ExecGrp)
[2828]BIP7032I: Publish/Subscribe state recovery started due to incorrect
sequence number. : NEW_BROKER.3ee411f3-0b01-0000-0080-8b571131c7c8: /build/
S210_BP/src/DataFlowEngine/ImbPubSubControlNode.cpp: 1256: ImbPubSubControlNode:
:sequenceNumberRecovery: ComIbmPSControlNode: ControlNode
Jun 20 15:30:34 hostname user:info WMQIv210[880712]: (NEW_BROKER.ExecGrp)
[2828]BIP7033I: Publish/Subscribe state recovery completed. : NEW_BROKE
R_1.3ee411f3-0b01-0000-0080-8b571131c7c8: /build/S210_BP/src/DataFlowEngine/ImbP
ubSubControlNode.cpp: 1296: ImbPubSubControlNode::sequenceNumberRecovery: ComIbm
PSControlNode: ControlNode |
|
| Back to top |
|
|
| mrlazy |
| Posted: Tue Jun 20, 2006 4:31 pm Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
| Guys, Still waiting....please respond with your input. |
|
| Back to top |
|
|
| wschutz |
| Posted: Tue Jun 20, 2006 5:28 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
From the DB/2 Messages & Codes manual for SQL0444N:
| Quote: |
| 5 There was insufficient memory to load the library containing the function or one or more symbols could not be resolved. Contact the routine creator or your database administrator to make sure that the library was correctly linked. All required libraries to resolve referenced symbols such as external functions must be available. If a lack of memory is determined then the system configuration may need to be changed to make more memory available to DB2. |
_________________
-wayne |
|
| Back to top |
|
|
| mrlazy |
| Posted: Tue Jun 20, 2006 7:12 pm Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
Thanks a lot for your reply wschutz.
But can you please be a little more brief on this point. Because I myself have configured the DB2, and did not face this problem earlier on this machine. I mean I did not see this error in broker log before I recreated the broker again.
One thing I noticed is that a couple of these errors(BIP2321E & BIP2322E) occur even in our production environment. I'm just not sure how bad this error affects the broker in my case, coz I see every thing got deployed well in the control center logs.
It would be really helpful if someone brief's me a little bit more on this issue. |
|
| Back to top |
|
|
|
|
