Author |
Message
|
scar |
Posted: Thu May 01, 2008 11:21 am Post subject: [SOLVED]MB 6 Error |
|
|
Centurion
Joined: 23 Jun 2004 Posts: 145
|
we are usind
MQSI 6.0.0.3
MQ 6.0.2.3
DB2 8.1.1.144(FixPak 16)
I am seeing the following errors in the log deploying the flows
Any help is appreciated
Apr 30 15:30:45 olive WebSphere Broker v6003[803014]: (IASBV.X01.BROKER.$SYS_mqsi)[1]BIP2111E: Message broker internal error: diagnostic information 'DynamicSubscriptionEngine'. : IASBV.X01.BROKER.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S600_P/src/DataFlowEngine/JavaNodeLibrary/ImbPubSubDatabase.cpp: 242: ImbPubSubDatabase::ImbPubSubDatabase: DynamicSubscriptionEngine: DynamicSubscriptionEngine
Apr 30 15:30:45 olive WebSphere Broker v6003[803014]: (IASBV.X01.BROKER.$SYS_mqsi)[1]BIP2321E: Database error: ODBC return code '-1'. : IASBV.X01.BROKER.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S600_P/src/DataFlowEngine/ImbOdbc.cpp: 227: ImbOdbcHandle::checkRcInner: :
Apr 30 15:30:45 olive WebSphere Broker v6003[803014]: (IASBV.X01.BROKER.$SYS_mqsi)[1]BIP2322E: Database error: SQL State '38553'; Native Error Code '-443'; Error Text '[IBM][CLI Driver][DB2/AIX64] SQL0443N Routine "SYSIBM.SQLTABLES" (specific name "TABLES") has returned an error SQLSTATE with diagnostic text "SYSIBM:CLI:-727". SQLSTATE=38553 '. : IASBV.X01.BROKER.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S600_P/src/DataFlowEngine/ImbOdbc.cpp: 355: ImbOdbcHandle::checkRcInner: :
Apr 30 15:36:19 olive sendmail[565272]: m3S1F4O659540: to=mcewen@us.ibm.com, ctladdr=root (0/0), delay=2+19:21:15, xdelay=00:30:44, mailer=esmtp, pri=6151321, relay=e35.co.us.ibm.com. [32.97.110.153], dsn=4.0.0, stat=Deferred: A remote host did not respond within the timeout period. with e35.co.us.ibm.com.
Apr 30 15:40:56 olive WebSphere Broker v6003[712822]: (IASBV.X01.BROKER.default)[1]BIP2201I: Execution Group started: process '712822'; thread '1'; additional information: brokerName 'IASBV.X01.BROKER'; executionGroupUUID '1455f9a0-1901-0000-0080-cd406387f69b'; executionGroupLabel 'default'; defaultExecutionGroup 'false'; queueManagerName 'IASBV.X01.BROKER'; trusted 'false'; dataSourceName 'MQSIBKDB'; userId 'db2inst2'; migrationNeeded 'false'; brokerUUID '1355f9a0-1901-0000-0080-cd406387f69b'; filePath '/opt/IBM/mqsi/6.0'; workPath '/var/mqsi'; ICU Converter Path ''. : IASBV.X01.BROKER.1455f9a0-1901-0000-0080-cd406387f69b: /build/S600_P/src/DataFlowEngine/ImbMain.cpp: 351: main: :
Apr 30 15:41:09 olive WebSphere Broker v6003[712822]: (IASBV.X01.BROKER.default)[1]BIP2111E: Message broker internal error: diagnostic information 'DynamicSubscriptionEngine'. : IASBV.X01.BROKER.1455f9a0-1901-0000-0080-cd406387f69b: /build/S600_P/src/DataFlowEngine/JavaNodeLibrary/ImbPubSubDatabase.cpp: 242: ImbPubSubDatabase::ImbPubSubDatabase: DynamicSubscriptionEngine: DynamicSubscriptionEngine
Apr 30 15:41:09 olive WebSphere Broker v6003[712822]: (IASBV.X01.BROKER.default)[1]BIP2321E: Database error: ODBC return code '-1'. : IASBV.X01.BROKER.1455f9a0-1901-0000-0080-cd406387f69b: /build/S600_P/src/DataFlowEngine/ImbOdbc.cpp: 227: ImbOdbcHandle::checkRcInner: :
Apr 30 15:41:09 olive WebSphere Broker v6003[712822]: (IASBV.X01.BROKER.default)[1]BIP2322E: Database error: SQL State '38553'; Native Error Code '-443'; Error Text '[IBM][CLI Driver][DB2/AIX64] SQL0443N Routine "SYSIBM.SQLTABLES" (specific name "TABLES") has returned an error SQLSTATE with diagnostic text "SYSIBM:CLI:-727". SQLSTATE=38553 '. : IASBV.X01.BROKER.1455f9a0-1901-0000-0080-cd406387f69b: /build/S600_P/src/DataFlowEngine/ImbOdbc.cpp: 355: ImbOdbcHandle::checkRcInner: :
Apr 30 15:41:29 olive WebSphere Broker v6003[803014]: (IASBV.X01.BROKER.$SYS_mqsi)[6169]BIP4041E: Execution group '$SYS_mqsi' received an invalid configuration message. See the following messages for details of the error. : IASBV.X01.BROKER.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S600_P/src/DataFlowEngine/ImbConfigurationNode.cpp: 384: ImbConfigurationNode::evaluate: ComIbmConfigurationNode: ConfigurationNode
Apr 30 15:41:29 olive WebSphere Broker v6003[803014]: (IASBV.X01.BROKER.$SYS_mqsi)[6169]BIP2461E: Error casting character string '' to a TIMESTAMP. State = '-1' 'S22007' '0' '' : IASBV.X01.BROKER.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S600_P/src/CommonServices/ImbDateTime.cpp: 2797: ImbTimeStamp::fromString: :
Apr 30 15:41:29 olive WebSphere Broker v6003[590068]: (IASBV.X01.CONFIGMGR)[3342]BIP1536S: The Configuration Manager was unable to register for internal subscriptions with broker IASBV.X01.BROKER. : IASBV.X01.CONFIGMGR.agent: /build/S600_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 686: BrokerManager.resolveRegSub: IASBV.X01.CONFIGMGR: IASBV.X01.CONFIGMGR
Apr 30 15:41:29 olive WebSphere Broker v6003[590068]: (IASBV.X01.CONFIGMGR)[3342]BIP2086E: Broker IASBV.X01.BROKER could only process parts of the internal configuration message. : IASBV.X01.CONFIGMGR.agent: /build/S600_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 711: BrokerManager.logLogEntry: IASBV.X01.CONFIGMGR: IASBV.X01.CONFIGMGR
Apr 30 15:41:29 olive WebSphere Broker v6003[590068]: (IASBV.X01.CONFIGMGR)[3342]BIP4046E: Invalid configuration message. See the following messages for details of the error. : IASBV.X01.CONFIGMGR.agent: /build/S600_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 633: BrokerManager.logLogEntry: IASBV.X01.CONFIGMGR: IASBV.X01.CONFIGMGR
Apr 30 15:41:29 olive WebSphere Broker v6003[590068]: (IASBV.X01.CONFIGMGR)[3342]BIP2461E: Error casting character string '' to a TIMESTAMP. State = '-1' 'S22007' '0' '' : IASBV.X01.CONFIGMGR.agent: /build/S600_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 711: BrokerManager.logLogEntry: IASBV.X01.CONFIGMGR: IASBV.X01.CONFIGMGR
Apr
Last edited by scar on Tue May 06, 2008 10:59 am; edited 1 time in total |
|
Back to top |
|
 |
MrSmith |
Posted: Tue May 06, 2008 6:40 am Post subject: |
|
|
 Master
Joined: 20 Mar 2008 Posts: 215
|
First of all just by reading throught the exception messages it is a database related issue and having had a quick search on the internet found that it has something to do with binding and the SQLcolumns your using, it does not recognise the column number which if my memory serves me right is the way DB2 sets column values rather than by column heading name in some cases. The sites i visited wanted to make you a member hence I will leave it there. Here is a link to start you off tho
http://www.lazydba.com/db2/2__12898.html |
|
Back to top |
|
 |
scar |
Posted: Tue May 06, 2008 11:00 am Post subject: |
|
|
Centurion
Joined: 23 Jun 2004 Posts: 145
|
$ db2 bind db2schema.bnd blocking all grant public sqlerror continue
Resolved the issue. |
|
Back to top |
|
 |
kiruthigeshwar |
Posted: Mon Nov 05, 2012 12:57 am Post subject: |
|
|
Acolyte
Joined: 31 Oct 2012 Posts: 50
|
scar wrote: |
$ db2 bind db2schema.bnd blocking all grant public sqlerror continue
Resolved the issue. |
I ran the above command in db2 console. I got the below message
C:\IBM\SQLLIB>db2 bind C:\IBM\SQLLIB\bnd\db2schema.bnd blocking all grant public
sqlerror continue
LINE MESSAGES FOR db2schema.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
2440 SQL0440N No authorized routine named "RTRIM" of type
"FUNCTION" having compatible arguments was found.
SQLSTATE=42884
SQL0091N Binding was ended with "0" errors and "1" warnings.
As it is only a warning I proceeded. But still I get the following error when I start the broker.
BROKER.default ) Database error: SQL State ''38553''; Native Error Code '-443'; Error Text ''[IBM][CLI Driver][DB2/NT] SQL0443N Routine "SYSIBM.SQLTABLES" (specific name "TABLES") has returned an error SQLSTATE with diagnostic text "SYSIBM:CLI:-727". SQLSTATE=38553 ''.
And in toolkit it shows the broker isn't started. While it is started in the services. |
|
Back to top |
|
 |
Vitor |
Posted: Mon Nov 05, 2012 5:50 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
kiruthigeshwar wrote: |
And in toolkit it shows the broker isn't started. While it is started in the services. |
And this is on the same level of WMB and the same scenario as the 4 year old post you've reopened?
If so, you're using an out of support level of WMB & you should upgrade.
If not, perhaps you'd care to mention what you are using? Or would you like us to guess???  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
kiruthigeshwar |
Posted: Mon Nov 05, 2012 9:24 pm Post subject: |
|
|
Acolyte
Joined: 31 Oct 2012 Posts: 50
|
Vitor wrote: |
kiruthigeshwar wrote: |
And in toolkit it shows the broker isn't started. While it is started in the services. |
And this is on the same level of WMB and the same scenario as the 4 year old post you've reopened?
If so, you're using an out of support level of WMB & you should upgrade.
If not, perhaps you'd care to mention what you are using? Or would you like us to guess???  |
Am using MB 6.1 |
|
Back to top |
|
 |
|