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 » SQL Server ODBC Error as "ConnectionOpen"

Post new topic  Reply to topic
 SQL Server ODBC Error as "ConnectionOpen" « View previous topic :: View next topic » 
Author Message
new_to_wmb8
PostPosted: Fri Dec 27, 2013 2:30 am    Post subject: SQL Server ODBC Error as "ConnectionOpen" Reply with quote

Centurion

Joined: 28 May 2013
Posts: 127
Location: Hyderabad, India

Hi All,

I am geting ConnectionOpen (Name or service not known() error while connecting to SQL Server 2008 using ODBC Connection ,

below are details,

Quote:
Broker Version : 8.0.0.2

Code:

$ echo $ODBCINI
/var/mqsi/odbc/odbc.ini

Code:

$ echo $ODBCSYSINI
/opt/ibm/IE02/2.0.0/etc

ODBC.INI Stanza,
Code:

Database=ODB_Dev
;# UNIX to SQLServer stanza
[ODB_Dev]
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,1433
#Alternative way to locate server using a named instance
#Address=<Your SQLServer Machine Name>\<Your SQLServer Instance Name>
AnsiNPW=Yes
Database=ODB_Dev
QuotedId=No
ColumnSizeAsCharacter=1
LoginTimeout=0

DBPARAM command is Successful.
Exception List error :
Code:
RecoverableException
         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:ODB_DEV
               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
View user's profile Send private message
smdavies99
PostPosted: Fri Dec 27, 2013 2:51 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Does the mqsicvp command work?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
new_to_wmb8
PostPosted: Fri Dec 27, 2013 3:13 am    Post subject: Reply with quote

Centurion

Joined: 28 May 2013
Posts: 127
Location: Hyderabad, India

It is giving error. but i had another Database connection in that too the mqsicvp command didnot worked but the odbc connection is working.
Back to top
View user's profile Send private message
new_to_wmb8
PostPosted: Fri Dec 27, 2013 5:13 am    Post subject: Reply with quote

Centurion

Joined: 28 May 2013
Posts: 127
Location: Hyderabad, India

Quote:
mqsicvp -n <DSN name> -u <user Id> -p <password>
command give below error
:
Code:

BIP2393E: Database error: ODBC return code '-1' from data source ''ODB_Dev'' 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 ''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 '0'; Error Text ''[unixODBC][IBM][ODBC SQL Server Driver][libssclient24]ConnectionOpen (Name or service not known()).''.
The error has the following diagnostic information:     SQL State             ''01000''     SQL Native Error Code '0'     SQL Error Text        ''[unixODBC][IBM][ODBC SQL Server Driver][libssclient24]ConnectionOpen (Name or service not known()).''
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.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Dec 27, 2013 10:15 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

sounds like something might be wrong or missing from your /etc/hosts or /etc/services ...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
nukalas2010
PostPosted: Sun Dec 29, 2013 4:26 am    Post subject: Reply with quote

Master

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

Check whether can you able to do telnet or not..

Code:
ex: telnet <Host Ip> <port>
Back to top
View user's profile Send private message
new_to_wmb8
PostPosted: Sun Dec 29, 2013 11:06 pm    Post subject: Reply with quote

Centurion

Joined: 28 May 2013
Posts: 127
Location: Hyderabad, India

when i did Telnet using putty as Message Broker is on Aix environment.

Quote:

telnet XYZXXX\DB02 1433 , it shows as " Name or service not known"

when did only
telnet XYZXXX 1433 , it shows Trying 172.X.X.X... connected XYZXXX


when i did Telnet from Windows system where broker is installed and remotely connectes to AIX Broker,
Quote:

C:\Users\kkapoor>telnet XYZXXX\DB02 1433
Connecting To XYZXXX\DB02 ...Could not open connection to the host, on
port 1433: Connect failed
Back to top
View user's profile Send private message
stoney
PostPosted: Mon Dec 30, 2013 3:08 am    Post subject: Reply with quote

Centurion

Joined: 03 Apr 2013
Posts: 140

In your odbc.ini, you are specifying both the port and the instance name:

Code:
Address=XXXXXX\DEV02,1433


In the sample odbc.ini provided, you can specify the port, or the instance name, but not both:

Code:
Address=<Your SQLServer Machine Name>,<Your SQLServer Port Number>
;# Alternative way to locate server using a named instance
;# Address=<Your SQLServer Machine Name>\<Your SQLServer Instance Name>


You should try removing either the port or the instance name from your odbc.ini:

Code:
Address=XXXXXX,1433


-or-

Code:
Address=XXXXXX\DEV02
Back to top
View user's profile Send private message
Muthukrishnan
PostPosted: Wed Feb 12, 2014 2:08 am    Post subject: SQL Server ODBC Error as "ConnectionOpen" Reply with quote

Apprentice

Joined: 16 Feb 2013
Posts: 48

Hi,

Even I am getting the same error. The broker version is same. WMB Version 8.0.0.2. But I have updated the odbc.ini as below. I am able to do telnet to SQL server from our linux server. But I am getting the same exception.

Code:


Address=XXXXXX\DEV02



Is there anything else I am missing. Please assist.
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SQL Server ODBC Error as "ConnectionOpen"
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.