| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SQL State 'IM003' : Specified driver could not be found |
« View previous topic :: View next topic » |
| Author |
Message
|
| roonie |
 Posted: Tue Sep 29, 2009 11:51 pm Post subject: SQL State 'IM003' : Specified driver could not be found |
 |
|
Newbie
Joined: 29 Sep 2009
Posts: 2
|
Hi
I'm new to message broker and after going through IBM documentation, i tried setting up MB with Oracle. I'm getting error while creating broker. Following are the details. Please help me understand where i'm doing wrong.
Installed Message broker binaries (/opt/IBM/WMB61)
Installed Oracle 10g (/opt/oracle)
Installed MQ v6
Created required Queue Managers and made them cluster
I have DBA permissions for the databse
ODBC32.ini file has full access permissions with mqm:mqbrkrs
-> ran mqsi_setupdatabase oracle10 /opt/oracle
-> modified MQSIPROFILE to have the oracle/lib in Ld_Library_path and ODBCINI variable
-> copied ODBC32.ini file to my home directory and modified it accordingly.
-> created ConfigManager successfully.
-> While creating broker getting the following error:
mqsicreatebroker MBRK -i brkuser -a brkuser
-q BRK_QM -n BRKDB -u brkuser -p brkuser
| Code: |
BIP2321E: Database error: ODBC return code '-1'.
The message broker encountered an error whilst executing a database
operation. The ODBC return code was '-1'. See the following messages for
information obtained from the database pertaining to this error.
Use the following messages to determine the cause of the error. This is
likely to be such things as incorrect datasource or table names. Then
correct either the database or message broker configuration.
BIP2322E: Database error: SQL State 'IM002'; Native Error Code '0'; Error
Text '[MERANT][ODBC lib] Data source name not found and no default driver specified'.
The error has the following diagnostic information: SQL State 'IM002' SQL
Native Error Code '0' SQL Error Text '[MERANT][ODBC lib] Data source name not found and no default driver specified'
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. |
My ODBC32.ini file
| Code: |
;###################################################################################
;########## 32 bit ODBC database driver manager initialization file ################
;###################################################################################
;# It is recommended that you take a copy of this file and then edit the copy. #
;# #
;# #
;# 1. Complete the 'Mandatory information stanza' section at the end of the file. #
;# #
;# #
;# 2. For each data source, add the name of the data source into the 'List of #
;# data sources stanza' section. #
;# #
;# #
;# 3. For each data source, create a stanza in the 'Individual datasource stanzas' #
;# section. #
;###################################################################################
;#########################################
;###### List of data sources stanza ######
;#########################################
[ODBC Data Sources]
DB2V8DB=IBM DB2 version 8 ODBC Driver
DB2V9DB=IBM DB2 version 9 ODBC Driver
brkdb=DataDirect 5.3 Oracle Driver
ORACLERACDB=DataDirect 5.3 Oracle Driver (Real Application Clusters)
SYBASEDB=DataDirect 5.3 Sybase Wire Protocol
SYBASEDBUTF8=DataDirect 5.3 Sybase UTF8 Wire Protocol
SQLSERVERDB=DataDirect 5.3 SQL Server Wire Protocol
INFORMIXDB=IBM Informix ODBC Driver
;##########################################################
;########## Individual data source stanzas ################
;##########################################################
;# DB2 version 8 stanza
[DB2V8DB]
Driver=/opt/IBM/WMB61/lib/libdb2.so
Description=DB2V8DB DB2 ODBC Database
Database=DB2V8DB
;# DB2 version 9 stanza
[DB2V9DB]
Driver=/opt/IBM/WMB61/lib32/libdb2.so
Description=DB2V9DB DB2 ODBC Database
Database=DB2V9DB
;# Oracle stanza
[brkdb]
Driver=/opt/IBM/WMB61/ODBC32/V5.3/lib/UKor823.so
Description=DataDirect 5.3 Oracle Driver
EnableDescribeParam=1
OptimizePrepare=1
ServerName=brkdb
WorkArounds=536870912
ProcedureRetResults=1
ColumnSizeAsCharacter=1
;# Oracle Real Application Cluster stanza
[ORACLERACDB]
Driver=/opt/IBM/WMB61/ODBC32/V5.3/lib/UKor823.so
Description=DataDirect 5.3 Oracle Driver
EnableDescribeParam=1
OptimizePrepare=1
ServerName=<Your Oracle Net Service Name defined for the RAC>
WorkArounds=536870912
ProcedureRetResults=1
ColumnSizeAsCharacter=1
;#Sybase Stanza
[SYBASEDB]
Driver=/opt/IBM/WMB61/ODBC32/V5.3/lib/UKase23.so
Description=DataDirect 5.3 Sybase Wire Protocol
Database=<Your Database Name>
ServerName=<Your Sybase Server Name>
EnableDescribeParam=1
OptimizePrepare=1
SelectMethod=0
NetworkAddress=<Your Sybase Server Name>,<Your Sybase Port Number>
SelectUserName=1
ColumnSizeAsCharacter=1
EnableSPColumnTypes=2
;#Sybase Stanza for a UTF8 datasource
[SYBASEDBUTF8]
Driver=/opt/IBM/WMB61/ODBC32/V5.3/lib/UKase23.so
Description=DataDirect 5.3 Sybase Wire Protocol
Database=<Your Database Name>
ServerName=<Your Sybase Server Name>
EnableDescribeParam=1
OptimizePrepare=1
SelectMethod=0
NetworkAddress=<Your Sybase Server Name>,<Your Sybase Port Number>
SelectUserName=1
ColumnSizeAsCharacter=1
EnableSPColumnTypes=2
Charset=UTF8
;# UNIX to SQLServer stanza
[SQLSERVERDB]
Driver=/opt/IBM/WMB61/ODBC32/V5.3/lib/UKmsss23.so
Description=DataDirect 5.3 SQL Server Wire Protocol
Address=<Your SQLServer Server Name>,<Your SQLServer Server Port Number>
Database=<Your Database Name>
AnsiNPW=Yes
QuoteId=No
ColumnSizeAsCharacter=1
;# Informix stanza
[INFORMIXDB]
Driver=/opt/IBM/WMB61/lib/cli/iclit09b.sl
Description=IBM Informix ODBC Driver
ServerName=<Your Informix Server Name>
Database=<Your Database Name>
Start of change
;#########################################
;###### Mandatory information stanza #####
;#########################################
[ODBC]
;# To turn on ODBC trace set Trace=1
Trace=1
TraceOptions=3
TraceFile=/opt/logs/odbctrace32.out
TraceDll=/opt/IBM/WMB61/ODBC32/V5.3/lib/odbctrac.so
InstallDir=/opt/IBM/WMB61/ODBC32/V5.3
UseCursorLib=0
IANAAppCodePage=4
UNICODE=UTF-8 |
Last edited by roonie on Sun Oct 04, 2009 8:35 pm; edited 1 time in total |
|
| Back to top |
|
 |
| WMBDEV1 |
| Posted: Wed Sep 30, 2009 12:01 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
The -n parameter has the datasource name in uppercase but its in lowercase in the ODBC file. I'd correct that first before doing anything else  |
|
| Back to top |
|
|
| roonie |
| Posted: Sun Oct 04, 2009 8:33 pm Post subject: SQL State 'IM003' : Specified driver could not be found |
|
|
Newbie
Joined: 29 Sep 2009
Posts: 2
|
Now, I have rectified the above error.
Solution is you need to give which DSN you are using.
| Code: |
But, I was stuck at another step....getting follwoing exception
SQL State 'IM003': specified driver could not be found |
|
|
| 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
|
|
|
|
