Please see my other blog for Oracle EBusiness Suite Posts - EBMentors

Search This Blog

Note: All the posts are based on practical approach avoiding lengthy theory. All have been tested on some development servers. Please don’t test any post on production servers until you are sure.

Monday, February 06, 2012

DG4MSQL Installation/Configuration - 11g RAC

Oracle Database Gateways provide the ability to transparently access data residing in a non-Oracle system from an Oracle environment. This transparency eliminates the need for application developers to customize their applications to access data from different non-Oracle systems, thus decreasing development efforts and increasing the mobility of the application.
Applications can be developed using a consistent Oracle interface for both Oracle and SQL Server.
This post provides information about the hardware and software requirements and the installation procedure for Oracle Database Gateway for SQL Server.

Oracle Database Gateway for SQL Server is supported on the following Microsoft Windows (64-bit) operating systems:
•Microsoft Windows Server 2003 - all x64 editions
•Microsoft Windows Server 2003 R2 - all x64 editions
•Microsoft Windows XP Professional x64 Edition
•Microsoft Windows Vista x64 - Business, Enterprise, and Ultimate editions
•Microsoft Windows 2008 x64

all screen shots related to installation are given below.

If you don't see the further screen , check from the application table and bring to it at front

Listener will be configured only on the node where you started the installation , you will need to create the listener on the other node as well.

after the installation, you will see the new listener service in windows services

Configure the Gateway Initialization Parameter File
Choose a System Identifier for the Gateway
The gateway system identifier (SID) is an alphanumeric character string that identifies a gateway instance. You need one gateway instance, and therefore one gateway SID, for each SQL Server database you are accessing. The SID is used as part of the file name for the initialization parameter file. The default SID is dg4msql.
Customize the Initialization Parameter File
The initialization parameter file must be available when the gateway is started. During installation, the following default initialization parameter file is created:
Where ORACLE_HOME is the directory under which the gateway is installed.
A number of initialization parameters can be used to modify the gateway behavior.
# HS init parameters

Configure Oracle Net for the Gateway
The gateway requires Oracle Net to communicate with the Oracle database. After configuring the gateway, perform the following tasks to configure Oracle Net to work with the gateway:

Configure Oracle Net Listener for the Gateway
The Oracle Net Listener listens for incoming requests from the Oracle database. For the Oracle Net Listener to listen for the gateway, information about the gateway must be added to the Oracle Net Listener configuration file, listener.ora. This file by default is located in ORACLE_HOME\network\admin, where ORACLE_HOME is the directory under which the gateway is installed.

The following entries must be added to the listener.ora file:
•A list of Oracle Net addresses on which the Oracle Net Listener listens
•The executable name of the gateway that the Oracle Net Listener starts in response to incoming connection requests

      (ADDRESS = (PROTOCOL = TCP)(HOST = OR-11)(PORT = 1622))
ADR_BASE_LISTENERDG2 = D:\product\\dg_2
Configure the Oracle Database for Gateway Access
Before you use the gateway to access SQL Server data you must configure the Oracle database to enable communication with the gateway over Oracle Net.
To configure the Oracle database you must add connect descriptors to the tnsnames.ora file. By default, this file is in ORACLE_HOME\network\admin, where ORACLE_HOME is the directory in which the Oracle database is installed. You cannot use the Oracle Net Assistant or the Oracle Net Easy Config tools to configure the tnsnames.ora file. You must edit the file manually.


No comments: