| Author |
Message
|
| chinnureddy |
 Posted: Fri Oct 02, 2015 10:00 am Post subject: Unable to connect to Informix - JDBC |
 |
|
Newbie
Joined: 15 Sep 2013
Posts: 6
|
Hello,
I have a flow which connects to Informix using JDBC getJDBCType4Connection("test", JDBC_TransactionType.MB_TRANSACTION_AUTO);
Configurable service properties:
mqsireportproperties test -c JDBCProviders -o test -r
JDBCProviders
test
connectionUrlFormat='jdbc:informix-sqli://[serverName]:[portNumber]/[databaseName]:informixserver=[connectionUrlFormatAttr1];user=[user];password=[password]'
connectionUrlFormatAttr1='hp10'
connectionUrlFormatAttr2=''
connectionUrlFormatAttr3=''
connectionUrlFormatAttr4=''
connectionUrlFormatAttr5=''
databaseName='Order'
databaseType='default_Database_Type'
databaseVersion='default_Database_Version'
description='Order'
environmentParms='default_none'
jarsURL='default_Path'
maxConnectionPoolSize='0'
portNumber='1548'
securityIdentity='testidentity'
serverName='hp10'
type4DatasourceClassName='com.informix.jdbcx.IfxXADataSource'
type4DriverClassName='com.informix.jdbc.IfxDriver'
When my flow tries to establish connection it fails with reason jdbc:informix-sqli://HP10:1548/Order:informixserver
=hp10;user=mqsiUser;password=xxxxxxxx
error message: Incorrect password or user com.informix.asf.IfxASFRemote
Exception: mqsiUser is not known on the database server., SQLState value: IX000, vendor's error code: -951.
However this is not the user I set initially with mqsisetdbparms. The userid & password that were set originally with mqsisetdbparms still exists in registry under the path /var/prod/mqsi/mqsi/registry/<broker>/CurrentVersion/DSN/jdbc::test
I can't figure out from where it's taking the default user to connect to the Informix.
Any help is much appreciated. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Oct 02, 2015 10:04 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
is testidentity the actual name you used in mqsisetdbparms?
did you ensure that it was marked as a JDBC identity?
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| chinnureddy |
| Posted: Fri Oct 02, 2015 10:07 am Post subject: |
|
|
Newbie
Joined: 15 Sep 2013
Posts: 6
|
Yes this was used for testing the connectivity.
Command used:
mqsisetdbparms <brokername> -n jdbc::testidentity -u <username> -p <password> |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Oct 02, 2015 10:56 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
May be the password change since it was first setup?
Reset the password using mqsisetdbparms bounce the broker and try again...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Oct 02, 2015 10:59 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| fjb_saper wrote: |
May be the password change since it was first setup?
Reset the password using mqsisetdbparms bounce the broker and try again... |
It's using the wrong userid.
bouncing the EG's not a bad idea, though.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
|
|
