| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| sqlserver 2012 DsN connectivity issues |
« View previous topic :: View next topic » |
| Author |
Message
|
| sunu |
 Posted: Sun Nov 04, 2012 8:29 pm Post subject: sqlserver 2012 DsN connectivity issues |
 |
|
Newbie
Joined: 04 Nov 2012
Posts: 2
|
While running following commands from MB/MQ servers. we are getting these errors.we can connect SQLserver 2012 from local machine through management Studio and ODBC. Please help
mqsicvp -n DSLDSN -u svdefstg -p xxxxx
BIP2393E: Database error: ODBC return code '-1' from data source ''DSLDSN'' using ODBC driver manager ''libbipodbc.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 ''[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 ''[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 ''[IBM][ODBC SQL Server Driver][libssclient24]ConnectionOpen (SQL0043DAG02()).''.
The error has the following diagnostic information: SQL State ''01000'' SQL Native Error Code '11' SQL Error Text ''[IBM][ODBC SQL Server Driver][libssclient24]ConnectionOpen (SQL0043DAG02()).''
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 ''IM006''; Native Error Code '0'; Error Text ''[DataDirect][ODBC lib] Driver's SQLSetConnectAttr failed''.
The error has the following diagnostic information: SQL State ''IM006'' SQL Native Error Code '0' SQL Error Text ''[DataDirect][ODBC lib] Driver's SQLSetConnectAttr failed''
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 ''HY000''; Native Error Code '0'; Error Text ''[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 ''[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.
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. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Mon Nov 05, 2012 12:12 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Have you asked yourself these simple questions
1) Is the version of broker I am using known to work with SQLServer 2012?
2) Is SQLServer 2012 on the list of supported databases for the version of broker I am using.
3) Have I used the right drivers when setting up the ODBC Connection
You don't say what platform and what broker version/patch level you are using. This always helps.
_________________
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 |
|
|
| sunu |
| Posted: Tue Nov 06, 2012 7:45 pm Post subject: Resolved issue |
|
|
Newbie
Joined: 04 Nov 2012
Posts: 2
|
We are Using Linux OS and Brokker Version 7.0.0.3. Issue is resloved we used hostname, port number. below updated settings
[XXXDSN]
Driver=/opt/mqsi/7.0/ODBC/V6.0/lib/UKmsss24.so
Description=DataDirect 6.0 SQL Server Wire Protocol
Address=Hostname, 1433
AnsiNPW=Yes
Database=DB NAME
QuotedId=No
ColumnSizeAsCharacter=1
LoginTimeout=0
Thanks
Cheers |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Nov 06, 2012 11:44 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
And the answers to my first two questions are?
_________________
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 |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
