Help installing gateway on non-database server

Question

I have a 64bit 10.2.0.3 database running on W2K3 64bit server. I need to access a SQL Server database (2005 version) on a different host.
I'd like some insight into installing the gateway services on a 32bit Wk23 machine to bridge the 64bit Oracle database to the SQL Server database.
IE: 64bit DB -> 32bit Gateway -> 2005 SQL Server DB
Thanks in advance.

Answer 1

There are four important things to consider when installing gateway or hsodbc .
1) the version of your database eg. 8i/9i/10g
2) Database library
3) Oracle transparent Gateway and Oracle's Heterogeneous Services ODBC - generic connectivity (HSODBC) are two different product.
4) You must have ODBC Driver setup on both servers{ i.e SERVER A Oracle database and SERVER B SQLSERVER} for generic connectivity hsodbc.
(if you are installing on Unix you must have to get ODBC driver for Unix (data direct third patry supplier).
But if you installing Oracle transparent Gateway you only need odbc driver configure on the SQLSERVER box.
NB: Point 3 and 4 are very important.
In point three you have to decide if you want to go with Oracle transparent Gateway (OR) Oracle's Heterogeneous Services ODBC.
A lot of my fellow DBAs have failed to explain this in details.
If you go for Oracle transparent Gateway you will have to buy additional license from oracle but the gateway can be use for multiple gateway configurations. In effect, this will become your transparent Gateway Server for many installation that require Gateway whether Unix or windows based configurations.
On the other hand, if you decide to go for generic connectivity (HSODBC) you still have to buy ODBC for UNIX (from data direct) unless you are on Windows Operating systems Server which come naturally with odbc installed.
In your case all your configurations are Windows based. Therefore no licensing issue for you if you are using generic connectivity (HSODBC). It will be all free.
During both odbc configurations, use system DSN and make sure you test them.
NB: I will not be going true system DSN configuration. It is simple, even my thirteen years old son could configure it.
Important:
a)
remeber to configure the initsid file in ORACLE_HOME\hs and remeber to name extactly the name giving to the DSN on SQLSERVER (SERVER B). so if it is named airwaves the init file should be name init_airwaves.ora
HS_FDS_CONNECT_INFO = airwaves -------> from DSN on SQLSERVER (SERVER B).
HS_FDS_TRACE_LEVEL = 4
set ODBCINI= d:\nigeria\xxxx\odbc\odbc.ini ------> path of odbc.ini on ORACLE (SERVER A).
b) tnsname .ora - in ORACLE (SERVER A). ORACLE_HOME\network\admin please add the entry as below to tnsnames.ora. there should always be two closing brackect after the SID entry and HS entry must be like below then follow by the last bracket as below. Any placement of the bracket will make the configuration fail.
airwaves=
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = nigeria)(PORT = 1530))
(CONNECT_DATA =
(SID = airwaves))
(HS=OK)
c) listener .ora - in ORACLE (SERVER A). ORACLE_HOME\network\admin please add the entry as below. The bleow might look funny.
NB:You might think the SQLSERVER (SERVER B) is not mentioned in the LISTENER:ORA. Yes that is true ! It will be mentioned via the DSN in init_airwaves HS_FDS_CONNECT_INFO definition.
LISTENER=
(ADDRESS_LIST =
(ADDRESS=(PROTOCOL=ipc)(KEY=PNPKEY))
(ADDRESS =(PROTOCOL = TCP)(HOST = nigeria)(PORT = 1530))
SID_LIST_LISTENER=
(SID_LIST =
(SID_DESC = (SID_NAME = nigeria)
(SID_DESC =
(SID_NAME = airwaves)
(ORACLE_HOME=c:\nigeria\ora18\oracle)
(PRESPAWN_MAX = 10)
(PROGRAM=hsodbc)
(ENVS=LD_LIBRARY_PATH=c:\nigeria\ora18\oracle\lib32:d:\nigeria\xxx\odbc\lib)
LOG_DIRECTORY_LISTENER=c:\nigeria\logs\ora18\LISTENER_nigeria
LOG_FILE_LISTENER= LISTENER_nigeria.log
LOGGING_LISTENER= ON
TRACE_LEVEL_LISTENER=OFF
TRACE_DIRECTORY_LISTENER= c:\nigeria\logs\ora18\LISTENER_nigeria
TRACE_FILE_LISTENER= LISTENER_nigeria.trc
USE_PLUG_AND_PLAY_LISTENER= OFF
STARTUP_WAIT_TIME_LISTENER= 0
CONNECT_TIMEOUT_LISTENER= 20
NB: although you are on 64bit oracle database on Windows make sure you point the library to lib32 as describe. Odbc uses 32bits.
Major pitfall to avoid for Unix configuration of hsodbc.
1. make sure you install ODBC for Unix.
a) The SHLIB_PATH and LD_LIBRARY_PATH must have $ORACLE_HOME/lib32 in their path
b) SHLIB_PATH and LD_LIBRARY_PATH must have odbc_home in their path
SHLIB_PATH=$ORACLE_HOME/lib32:$ORACLE_HOME/network/lib:/pkg/Ndc20/home/ora18/odbc32v53/lib:/usr/lib:/usr/ccs/lib:/usr/openv/netbackup/bin
export SHLIB_PATH
LD_LIBRARY_PATH=/usr/openv/netbackup/bin:$ORACLE_HOME/lib32:/pkg/Ndc18/home/ora18/odbc32v53/lib
export LD_LIBRARY_PATH
ODBCINI=/pkg/Ndc18/home/ora18/odbc32v53/odbc.ini >>>>>> (using data direct odbc on unix for sqlserver )
export ODBCINI
To check if this correct.
env at a unix prompt
or
cd $ORACLE_HOME then type
hsodbc
then you will received the banner below.
Oracle Corporation --- DONNERSTAG SEP 11 2008 12:22:48.154
Heterogeneous Agent Release 10.2.0.3.0 - Production Built with
Driver for ODBC
if it returns a banner then you are on the right way to sucessful configuration. if it generates core dump the go back and make sure the path are set correctly. if you get a banner then procced to the next step.
2)
You need only one listerner.ora adjust as above and also adjust the tnsnames.ora as well the brackect in tnsname is very important. if you get it wrong will be receiving ORA-12537: TNS:connection closed. This indicates that you have not set the lib as mentioned above.
Both Windows and Unix
1) reload the listener or stop and restart listener which ever you are comfortable with.
2) log on to sqlplus and create the dblink
3) CREATE DATABASE LINK "AIRCOM" CONNECT TO "airwaves_link"
IDENTIFIED BY "********"
USING 'airwaves'
----> airwaves_link ------Is the user name on SQLSERVER (SERVER B) identifed by is the password of the user
4) now test your connection from sqlplus using the link created.
-- > tnsping airwaves
Also make sure you have a known table on the sqlserver database
sqlplus " / as sysdba "
SQL> select * from account@aircom;
I hope this helps.
[email protected]