Executables from TD6.2.2 connects to oracle after 2 minutes

[asoultanis]

I have made executables with TD 6.2.2 version. When I execute them in a 32bit machine(xp or win7) they are connecting to oracle just fine but when I execute them in 64bit(win7) machine it takes more than 2 minutes to connect to oracle (SQLConnect). The weird part is that when I run the code throught the IDE in 64bit(win7) everything works ok. I have tried to run exe in TDs installed directory, change the machine's enviroment path or change the ini params but nothing works.TD 1.5.3 and 5.2.3 executables work fine. All the tests have been made with oracle client 11g 32bit and the oracle db is 11g. Please advise.

[Mike Vandine]

Here are some replies from Development and Support:

“We have not been able to reproduce this problem. We need more information as to the exact problem and a reproducible testcase.”

“They need to check to see if the same sql.ini is loaded in both environments. Remotedbname inside oragtwy section should be same and check for tnsnames.”

“It is very possible to connect via ODBC to ORACLE when you intended to connect via SQLORA. This can happen when you have the same REMOTEDBNAME for ORACLE as an ODBC DSN (SQLODB loads at first try to connect even if it is commented out in SQL.INI). You can also have a SQL.INI where you have ROUTER LOG enabled. This is known to cause slow performance.

Also using TNS:your_ORA_INST in ORACLE instead of @your_ORA_INST is also known to be bad for performance. Your SQL.INI can also have hundreds of remotedbname entries which would also account for bad performance.

The best way to go about troubleshooting this is to use DEPENDENCY WALKER in PROFILE mode along with PROCESS MONITOR and also process explorer. What SQL.INI gets loaded when comparing IDE vs .EXE, what DLLs are loaded ( version etc.) If they can reproduce this, we need a solid test case that shows us the exact circumstances.”

So, it looks like you need to check the sql.ini files that are loaded in both circumstances, i.e. when running from the GUI and running as an EXE. Compare these and also which DLLs are being loaded in the two environments. In any case, if you can reproduce this, we would need a testcase that shows us the problem.

Hope this helps!

Best regards,

[asoultanis]

The sql.ini is the same from both TD and exe. TD 1.5.3 and 5.2.3 executables work fine with this ini.
I have attached a code sample app , sql.ini used , the exe file and screenshots. I can give you access to this machine if neccessary.

testOracleConnection.rar

[mcwizardry]

We discovered ( by accident ) that we could speed up the connect by using DIAG_ADR_ENABLED=OFF in SQLNET.ORA.