Always disabled state of Oracle db in Gupta Conn Admin

[Ramesh]

Hi,

I have changed sql.ini file to connect oracle 11g from windows server 2012. When I opened gupta connectivity administrator I can see the database but in disabled state. I have selected Oracle and clicked enable option. I got message a pop up message -Are you sure you want to enable this router? I clicked yes . It got enabled. Clicked OK. Then I got another pop up message "Please restart your application for these changes to take effect.". I clicked ok. But when I opened connectivity administrator, still the oracle is in disabled state.

Can somebody explain how to connect oracle by changing sql.ini file.
I have added below text in sql.ini file and the rest I left as it is.

[win32client.dll]
comdll=sqlora32

[oragtwy]
remotedbname=abcprod,@abcprod.world
fetchrow=20
maperror=0
nodefparse=no
longbuffer=32000

I want to know whether TD6.3 connect to Oracle 11g 64 bit database.



Many Thanks.
Ramesh

[Charlie]

Warning: I haven't used the connectivity administrator since the late 90's, so take all of this with a grain of salt !!!

Did you use the TD installer to put SQLORA32.DLL on the computer ? I ask, because the connectivity administrator is for configuring the setup of database instances, but only for database products chosen as part of the TD install.

I'm still on TD5.2, and we use the Oracle 11 64-bit database without any issues.

[Ramesh]

Thanks for the reply Charlie. After copying sqlora32.dll from Gupta folder to sqlbase folder itgot enabled. Now I am getting 9268 gci cnn error. Help me to solve this problem. I am using 11g 64 bit with TD 6.3

Many thanks
Ramesh

[Charlie]

I have no idea if sqlora32.dll is the only file needed. I've never done a post-TD-install copying of individual files to make connection to a database work.

The safest approach (in my mind, anyway) would be to make use of the TD installer (i.e. to specify connection to Oracle will be needed), to make sure you get all necessary support files.

I can only throw out very general suggestions (that certainly apply to TD 5.2 downward, and may apply to newer versions of TD too.)

Now you are getting into error messages *** I've never faced, and may be very specific to TD6.3 ???

*** 2015-11-06 edit: replaced "errors" with "error messages"

[wardies]

I ran up a test harness to see which SQL-related files are loaded when I connect using Oracle 32-bit client (you are using the 32-bit client, not 64-bit, right?)

Output from the SysInternals listdlls utility after successful connection in TD6.3 IDE includes the following:

Code: Select all

...\td63\SQLBAPW10.DLL
...\td63\icuuc53.dll
...\td63\icudt53.dll
...\td63\icuin53.dll
...\td63\sqlbase\sqlwntm.dll
...\td63\sqlora32.dll

You mentioned that you'd copied sqlora32.dll into the sqlbase folder but on my install it lives in the root of the TD63 install folder. Oddly, there is a copy of sqlwntm.dll in both folders though!

Perhaps try a full install with Oracle connectivity selected, then it should all work out of the box.

Edit: included full list of additional DLLs loaded after first SQL-related DLL

[Ramesh]

Hi Wardies,

Thank you for your reply. I have both 64 bit and 32 bit clients along with Oracle 11g 64 bit database but not sure how to select 32 bit client alone. When I am trying to connect I am getting 401 cannot connect database error. How to check which from which client it is connecting?

[wardies]

Hi Ramesh,

The most important thing is that your PATH environment variable must have the 32-bit Oracle client listed first. If the 64-bit client comes first, that's a guaranteed failure to connect.

Rather than edit your system environment (which might break other Oracle things), you could just create a separate launch.cmd file that contains the relevant path settings before launching your application EXE or TD IDE. E.g. (assuming your test application is test.apt):

Code: Select all

PATH=C:\oracle\product\client_32\bin;C:\Gupta\TD63;C:\Windows\system32;C:\Windows
cbi63.exe test.apt

(Replace relevant parts with your actual path to Oracle, TD6.3, etc.)

Or you can just type the above lines into an interactive CMD prompt.

This might be enough, or you might need to adjust other ORA_... and TNSADMIN environment variables if those are present on your system. However, the priority is to get TD to find your 32-bit Oracle DLLs first, then you can deal with any other errors.

I can also recommend SysInternals' ProcMon.exe utility for Oracle install/path issues; it really helps to see which files and registry entries TD/Oracle are trying (but failing) to open when there are problems. E.g. it will tell you immediately if the x64 DLLs are being loaded rather than x86.

[Ramesh]

Thanks Wardies. I will try and let you know the results. Thanks once again.