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 » "Unable to load recource" on adding Data Source in

Post new topic  Reply to topic
 "Unable to load recource" on adding Data Source in « View previous topic :: View next topic » 
Author Message
dziku007
PostPosted: Thu Jul 26, 2012 3:13 am    Post subject: "Unable to load recource" on adding Data Source in Reply with quote

Apprentice

Joined: 26 Jul 2012
Posts: 32

hi,
I'm trying define Data Source in Mapping Node. I'm following the steps from websphere broker documentation "Adding a database as a source or target". (this is my first post so I'm not able to post URL's)

When I'm doing on source pane of *.msgmap right click-> Add Sources-> Data Sources->Database Selects->check in my db->OK i get:
"Unable to load resource
The following error was reported rdb://XE"
(XE is the name of my database model file *.dbm)

I have specified Database Definition File inside Data Design Project. I also create database connection (Test connection works). I can navigate to database objects via Data Project Explorer or Data Source Explorer tab.

I'm not sure how to set Mapping Node->Properties->Basic->Datasource i tried several options (with websphere documentation help) but without success.

Database: Oracle Express Edition 11g (11.2)
Message Broker Toolkit: Version: 7.0.0.1
System: Windows XP, 32-bit

many thanks for help
dd
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu Jul 26, 2012 3:19 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

right click on the mapping node, choose properties, then look at the fields on the property tab.

However did you also add the DB in the computer's system odbc/odbc64 view?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
dziku007
PostPosted: Fri Jul 27, 2012 6:44 am    Post subject: Reply with quote

Apprentice

Joined: 26 Jul 2012
Posts: 32

I've added DB in the computers system odbc configuration (Start->Run->odbcad32->Add and so on...)

what should I put into mapping node-> properties->datasource ?
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Jul 27, 2012 11:19 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

dziku007 wrote:
I've added DB in the computers system odbc configuration (Start->Run->odbcad32->Add and so on...)

what should I put into mapping node-> properties->datasource ?

The data source should be the name you defined in the ODBC setup...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
dziku007
PostPosted: Tue Jul 31, 2012 4:05 am    Post subject: Reply with quote

Apprentice

Joined: 26 Jul 2012
Posts: 32

now I have error during execution of database node:

2012-07-31 12:45:11.191860 3368 DatabaseException BIP2393E: Database error: ODBC return code ''-1'' from data source ''MYDB'' using ODBC driver manager ''odbc32.dll''.
The broker received an error when processing a database operation. The ODBC return code was ''-1''. See the following messages for information obtained from the database about this error.
Use the following messages to determine the cause of the error. Typical problems are an incorrect data source, or table names. Correct either the database or the broker configuration.
2012-07-31 12:45:11.191906 3368 DatabaseException BIP2322E: Database error: SQL State ''IM002''; Native Error Code ''0''; Error Text ''[Microsoft][Menedżer sterowników ODBC] Nie można odnaleźć nazwy źródła danych, a nie ma podanego sterownika domyślnego''.
The error has the following diagnostic information: SQL State ''IM002'' SQL Native Error Code ''0'' SQL Error Text ''[Microsoft][Menedżer sterowników ODBC] Nie można odnaleźć nazwy źródła danych, a nie ma podanego sterownika domyślnego''
This message may be accompanied by other messages describing the effect on the message broker itself. Use the reason identified in this message with the accompanying messages to determine the cause of the error.

MYDB is the name of my DSN in odbc configuration
sorry for not fully english log
Back to top
View user's profile Send private message
marko.pitkanen
PostPosted: Tue Jul 31, 2012 4:26 am    Post subject: Reply with quote

Chevalier

Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland

Hi dziku007,

Before you ran message through the flow, did you verify with mqsicv at the broker runtime environment that the data source is defined correctly for the broker ?

--
Marko
Back to top
View user's profile Send private message Visit poster's website
dziku007
PostPosted: Fri Aug 03, 2012 2:17 am    Post subject: Reply with quote

Apprentice

Joined: 26 Jul 2012
Posts: 32

it returnes:

C:\Program Files\IBM\MQSI\7.0>mqsicvp MB7BROKER -n MYDB

BIP8270I: Connected to Datasource 'MYDB' as user 'SAMPLE'. The datasource platfo
rm is 'Oracle', version '11.01.0000 Oracle 11.1.0.0.0'.
===========================
databaseProviderVersion = 11.01.0000 Oracle 11.1.0.0.0
driverVersion = 06.00.0175 (B0126, U0056)
driverOdbcVersion = 03.52
driverManagerVersion = 03.52.3012.0000
driverManagerOdbcVersion = 03.52.0000
databaseProviderName = Oracle
datasourceServerName = localhost
databaseName = N/A
odbcDatasourceName = MYDB
driverName = UKORA24.DLL
supportsStoredProcedures = Yes
procedureTerm = PL/SQL
accessibleTables = Yes
accessibleProcedures = Yes
identifierQuote = "
specialCharacters = None
describeParameter = Yes
schemaTerm = User Name
tableTerm = Table
sqlSubqueries = 31
activeEnvironments = 0
maxDriverConnections = 0
maxCatalogNameLength = 128
maxColumnNameLength = 30
maxSchemaNameLength = 30
maxStatementLength = 0
maxTableNameLength = 30
supportsDecimalType = Yes
supportsDateType = No
supportsTimeType = No
supportsTimeStampType = Yes
supportsIntervalType = No
supportsAbsFunction = Yes
supportsAcosFunction = No
supportsAsinFunction = No
supportsAtanFunction = No
supportsAtan2Function = No
supportsCeilingFunction = Yes
supportsCosFunction = Yes
supportsCotFunction = No
supportsDegreesFunction = No
supportsExpFunction = Yes
supportsFloorFunction = Yes
supportsLogFunction = Yes
supportsLog10Function = Yes
supportsModFunction = Yes
supportsPiFunction = No
supportsPowerFunction = Yes
supportsRadiansFunction = No
supportsRandFunction = No
supportsRoundFunction = Yes
supportsSignFunction = Yes
supportsSinFunction = Yes
supportsSqrtFunction = Yes
supportsTanFunction = Yes
supportsTruncateFunction = Yes
supportsConcatFunction = Yes
supportsInsertFunction = Yes
supportsLcaseFunction = Yes
supportsLeftFunction = Yes
supportsLengthFunction = Yes
supportsLTrimFunction = Yes
supportsPositionFunction = No
supportsRepeatFunction = Yes
supportsReplaceFunction = Yes
supportsRightFunction = Yes
supportsRTrimFunction = Yes
supportsSpaceFunction = Yes
supportsSubstringFunction = Yes
supportsUcaseFunction = Yes
supportsExtractFunction = No
supportsCaseExpression = No
supportsCastFunction = No
supportsCoalesceFunction = No
supportsNullIfFunction = No
supportsConvertFunction = Yes
supportsSumFunction = Yes
supportsMaxFunction = Yes
supportsMinFunction = Yes
supportsCountFunction = Yes
supportsBetweenPredicate = Yes
supportsExistsPredicate = Yes
supportsInPredicate = Yes
supportsLikePredicate = Yes
supportsNullPredicate = Yes
supportsNotNullPredicate = Yes
supportsLikeEscapeClause = Yes
supportsClobType = No
supportsBlobType = No
charDatatypeName = CHAR
varCharDatatypeName = VARCHAR2
longVarCharDatatypeName = CLOB
clobDatatypeName = N/A
timeStampDatatypeName = TIMESTAMP
binaryDatatypeName = RAW
varBinaryDatatypeName = RAW
longVarBinaryDatatypeName = BLOB
blobDatatypeName = N/A
intDatatypeName = NUMBER
doubleDatatypeName = BINARY_DOUBLE
varCharMaxLength = 4000
longVarCharMaxLength = 2147483647
clobMaxLength = 0
varBinaryMaxLength = 2000
longVarBinaryMaxLength = 2147483647
blobMaxLength = 0
timeStampMaxLength = 29
identifierCase = Upper
escapeCharacter = \
longVarCharDatatype = -1
clobDatatype = 0
longVarBinaryDatatype = -4
blobDatatype = 0

BIP8273I: The following datatypes and functions are not natively supported by da
tasource 'MYDB' using this ODBC driver: Unsupported datatypes: 'DATE, TIME, INTE
RVAL, CLOB, BLOB' Unsupported functions: 'ACOS, ASIN, ATAN, ATAN2, COT, DEGREES,
PI, RADIANS, RAND, POSITION, EXTRACT, CASE, CAST, COALESCE, NULLIF'
Examine the specific datatypes and functions not supported natively by this data
source using this ODBC driver.
When using these datatypes and functions within ESQL, the associated data proces
sing is done within WebSphere Message Broker rather than being processed by the
database provider.

Note that "functions" within this message can refer to functions or predicates.

BIP8071I: Successful command completion.

Invoking Database Node i still got exception:

ExceptionList
RecoverableException
File:CHARACTER:F:\build\S700_P\src\DataFlowEngine\ImbDataFlowNode.cpp
Line:INTEGER:1073
Function:CHARACTER:ImbDataFlowNode::createExceptionList
Type:CHARACTER:ComIbmMQInputNode
Name:CHARACTER:TestDB#FCMComposite_1_1
Label:CHARACTER:TestDB.MQ Input
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Node throwing exception
RecoverableException
File:CHARACTER:F:\build\S700_P\src\DataFlowEngine\ImbDatabaseNode.cpp
Line:INTEGER:313
Function:CHARACTER:ImbDatabaseNode::evaluate
Type:CHARACTER:ComIbmDatabaseNode
Name:CHARACTER:TestDB#FCMComposite_1_2
Label:CHARACTER:TestDB.Database
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Caught exception and rethrowing
DatabaseException
File:CHARACTER:F:\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:MYDB
Insert
Type:INTEGER:14
Text:CHARACTER:odbc32.dll
DatabaseException
File:CHARACTER:F:\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:IM002
Insert
Type:INTEGER:2
Text:CHARACTER:0
Insert
Type:INTEGER:5
Text:CHARACTER:[Microsoft][Menedżer sterowników ODBC] Nie można odnaleźć nazwy źródła danych, a nie ma podanego sterownika domyślnego[/list]
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Aug 03, 2012 4:31 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

dziku007 wrote:
Text:CHARACTER:[Microsoft][Menedżer sterowników ODBC] Nie można odnaleźć nazwy źródła danych, a nie ma podanego sterownika domyślnego[/list]


This is your problem. Literally. You've demonstrated that the ODBC is correctly configured using the mqsicvp, but when you do whatever you're doing that error message is being returned to WMB not by WMB; all WMB is doing is repeating the exact text of the message it's being given.

Your next diagnostic step is to find a native language speaker (Polish?) and see what the problem is. For all I know it says "input data longer than target field" and you just need to trim some spaces. It could equally say "operation not supported", "cheese out of range" or "insufficient pixie dust reserve to complete wish".

Read the error. Fix the error. The ODBC per se is clearly working, the database is cross about your operation.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Fri Aug 03, 2012 4:35 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Vitor wrote:
Your next diagnostic step is to find a native language speaker (Polish?) and see what the problem is. For all I know it says "input data longer than target field" and you just need to trim some spaces. It could equally say "operation not supported", "cheese out of range" or "insufficient pixie dust reserve to complete wish".


Does your Google not work?

EDIT:
dziku007 Did you create your DSN as a User datasource or as a System Datasource?
Back to top
View user's profile Send private message
dziku007
PostPosted: Fri Aug 31, 2012 12:38 am    Post subject: Reply with quote

Apprentice

Joined: 26 Jul 2012
Posts: 32

I created DNS as a User Datasource

sorry for no answer during last couple of days, I got a long holidays that I've just returned
Back to top
View user's profile Send private message
mqjeff
PostPosted: Fri Aug 31, 2012 1:54 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Create your DSN as a System DSN.

Then you know that all programs on the system will have access to it, rather than just those programs that are run by some particular user.
Back to top
View user's profile Send private message
dziku007
PostPosted: Thu Sep 06, 2012 2:14 am    Post subject: Reply with quote

Apprentice

Joined: 26 Jul 2012
Posts: 32

Quote:
Create your DSN as a System DSN


Now it works!

mea culpa, I missed that in documentation, I should read it more carefully.

Thanks for Your patience and help!
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 » "Unable to load recource" on adding Data Source in
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.