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 » Invalid or unsupported name

Post new topic  Reply to topic
 Invalid or unsupported name « View previous topic :: View next topic » 
Author Message
nukalas2010
PostPosted: Wed Apr 24, 2013 2:33 am    Post subject: Invalid or unsupported name Reply with quote

Master

Joined: 04 Oct 2010
Posts: 220
Location: Somewhere in the World....

Dears,
We are calling one client database of Oracle using JDBC.
We are trying to send extended properties while we execute Oracle database commands, expecially the name of machine where we initiate the connection from because the remote database server, uses the client name as additional security.
We are trying to use Connection.setClientInfo("ClientHostname", "name_of_client") to send the properties while executing the command. However we are getting SQLClientInfoException with message "Invalid or unsupported ClientInfo property"

Code:
oConn = getJDBCType4Connection(sDSN,JDBC_TransactionType.MB_TRANSACTION_AUTO);
oConn.setClientInfo("ClientHostname", "XXXXXX");
oConn.setClientInfo("ApplicationName", "XXXXXX");


But after executing the second statement we are getting the exception as
Code:
java.sql.SQLClientInfoException: Invalid or unsupported name for clientInfo.


We followed the references from below:

http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/index.jsp?topic=%2Frzaha%2Fdatameta.htmhttp://publib.boulder.ibm.com/infocenter/idshelp/v111/index.jsp?topic=/com.ibm.jccids.doc/com.ibm.db2.luw.apdv.java.doc/doc/t0052428.htm

Are we missing any thing here ???

PS: we are using JDBC Driver version - Oracle 11.2.0.1.0 JDBC 4.0 compiled with JDK6

Thanks,
Back to top
View user's profile Send private message
mqjeff
PostPosted: Wed Apr 24, 2013 3:54 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

I'd have referenced documentation on the Oracle JDBC driver rather than potentially unrelated iSeries and Informix documentation.

I expect if you go to the Java JDK documentation (on Oracle's site), they will explain that the error you are receiving means that the JDBC driver in question does not understand "ApplicationName" as a valid piece of client information.

That is, I don't believe this has anything to do with broker or with JDBC, but with the particular JDBC client.
Back to top
View user's profile Send private message
nukalas2010
PostPosted: Wed Apr 24, 2013 6:00 am    Post subject: Reply with quote

Master

Joined: 04 Oct 2010
Posts: 220
Location: Somewhere in the World....

[quote="mqjeff"]
Quote:
I'd have referenced documentation on the Oracle JDBC driver rather than potentially unrelated iSeries and Informix documentation.

Yeah We agree, that's the only related information we got from IBM.

Quote:
I expect if you go to the Java JDK documentation (on Oracle's site), they will explain that the error you are receiving means that the JDBC driver in question does not understand "ApplicationName" as a valid piece of client information.


Sure we will check..

Quote:
That is, I don't believe this has anything to do with broker or with JDBC, but with the particular JDBC client


We are looking for, how can we send the extended properties like(ClinetName) through the connection..

Thanks...
Back to top
View user's profile Send private message
mqjeff
PostPosted: Wed Apr 24, 2013 6:19 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

nukalas2010 wrote:
Quote:
That is, I don't believe this has anything to do with broker or with JDBC, but with the particular JDBC client


We are looking for, how can we send the extended properties like(ClinetName) through the connection..

Thanks...


Yeah. and that setClientInfo appears to be the correct method to do that.

What I'm saying is that the JDBC provider you are using does not appear to understand anything about an extended property called 'ApplicationName', that's what it looks like the error you are getting is saying.
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 » Invalid or unsupported name
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.