Connect oracle to ms sqlserver

Question

hi i tried to crate database link i got some error:i start tnsname.ora and listener.ora files started succesfully.
when i run this sql statment gor error:
select * from s_30_login@mysqlserverdsn
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
ORA-28541: Error in HS init file on line 6.
ORA-02063: preceding 2 lines from MYSQLSERVERDSN
i changed my listener.ora file like this;
# listener.ora Network Configuration File: /u01/oracle/product/10.2.0/db_1/network/admin/listener.ora
# Generated by Oracle configuration tools.
#SID_LIST_LISTENER =
# (SID_LIST =
# (SID_DESC =
# (SID_NAME = orcl)
# (ORACLE_HOME = /u01/oracle/product/10.2.0/db_1)
# (PROGRAM =hsodbc )
#LISTENER =
# (DESCRIPTION_LIST =
# (DESCRIPTION =
# (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
# (ADDRESS = (PROTOCOL = TCP)(HOST = #localhost.localdomain)(PORT = 1521))
LISTENERMYSQLSERVERDSN =
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1522))
(ADDRESS=(PROTOCOL=ipc)(KEY=PNPKEY)))
SID_LIST_LISTENERMYSQLSERVERDSN=
(SID_LIST=
(SID_DESC=
(SID_NAME=MYSQLSERVERDSN)
(ORACLE_HOME = /u01/oracle/product/10.2.0/db_1)
(PROGRAM=hsodbc)
#LISTENERMYSQLSERVERDSN =
# (ADDRESS_LIST=
# (ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521))
# (ADDRESS=(PROTOCOL=ipc)(KEY=PNPKEY)))
#SID_LIST_LISTENERMYSQLSERVERDSN==
# (SID_LIST=
# (SID_DESC=
# (SID_NAME=MYSQLSERVERDSN)
# (ORACLE_HOME=/u01/oracle/product/10.2.0/db_1)
# (PROGRAM=hsodbc)
and changed my tnsname.ora like this ;
# tnsnames.ora Network Configuration File: /u01/oracle/product/10.2.0/db_1/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.
ORCL =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost.localdomain)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = orcl)
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
MYSQLSERVERDSN =
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1522))
(CONNECT_DATA=(SID=MYSQLSERVERDSN))
(HS=OK)
this is my init file;
# This is a sample agent init file that contains the HS parameters that are
# needed for an ODBC Agent.
# HS init parameters
HS_FDS_CONNECT_INFO = MYSQLSERVERDSN
HS_FDS_TRACE_LEVEL = OFF
HS_FDS_SHAREABLE_NAME = <full path name of odbc driver manager or driver>
# ODBC specific environment variables
set ODBCINI=<full path name of the odbc initilization file>
# Environment variables required for the non-Oracle system
set <envvar>=<value>
Edited by: 837211 on Feb 16, 2011 4:00 AM
Edited by: 837211 on Feb 16, 2011 4:08 AM

Answer 1

The error states you have an error in the gateway config file line 6 which contains:
HS_FDS_SHAREABLE_NAME = <full path name of odbc driver manager or driver>
Other errors are:
HS_FDS_SHAREABLE_NAME = <full path name of odbc driver manager or driver>
# ODBC specific environment variables
set ODBCINI=<full path name of the odbc initilization file>
# Environment variables required for the non-Oracle system
set <envvar>=<value>
=> for HS_FDS_SHAREABLE_NAME you need to refer to an ODBC Driver Manager. Depending on the foreign ODBC driver you are using the ODBC driver manager is included in the ODBC driver setup or it needs to be installed from a 3rd party vendor like unixodbc.org
You're also missing the ODBCINI reference:
set ODBCINI=<full path name of the odbc initilization file>
=> here you need to refer to the odbc.ini file which contains the odbc driver library reference and the connect details to the foreign database.
Finally comment out by simply adding a hash sign in front of this line.
#set <envvar>=<value>
=> so what you now need to configure is the ODBC driver that is used to connect to the SQL Server. This depends on the ODBC vendor you are using and you have to check out the vendors manual how to set it up correctly. At the end you'll have an odbc.ini somewhere on your machine and when using any ODBC test utility (for example isql) you can connect with the ODBC driver to the SQL Server.
Only when the ODBC driver setup is done, you can add the missing 2 parameters to your gateway init file and test the link again.
Edited by: kgronau on Feb 16, 2011 1:47 PM
By the way - HSODBC has been desupported since March 2008. So you might better think about using the follow up product Database Gateway for ODBC (=DG4ODBC).