| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Issue while Message broker accessing DB2 |
« View previous topic :: View next topic » |
| Author |
Message
|
| sarathmattam |
 Posted: Mon Jul 05, 2010 10:57 pm Post subject: Issue while Message broker accessing DB2 |
 |
|
Voyager
Joined: 05 Sep 2008
Posts: 94
|
Dear All,
I am working in Solaris Environment with MB 6.1.0.2, MQ 6.0 and DB2 9.5. I am facing a weird issue in my production environment. I would like to get your help in resolving this issue.
I have a message flow deployed in PRD2.FOP.BRK under the execution group PRD2.FOP.ERP.EXE. The message flow has a logic for connecting to a DB to populate some values in the output. But whenever it reaches that particular line, it throws an exception saying
Description: Exception, Error detected, rethrowing, com.XXX.esb.Validation.Main, 30.3, , Root SQL exception, -1, Child SQL exception, 38553, -443, [IBM][CLI Driver][DB2/SUN64] SQL0443N Routine "SYSIBM.SQLCOLUMNS" (specific name "COLUMNS") has returned an error SQLSTATE with diagnostic text "SYSIBM:CLI:-805". SQLSTATE=38553
I have searched in Google for the SQL error thrown. All sites and forums talks about binding the db2 schema against the database . But the below questions refrains me from doing the bind.
1. There are few other message flows deployed in the same EG accessing some other tables under the same DB. It works fine.
2. The same code deployed in Production is available in another environment. That works fine.
I have tried redeploying the same under a different EG. I tried the option of dropping the table and creating it again.. Nothing works ..
Kindly guide me how to proceed .. if am going for a bind option, do I need to restart the DB ?? |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Jul 06, 2010 1:41 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I'm not sure that DB2 9.5 is supported at MB 6.1.0.2. It's definitely supported at 6.1.0.7, but given that I don't think 9.5 was released when 6.1.0.2 shipped...
It would be helpful to know the exception number/bip number for the error you're getting as well. |
|
| Back to top |
|
|
| sarathmattam |
| Posted: Sat Jul 10, 2010 3:40 am Post subject: |
|
|
Voyager
Joined: 05 Sep 2008
Posts: 94
|
Dear All,
This is what am getting in /var/adm/messages
Jul 10 14:28:49 osiprd02 WebSphere Broker v6102[3147]: [ID 702911 user.error] (PRD2.NMS.BRK.PRD2.NMS.SDD.EXE)[1]BIP2322E: Database error: SQL State '38553'; Native Error Code '-443'; Error Text '[IBM][CLI Driver][DB2/SUN64] SQL0443N Routine "SYSIBM.SQLTABLES" (specific name "TABLES") has returned an error SQLSTATE with diagnostic text "SYSIBM:CLI:-805". SQLSTATE=38553 '. : PRD2.NMS.BRK.ef9ee63d-2701-0000-0080-cad9eaae214b: /build/S610_P/src/DataFlowEngine/ImbOdbc.cpp: 456: ImbOdbcHandle::checkRcInner: :
Regards,
Sarath |
|
| Back to top |
|
|
| sarathmattam |
| Posted: Sat Jul 10, 2010 3:56 am Post subject: |
|
|
Voyager
Joined: 05 Sep 2008
Posts: 94
|
Dear All,
I did lot of googling and everything points to 'binding the sql schema' using the below commands.
"db2 connect to database-name
db2 bind path\db2schema.bnd blocking all grant public sqlerror continue
db2 terminate
"
But do we need to restart the DB2 instance once i execute the above commands.?
Also what is the possibility of loosing the binding as didn't apply any patch and the current set up has been working fine for the last one year ? |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sat Jul 10, 2010 6:05 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I can recall in the dim and distant past having to bind a DB2 Database for use by broker but recently, I can't recall ever having to do it.
As the table in question is a DB2 Internal table then perhaps some DBa has been messing around with it and maybe flushed it thus your need to bind.
I'm inclined to point the finger here as the DB has been working well for so long unless you have stumbled upon a defect in the DB code itself.
Generally, I have not had to restart the DB after doing things like this but in this case but I does not take that long so why not...
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| sarathmattam |
| Posted: Sat Jul 10, 2010 9:12 pm Post subject: |
|
|
Voyager
Joined: 05 Sep 2008
Posts: 94
|
Dear All,
The issue seems to be resolved .. I have used the bind commands mentioned in my earlier post and restarted the DB2 instance.
Thanks for your help and guidance
Regards,
Sarath KS |
|
| 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
|
|
|
|
