ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Text:CHARACTER:[IBM][ODBC 20101 driver]1509

Post new topic  Reply to topic
 Text:CHARACTER:[IBM][ODBC 20101 driver]1509 « View previous topic :: View next topic » 
Author Message
matuwe
PostPosted: Thu Jun 09, 2011 8:21 am    Post subject: Text:CHARACTER:[IBM][ODBC 20101 driver]1509 Reply with quote

Master

Joined: 05 Dec 2007
Posts: 296

Hi Please help... I seem to be getting a lot of database errors on the one BROKER. I have now tried to fix this message catalog but not winning.

I tried to set the Environment Variable for the catalog,

rbrk1 /home/wbrkadm $echo $NLSPATH
/opt/IBM/mqsi/7.0/messages/%L/%N:/opt/IBM/mqsi/7.0/messages/En_US/%N:/opt/IBM/mqsi/7.0/messages/%L/%N:/opt/IBM/mqsi/7.0/messages/En_US/%N:/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat:/opt/IBM/mqsi/7.0/ODBC/V6.0/locale/en_US/LC_MESSAGES

And my ODBCINI is pointing to drivers

/opt/IBM/mqsi/7.0/ODBC/V6.0/lib/UKora24.so



Quote:

locale/localized_territory_directory/LC_MESSAGES

where localized_territory_directory depends on your language.

For instance, German localization files are stored in locale/de/LC_MESSAGES, where de is the locale for German.

If localized error messages are not available for your locale, then they will contain message numbers instead of text. For example:

[DataDirect] [ODBC 20101 driver] 30040



Please help as I don't know what to tell the ORACLE guys to look for, or what the error is. All I can see is that we are getting database Exception.
Back to top
View user's profile Send private message
matuwe
PostPosted: Thu Jun 09, 2011 8:30 am    Post subject: Reply with quote

Master

Joined: 05 Dec 2007
Posts: 296

IS THERE ANY other way to lookup these error codes

Text:CHARACTER:[IBM][ODBC 20101 driver][20101]11603
Back to top
View user's profile Send private message
matuwe
PostPosted: Thu Jun 09, 2011 8:48 am    Post subject: Reply with quote

Master

Joined: 05 Dec 2007
Posts: 296

Hi

It Looks like sometime it does give me a valid error code I just tried with wrong data and this is what I got

Text:CHARACTER:[IBM][ODBC 20101 driver][Oracle]ORA-00911: invalid character
Back to top
View user's profile Send private message
smdavies99
PostPosted: Thu Jun 09, 2011 9:05 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

The real error is indeed an invalid character.
Googling for ORA-00911 shows that.

There might well be other messages with the same timestamp in the event log that will tell you what the character is.

As has been documented here many times it is entirely possible that the problem lies in the bad data you are receiving. By bad I mean that the CCSID in the message wrapper (SOAP, HTTP, MQMD etc) says one thing and the actual data is formatted using another CCSID.
_________________
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
View user's profile Send private message
matuwe
PostPosted: Thu Jun 09, 2011 11:26 pm    Post subject: Reply with quote

Master

Joined: 05 Dec 2007
Posts: 296

Hi,

The second Error that has proper oracle error and number, that is if I force the data to be incorrect. And it seems to be giving me a proper number.

The one I am trying to fix, is the other errors that are happening and are getting database exception , This is a simple select statement from the DB? That works some times and doesn't work most of the time, with exactly the same data.


Quote:

ExceptionList
RecoverableException
File:CHARACTER:/build/S700_P/src/DataFlowEngine/ImbDataFlowNode.cpp
Line:INTEGER:1073
Function:CHARACTER:ImbDataFlowNode::createExceptionList
Type:CHARACTER:ComIbmMQInputNode
Name:CHARACTER:DelMechInputTargetID#FCMComposite_1_1
Label:CHARACTER:DelMechInputTargetID.ESB_TARGET_IDENTIFICATION
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Node throwing exception
RecoverableException
File:CHARACTER:/build/S700_P/src/DataFlowEngine/ImbComputeNode.cpp
Line:INTEGER:489
Function:CHARACTER:ImbComputeNode::evaluate
Type:CHARACTER:ComIbmComputeNode
Name:CHARACTER:DelMechInputTargetID#FCMComposite_1_7
Label:CHARACTER:DelMechInputTargetID.FindRoute
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Caught exception and rethrowing
RecoverableException
File:CHARACTER:/build/S700_P/src/DataFlowEngine/ImbRdl/ImbRdlStatementGroup.cpp
Line:INTEGER:625
Function:CHARACTER:SqlStatementGroup::execute
Type:CHARACTER:ComIbmComputeNode
Name:CHARACTER:DelMechInputTargetID#FCMComposite_1_7
Label:CHARACTER:DelMechInputTargetID.FindRoute
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2488
Text:CHARACTER:Error detected, rethrowing
Insert
Type:INTEGER:5
Text:CHARACTER:.DelMechInputTargetID_FindRoute.Main
Insert
Type:INTEGER:5
Text:CHARACTER:10.5
Insert
Type:INTEGER:5
Text:CHARACTER:SET Environment.DATASTORE.Destinations.ROUTES[ ] = (SELECT ROW (COLUMN(0) AS *:CONFIGID, COLUMN(1) AS *:CONDESCRIPTION, COLUMN(2) AS *:MESSAGETYPE, COLUMN(3) AS *:EXCLUSIONIN, COLUMN(4) AS *:EXCLUSIONLIKE1, COLUMN(5) AS *:EXCLUSIONLIKE2, COLUMN(6) AS *:TARGETDESKID, COLUMN(7) AS *:SOURCEDESKID, COLUMN( AS *:ZEROBYTEHALT, COLUMN(9) AS *:DAYSSTORED, COLUMN(10) AS *:ACTIVE, COLUMN(11) AS *:ACKTIMEOUT, COLUMN(12) AS *:DEPENDANCYTIMEOUT, COLUMN(13) AS *:PRIORITY, COLUMN(14) AS *:PRECEDENCE, COLUMN(15) AS *:QUEUEDDELIVERY, COLUMN(16) AS *:ENCDECMESSAGETYPE, COLUMN(17) AS *:ENCDECKEY, COLUMN(1 AS *:DELMECHID, COLUMN(19) AS *:DELMECHDESCRIPTION, COLUMN(20) AS *:DELMECHTYPENAME, COLUMN(21) AS *:DELMECHTYPEID, COLUMN(22) AS *:RETRYCOUNT, COLUMN(23) AS *:RETRYDELAY, COLUMN(24) AS *:ARCHIVEDELMECHID, COLUMN(25) AS *:ASYNCHRONOUS, COLUMN(26) AS *:VERSION, COLUMN(27) AS *:SOURCENAME, COLUMN(2 AS *:SOURCECODE, COLUMN(29) AS *:TARGETNAME, COLUMN(30) AS *:TARGETCODE, COLUMN(31) AS *:TARGETDESCRIPTION, COLUMN(32) AS *:TARGETID, COLUMN(33) AS *:SOURCEDESKCODE, COLUMN(34) AS *:TARGETDESKCODE) AS ? FROM DATABASE(, InputBody.ESB_INTERNAL.ESB_DATA.sourceSystem, UPPER(InputBody.ESB_INTERNAL.ESB_DATA.messageType), version));
DatabaseException
File:CHARACTER:/build/S700_P/src/DataFlowEngine/ImbOdbc.cpp
Line:INTEGER:341
Function:CHARACTER:ImbOdbcHandle::checkRcInner
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2393
Text:CHARACTER:Root SQL exception
Insert
Type:INTEGER:2
Text:CHARACTER:-1
Insert
Type:INTEGER:5
Text:CHARACTER:TESTDB
Insert
Type:INTEGER:14
Text:CHARACTER:libbipodbc.a(odbc.so)
DatabaseException
File:CHARACTER:/build/S700_P/src/DataFlowEngine/ImbOdbc.cpp
Line:INTEGER:480
Function:CHARACTER:ImbOdbcHandle::checkRcInner
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2322
Text:CHARACTER:Child SQL exception
Insert
Type:INTEGER:5
Text:CHARACTER:60
Insert
Type:INTEGER:2
Text:CHARACTER:1509
Insert
Type:INTEGER:5
Text:CHARACTER:[IBM][ODBC 20101 driver]1509
DatabaseException
File:CHARACTER:/build/S700_P/src/DataFlowEngine/ImbOdbc.cpp
Line:INTEGER:480
Function:CHARACTER:ImbOdbcHandle::checkRcInner
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2322
Text:CHARACTER:Child SQL exception
Insert
Type:INTEGER:5
Text:CHARACTER:21
Insert
Type:INTEGER:2
Text:CHARACTER:-1
Insert
Type:INTEGER:5
Text:CHARACTER:[IBM][ODBC 20101 driver][20101]11603
DatabaseException
File:CHARACTER:/build/S700_P/src/DataFlowEngine/ImbOdbc.cpp
Line:INTEGER:480
Function:CHARACTER:ImbOdbcHandle::checkRcInner
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2322
Text:CHARACTER:Child SQL exception
Insert
Type:INTEGER:5
Text:CHARACTER:08001
Insert
Type:INTEGER:2
Text:CHARACTER:0
Insert
Type:INTEGER:5
Text:CHARACTER:[IBM][ODBC 20101 driver]6173
DatabaseException
File:CHARACTER:/build/S700_P/src/DataFlowEngine/ImbOdbc.cpp
Line:INTEGER:480
Function:CHARACTER:ImbOdbcHandle::checkRcInner
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2322
Text:CHARACTER:Child SQL exception
Insert
Type:INTEGER:5
Text:CHARACTER:60
Insert
Type:INTEGER:2
Text:CHARACTER:1509
Insert
Type:INTEGER:5
Text:CHARACTER:[IBM][ODBC 20101 driver]1509
[/code]
Back to top
View user's profile Send private message
mqjeff
PostPosted: Fri Jun 10, 2011 3:23 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Is the broker or eg restarted between the times that it does work and the times that it doesn't work?

This kind of message usually indicates an environmental issue, where the command shell that ran mqsistart wasn't quite set up correctly.
Back to top
View user's profile Send private message
matuwe
PostPosted: Fri Jun 10, 2011 3:28 am    Post subject: Reply with quote

Master

Joined: 05 Dec 2007
Posts: 296

Hi Thanks for your response. No, Broker was never restarted.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Fri Jun 10, 2011 3:41 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Well.

You might stop the broker and review the command shell. Look particularly for things like NLS_LANG and etc variables either being set or not set.

And make sure you're using the mqsiprofile from your current fix level, rather than a modified one that you copied from a previous level or pointing at a previous install level.
Back to top
View user's profile Send private message
matuwe
PostPosted: Fri Jun 10, 2011 3:51 am    Post subject: Reply with quote

Master

Joined: 05 Dec 2007
Posts: 296

Thanks a mill, I will try to take the latest mqsiprofile into the .bash_profile. But just another question? I have 8 brokers and all of them are using the same bash_profile. I cannot understand why only these these two are giving problems. The only difference in these brokers is the ORA server I am connecting too is different.

Or am I reading to much into this problem
Back to top
View user's profile Send private message
smdavies99
PostPosted: Fri Jun 10, 2011 4:05 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

matuwe wrote:
The only difference in these brokers is the ORA server I am connecting too is different.


Ask the Oracle DBA what the CCSID of their databases are. Get them to show you exactly what they are. It two DB's are showing this problem then they might be setup to use the wrong CCSID.
_________________
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
View user's profile Send private message
matuwe
PostPosted: Fri Jun 10, 2011 7:02 am    Post subject: Reply with quote

Master

Joined: 05 Dec 2007
Posts: 296

I just spoke to the DBA.. and here is their response

In Oracle there is a character set that is used but it is set to UTF8 everywhere
Back to top
View user's profile Send private message
mqjeff
PostPosted: Fri Jun 10, 2011 7:27 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

If you are using Oracle:

* Your database must be created with NLS_CHARACTERSET of AL32UTF8.
* Your ODBC data source definition must include the setting ColumnSizeAsCharacter=1.

On UNIX and Linux platforms, this setting must be included in the appropriate stanza in the ODBC ini files.

On Windows platforms, this string value must be added to the ODBC data source key in the registry.

See Enabling ODBC connections to the databases for further information.
* For 32-bit connections, you must set the variable NLS_LANG in the broker environment to the value <yourlanguage>_<yourterritory>.AL32UTF8.
Back to top
View user's profile Send private message
matuwe
PostPosted: Fri Jun 10, 2011 8:18 am    Post subject: Reply with quote

Master

Joined: 05 Dec 2007
Posts: 296

Hi

I cannot find the variable find the variable NLS_LANG. I checked on the new mqsiprofile.. should it be there, what should I set it too??
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Text:CHARACTER:[IBM][ODBC 20101 driver]1509
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.