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 IndexWebSphere Message Broker SupportODBC Connection From Database Node Failed - On Windows 10

Post new topicReply to topic
ODBC Connection From Database Node Failed - On Windows 10 View previous topic :: View next topic
Author Message
EricL
PostPosted: Tue Aug 28, 2018 1:13 pm Post subject: ODBC Connection From Database Node Failed - On Windows 10 Reply with quote

Voyager

Joined: 10 Oct 2014
Posts: 82

Hi

I have a workflow needs to access DB, both IIB and MSSQL server are on the same windows platform (Win10), what I did:

1. Create ODBC datasource connection on windows (named as DSHRDB), it is working fine when do connection test.
2. Create a workflow with a Database Node, specifed Data Source as "DSHRDB"
3. Execte mqsisetdbparms command to set id/password for the broker node

mqsisetdbparms LocalBrkr -n DSNHRDB -u aaa -p bbb

4. Within Database Node ESQL program, there is one insert statement:
...
INSERT INTO dbo.USER_REGISTRANTS(FILE_NUMBER,REG_CODE,REGISTRATION_DATE...) VALUES(Root.MRM.FileNumber, Root.MRM.RegCategory...);
....

5. Double checked DB, table USER_REGISTRANTS is created, with schema "dbo"

Stragnely, ESQL program keep on getting "identifier 'dbo' can not be resolved" message, detail message shows:

The correlation name 'dbo.USER_REGISTRANTS' is not valid....

What could be wrong here? Please provide advice...

Thanks
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Aug 29, 2018 5:06 am Post subject: Re: ODBC Connection From Database Node Failed - On Windows 1 Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 25165
Location: Ohio, USA

EricL wrote:
The correlation name 'dbo.USER_REGISTRANTS' is not valid....

What could be wrong here? Please provide advice...


What happens when you use USER_REGISTRANTS not dbo.USER_REGISTRANTS?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
EricL
PostPosted: Wed Aug 29, 2018 6:18 am Post subject: Reply with quote

Voyager

Joined: 10 Oct 2014
Posts: 82

If take out 'dbo', the message become 'AGCO_REGISTRANTS' is not valid.
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Aug 29, 2018 6:29 am Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 25165
Location: Ohio, USA

EricL wrote:
If take out 'dbo', the message become 'AGCO_REGISTRANTS' is not valid.


Now try "Database.AGCO_REGISTRANTS".

Or "Database.USER_REGISTRANTS".

Whichever it is, as it seems to be changing.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
EricL
PostPosted: Wed Aug 29, 2018 7:46 am Post subject: Reply with quote

Voyager

Joined: 10 Oct 2014
Posts: 82

Sorry, the table name should be "USER_REGISTRANTS".

When use "Database", it becomes more interesting now,
The messages become:

Unresolvable database table reference "Database.USER_REGISTRANTS"


And similar messages popup for each every field trying to add values to:

Unresolvable database table reference FILE_NUMBER
Unresolvable database table reference REG_TYPE_CODE
.....

The SQL statement looks like:

INSERT INTO Database.USER_REGISTRANTS(FILE_NUMBER,
REG_TYPE_CODE,
REGISTRATION_CREATION_DATE,
CITY,
PROVINCE,
FSA_CODE,
LDU_CODE
)
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Aug 29, 2018 8:01 am Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 25165
Location: Ohio, USA

EricL wrote:
When use "Database", it becomes more interesting now,
The messages become:

Unresolvable database table reference "Database.USER_REGISTRANTS"


So when you thought "I wonder why it can't resolve the table reference; I wonder if it's looking in the wrong schema" and tried "Database.dbo.USER_REGISTRANTS", what happened?


_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
EricL
PostPosted: Thu Aug 30, 2018 3:03 pm Post subject: Reply with quote

Voyager

Joined: 10 Oct 2014
Posts: 82

Give it a try by using "Database.dbo.USER_REGISTRANTS", got same result as using Database.USER_REGISTRANTS....

E.g:

Unresolvable database table reference FILE_NUMBER
Unresolvable database table reference REG_TYPE_CODE
.....

The SQL statement looks like:

INSERT INTO Database.dbo.USER_REGISTRANTS(FILE_NUMBER,
REG_TYPE_CODE,
REGISTRATION_CREATION_DATE,
CITY,
PROVINCE,
FSA_CODE,
LDU_CODE
)
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexWebSphere Message Broker SupportODBC Connection From Database Node Failed - On Windows 10
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.