| Author |
Message
|
| Muthukrishnan |
 Posted: Thu Feb 13, 2014 8:30 am Post subject: SQL Server ODBC Error |
 |
|
Apprentice
Joined: 16 Feb 2013
Posts: 48
|
Hi All,
I am geting ConnectionOpen (Name or service not known() error while connecting to SQL Server 2008 using ODBC Connection in WMB 8.0.0.2, telnet is successful. Please assist.
ODBC.INI
| Code: |
Database=XXX
;# UNIX to SQLServer stanza
[XXX]
Driver=/opt/ibm/mqsi/8.0.0.2/ODBC64/V6.0/lib/UKmsss24.so
Description=DataDirect 6.0 ODBC SQL Server Wire Protocol
Address=XXXXXX\DEV02
#Alternative way to locate server using a named instance
#Address=<Your SQLServer Machine Name>\<Your SQLServer Instance Name>
AnsiNPW=Yes
Database=XXX
QuotedId=No
ColumnSizeAsCharacter=1
LoginTimeout=0
|
RecoverableException
| Code: |
File:CHARACTER:/build/slot1/S800_P/src/DataFlowEngine/ImbDataFlowNode.cpp
Line:INTEGER:1154
Function:CHARACTER:ImbDataFlowNode::createExceptionList
Type:CHARACTER:ComIbmComputeNode
Name:CHARACTER:SAP_POT_VENDOR_DATABSE_MF#FCMComposite_1_2
Label:CHARACTER:SAP_POT_VENDOR_DATABSE_MF.Compute
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Node throwing exception
DatabaseException
File:CHARACTER:/build/slot1/S800_P/src/DataFlowEngine/ImbOdbc.cpp
Line:INTEGER:2259
Function:CHARACTER:ImbOdbcConnection::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:XXX
Insert
Type:INTEGER:14
Text:CHARACTER:/opt/ibm/IE02/2.0.0/lib/libodbcinterface.so
DatabaseException
File:CHARACTER:/build/slot1/S800_P/src/DataFlowEngine/ImbOdbc.cpp
Line:INTEGER:2437
Function:CHARACTER:ImbOdbcConnection::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:20117
Insert
Type:INTEGER:2
Text:CHARACTER:11
Insert
Type:INTEGER:5
Text:CHARACTER:[unixODBC][IBM][ODBC SQL Server Driver][libssclient24]206112061120611
DatabaseException
File:CHARACTER:/build/slot1/S800_P/src/DataFlowEngine/ImbOdbc.cpp
Line:INTEGER:2437
Function:CHARACTER:ImbOdbcConnection::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:01000
Insert
Type:INTEGER:2
Text:CHARACTER:0
Insert
Type:INTEGER:5
Text:CHARACTER:[unixODBC][IBM][ODBC SQL Server Driver][libssclient24]ConnectionOpen (Name or service not known()). |
|
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Feb 13, 2014 8:32 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
What do you get from an mqsicvp command? Are you sure that data source is registered to the broker? Did this work and stop working, or is this new and has never worked?
Better information, better advice.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Muthukrishnan |
| Posted: Thu Feb 13, 2014 8:38 am Post subject: SQL Server ODBC Error |
|
|
Apprentice
Joined: 16 Feb 2013
Posts: 48
|
I guess we are using the same driver that was working fine for different SQL server DB. So is there any thing am missing. Below is the error output of mqsicvp.
| Code: |
BIP2393E: Database error: ODBC return code '-1' from data source ''XXX'' using ODBC driver manager ''/opt/ibm/IE02/2.0.0/lib/libodbcinterface.so''.
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.
BIP2322E: Database error: SQL State ''HY000''; Native Error Code '0'; Error Text ''[unixODBC][IBM][ODBC SQL Server Driver]The requested instance is either invalid or not running''.
The error has the following diagnostic information: SQL State ''HY000'' SQL Native Error Code '0' SQL Error Text ''[unixODBC][IBM][ODBC SQL Server Driver]The requested instance is either invalid or not running''
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.
BIP2322E: Database error: SQL State ''08001''; Native Error Code '11'; Error Text ''[unixODBC][IBM][ODBC SQL Server Driver][libssclient24]General network error. Check your network documentation.''.
The error has the following diagnostic information: SQL State ''08001'' SQL Native Error Code '11' SQL Error Text ''[unixODBC][IBM][ODBC SQL Server Driver][libssclient24]General network error. Check your network documentation.''
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.
BIP2322E: Database error: SQL State ''01000''; Native Error Code '11'; Error Text ''[unixODBC][IBM][ODBC SQL Server Driver][libssclient24]ConnectionOpen (XXXX\XXX()).''.
The error has the following diagnostic information: SQL State ''01000'' SQL Native Error Code '11' SQL Error Text ''[unixODBC][IBM][ODBC SQL Server Driver][libssclient24]ConnectionOpen (XXXX\XXX()).''
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.
BIP8040E: Unable to connect to the database.
The database cannot be accessed with the specified user Id and password pair.
- Check that the database is running.
- Check that the database has an adequate number of database connections available for use.
- On Windows, check that an ODBC connection has been created.
- On systems that use $ODBCINI, check that the file pointed to by $ODBCINI has been correctly updated.
- On z/OS check the BIPDSNAO member of the component's dataset, and check the DB2 64bit ODBC driver (DSNAO64C) is in the STEPLIB.
- Use mqsisetdbparms to set the password to the correct value and try again.
|
Last edited by Muthukrishnan on Thu Feb 13, 2014 8:49 am; edited 1 time in total |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Feb 13, 2014 8:44 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I didn't ask about the driver, I asked about the data source.
You also have not answered my other questions - is this new for this broker, or did it stop working?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Muthukrishnan |
| Posted: Thu Feb 13, 2014 8:48 am Post subject: SQL Server ODBC Error |
|
|
Apprentice
Joined: 16 Feb 2013
Posts: 48
|
| Sorry for that. I registered the datasource using mqsisetdbparms. This is the first time we are testing this. I even tried to restart the broker. But it dint solve the issue. |
|
| Back to top |
|
|
| Gralgrathor |
| Posted: Thu Feb 13, 2014 9:22 am Post subject: |
|
|
Master
Joined: 23 Jul 2009
Posts: 297
|
| Have you checked that the ip address associated with the hostname is correct? Have you checked that the instance is running and listening to the right port? |
|
| Back to top |
|
|
| Muthukrishnan |
| Posted: Thu Feb 13, 2014 9:29 am Post subject: SQL Server ODBC Error |
|
|
Apprentice
Joined: 16 Feb 2013
Posts: 48
|
| I have you checked the instance status using MYSQL. Its in running state and listening to the right port . Is Ip address association with the hostname is required? I have not used the ip address anywhere. Telnet is successful. Hence I assume Ip address is correctly associated with the hostname. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Feb 13, 2014 9:31 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Did you telnet to the server, or to the port that the db is listening on? It could be that the telnet port is open, but the other port is blocked by a firewall
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Muthukrishnan |
| Posted: Thu Feb 13, 2014 9:34 am Post subject: SQL Server ODBC Error |
|
|
Apprentice
Joined: 16 Feb 2013
Posts: 48
|
| Telnet was successful with the hostname and port number is which DB is running. |
|
| Back to top |
|
|
| Gralgrathor |
| Posted: Thu Feb 13, 2014 9:47 am Post subject: |
|
|
Master
Joined: 23 Jul 2009
Posts: 297
|
| Are you by chance connecting to TST in stead of DEV? Or otherwise using the wrong instance name? Are there any conspiracies in your vicinity? |
|
| Back to top |
|
|
| Muthukrishnan |
| Posted: Thu Feb 13, 2014 10:02 am Post subject: SQL Server ODBC Error |
|
|
Apprentice
Joined: 16 Feb 2013
Posts: 48
|
The instance name is correct. I do not think there is any problem. As per IBM infocenter, I am using host name and the instance name as below
| Code: |
Address=XXXXXX\DEV02
|
|
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Feb 13, 2014 12:03 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And this is your reply:
| Code: |
| BIP2322E: Database error: SQL State ''HY000''; Native Error Code '0'; Error Text ''[unixODBC][IBM][ODBC SQL Server Driver]The requested instance is either invalid or not running''. |
So something does not match what you're thinking it does in your environment 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
