*************************************************************************
# This is a customized agent init file that contains the HS parameters
# that are needed for the Database Gateway for Microsoft SQL Server

Hi,
Thanks for making the changes and confirming the tnsping works.
We need to go through some checks to try and find why the problem is happening.

1. I have seen corrupted gateway trace files before. Can you confirm you installed the 64-bit DG4MSQL software and not the 32-bit version ? How are you trying to open the trace file and what is the name of the file ?

2. Can you check the log for the gateway listener LISTENERMSSQL or post here. For the dg4msql connection it will either say something like 'Establish rc=0' or give an error message.

3. From a command line can you stop and start the LISTENERMSSQL listener and post the output here ?

*1. I have seen corrupted gateway trace files before. Can you confirm you installed the 64-bit DG4MSQL software and not the 32-bit version ? How are you trying to open the trace file and what is the name of the file ?*

I confirm, yes, is x64. On documentation show: Oracle Database Gateway 11g release2(11.2) for M.W x64 (64-bit).
The name of trace is [dg4msql_agt_12232.trc] i'm trying by the [SQL Server Profile]

@edit
I visualized dates, and no trace is being generated with the current date

*2. Can you check the log for the gateway listener LISTENERMSSQL or post here. For the dg4msql connection it will either say something like 'Establish rc=0' or give an error message.*

Not exists file of log on the folder: C:\product\11.2.0\tg_1\NETWORK\log

Is this ?

*3-From a command line can you stop and start the LISTENERMSSQL listener and post the output here ?*

Hi,
If you cannot find the LISTENERMSSQL listener then make sure the gateway ORACLE_HOME/bin directory is in the path before any other Oracle installs.
On my system the listner log is in the directory -

Log messages written to C:\product\11.2.0\tg_3\diag\tnslsnr\mkirtley-uk\listener\alert\log.xml

so you should be able to find the equivalent on your system. Or if you get the listener stopped and started the messages detail where the files are located.

Everton,
The information shows thatthe LISTENERMSSQL is being started using the parameter file C:\app\admsetape\product\11.2.0\dbhome_1\NETWORK\ADMIN\listener.ora but it should be using the file C:\app\admsetape\product\11.2.0\tg_1\NETWORK\ADMIN\listener.ora.

Could you do the following -

1. Remove refernces to the gateway in the listener.ora in dbhome_1\NETWORK\ADMIN\listener.ora

2. Check if you have set the variable ORACLE_HOME. This is not recommended for Oracle on Windows and can cause problems such as this.

3. From a command line type -
set ORACLE_HOME
if it returns -
Environment variable ORACLE_HOME not defined
then it has not been set, otherwise issue -
set ORACLE_HOME=
and then confirm it has been unset -
set ORACLE_HOME
4. Check the PATH tomake sure the gateway ORACLE_HOME is first, then stop and start the listener LISTENERMSSQL. It should start with the parameter file -
C:\app\admsetape\product\11.2.0\tg_1\NETWORK\ADMIN\listener.ora.