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 » ODBC problems

Post new topic  Reply to topic
 ODBC problems « View previous topic :: View next topic » 
Author Message
bocbocboc
PostPosted: Tue Feb 05, 2002 1:29 am    Post subject: Reply with quote

Newbie

Joined: 04 Feb 2002
Posts: 1

I'm using MQSI v2.1 on Win2000 with DB2 V7.2. I developed a message flow wtih a compute node that is trying to connect to the DB. However, every time I put a queue into the flow, it went to the failure queue container. I checked the trace file, found the following message:

1912 ImbOdbcHandle::checkRcInner, -1
1912 ImbOdbcHandle::checkRcInner, 42s02,-204,[IBM][CLI Driver][DB2/NT]SQL0204N 'DB2ADMIN.TXTPLATE2' is an undefined name. SQLSTATE=42704

I tried to connect that table by the command line, and it's worked, so I think there might be some problem related to ODBC, can anybody help me? thanks.
Back to top
View user's profile Send private message Send e-mail
NickB
PostPosted: Tue Feb 05, 2002 2:07 am    Post subject: Reply with quote

Centurion

Joined: 20 May 2001
Posts: 107
Location: Zurich Financial Services

This is probably caused by the fact that the table has been created by a different logon id to the id which is used to run the broker. Try creating a synonym to the table using the id of the broker.
Back to top
View user's profile Send private message
mpuetz
PostPosted: Tue Feb 05, 2002 9:30 am    Post subject: Reply with quote

Centurion

Joined: 05 Jul 2001
Posts: 149
Location: IBM/Central WebSphere Services

Hi,

instead of creating an alias as suggested, you might also
try to specify the schema for the table as well.
From your error message I assume your broker connects as
db2admin to your DB. If the owner of the database is
say userX, try

SELECT bla FROM Database.userX.TABLEX

instead of just

SELECT bla FROM Database.TABLEX

The latter uses the implicit schema of the broker, i.e. db2admin,
so your TABLEX might not be visible from this schema.


_________________
Mathias Puetz

IBM/Central WebSphere Services
WebSphere Business Integration Specialist
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 » ODBC problems
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.