TD 5.2 connecting to Oracle 10GXE

[44Tonner]

I just purchased my own copy of TD 5.2 for a project as I retired from my day job. In my previous life the SQL.INI was already there and all I did was develop applications. I've been using SQLWindows since 1994 1.5 with Ptf 6

I have Oracle 10GXE running on a XP laptop and TD 5.2 and the Oracle client on a Windows 7 laptop. I can connect to 10GXE from the Client laptop with Oracle SQLPLUS with no problem. I cannot connect to 10GXE with SQLTalk. I'm getting
"00133 SQL IVE ERROR 26413 NOT FOUND IN ERROR.SQL"

SQL.INI below
_________________________________________________________________________________________________________

; SQL.INI 2005-10-14

[winclient]
clientname=WinClient

[winclient.dll]
comdll=sqloraw

[winclient.nbiow]

[winclient.spxw4]

[winclient.wsock]

[win32client.comments]
;
; Win32 (Windows 95 or NT)
;--------------------------
; Use this section to specify Win32 client workstation parameters that
; are independent of the communications protocol(s) being used.
;
; This section is for the Win32 client workstations. Here you will specify
; the COMmunication DLL(s) that the Win32 application(s) intend to use.
; Use the following protocol(s) to connect to the specified SQLBase product:
;
; comdll SQLBase target
; ------ --------------
; sqlapipe LOCAL database using Anonymous Pipes
; sqlntnbi REMOTE database using NetBios
; sqlws32 REMOTE database using TCP/IP (WinSock)
; sqlspx32 REMOTE database using IPX/SPX (Win32 Novell Client)
; sqlwsspx REMOTE database using IPX/SPX (Win32 Microsoft Client)
;
[win32client]
clientname=Win32User

[win32client.dll]
comdll=sqlora32
comdll=sqlapipe
;comdll=sqlwsspx
;comdll=sqlntnbi
;comdll=sqlws32

[win32client.apipe]

[win32client.ntnbi]
;
[win32client.ws32]
;
[win32client.spx32]

[win32client.wsspx]
;
[nwclient.comments]
; Netware clients
;-------------------
; Add this to the sql.ini for netware clients for SQLAPI for Netware and 2pc.
; Use this section to specify Netware client workstation parameters that
; are independent of the communications protocol(s) being used.
;
[nwclient]
;clientname=NWUser

[nwclient.dll]
;comdll=sqlspx

[nwclient.spx]

[patch.comments]
;
; This section is only used if running the NLM Database Server on a
; NETFRAME machine.
;
[patch]

[oragtwy]
; Modify remotedbname to reflect your Database configuration

remotedbname=XE,@TNS:XE


longbuffer=32760
fetchrow=20
maperror=OFF

; Substitutions currently needed by VISUAL Mfg
; NOTE: The first four lines must precede the other substitutions
; (specifically, they must precede the other @DATEVALUE substitutions)
substitute=@DATEVALUE(''),TO_DATE(NULL)
substitute=@datevalue(''),TO_DATE(NULL)
substitute=@DATEVALUE(NULL),TO_DATE(NULL)
substitute=@datevalue(NULL),TO_DATE(NULL)
substitute=@DECODE,DECODE
substitute=@DATEVALUE,TRUNC
substitute=@ROUND,ROUND
substitute=@NULLVALUE,NVL
substitute=@TRIM,RTRIM
substitute=@VALUE,TO_NUMBER
substitute=@LENGTH,LENGTHB
substitute=@SDV,STDDEV
substitute=SYSSQL.,
substitute=SYSADM.,
substitute=SYSUSERAUTH,SYS.USER$
substitute=@decode,DECODE
substitute=@datevalue,TRUNC
substitute=@round,ROUND
substitute=@nullvalue,NVL
substitute=@trim,RTRIM
substitute=@value,TO_NUMBER
substitute=@length,LENGTHB
substitute=@sdv,STDDEV
substitute=syssql.,
substitute=sysuserauth,SYS.USER$
substitute=sysadm.,
substitute=SYSDATETIME,SYSDATE
substitute=sysdatetime,SYSDATE

________________________________________________________________________________________________

Any ideas what I need to change in the SQL.INI to get connected so I can start developing my project???

Thanks

Gary Greenwood
Leslie, MI

[Jeff Luther]

I don't off-hand know. I'll post something internally and see what info. I get. In the meantime:

Your entry remotedbname=XE,@TNS:XE means you have a TSNAMES.ORA client-side installed with "XE" declared for your DB?

Have you tried connecting via ODBC?

FYI, for anyone who wants to know about this DB, here's a link to the Oracle page: https://www.oracle.com/technology/produc ... index.html

[44Tonner]

Jeff, First thanks for taking a look at this. I've been working with my Oracle DBA and we were able to connect to the XE DB using Oracle's SQLPLUS. It connects fine on the client side and we can run SQL scrips against it OK. I just can't get it to connected with SQLTalk. I have no idea how to connect to it using ODBC. Send me a SQL.INI or tell me how to try it and I will. Thanks Gary

[Jeff Luther]

Couple things to check and/or see:
* attach your TNSNAMES.ORA file
(On my Oracle 10g client, that file is located in this folder: C:\oracle\product\10.2.0\client_1\NETWORK\ADMIN )

* be sure that the Oracle client is in the PATH. (SQLPLUS might just be running local; TD app. or SQLTalk on the other hand had to find it and thus )

* be sure the TD install is correct and in the PATH.

* one BIG issue/question: Why is the "clientruntimedir" entry in your INI file missing? This is what I would expect in the [win32client] section:
[win32client]
clientname=Win32User
clientruntimedir="C:\Program Files\Unify\Team Developer 5.2"

You have clientname=Win32User but why is "clientruntimedir" missing? That should have been correctly written when you installed TD v5.2. That needs to be in the INI file. NOTE: that full path for "clientruntimedir" in bold above is mine, yours will be different if you didn't install TD in the default folder.

"I have no idea how to connect to it using ODBC. Send me a SQL.INI" -- see Ch. 7 of the PDF book: CCOD.PDF for details if you want to try that. But get the other issues above ironed out first.

[44Tonner]

I went through the same routine as before. First I connected to XE throught SQLPlus and it connects and disconnects fine.
The client laptop does not have the XE DB on it. Only the client software. I know it's connecting through the network.

Changed the SQL.INI to include clientruntimedir="C:\Program Files (x86)\Unify\Team Developer 5.2"
This is a Windows 7 laptop. Still getting the same error as before. "00133 SQL IVE ERROR 26413 NOT FOUND IN ERROR.SQL"

Also I don't have the "Books" for TD. They didn't down load with TD 5.2 Sales said to download from the "DEMO" site and put the "KEY" in and I would have the full version. NO BOOKS.

ALSO there are two versions of SQLTalk. One in the TD 5.2 dir 1612KB and another in SQLBase dir 1256KB. They are different sizes. If I use the one in the SQLBase I get a different error. SQL Error 401 "00401 DBA COD Cannot open database" Yes both SQL.ini are the same. When I'm trying SQLTalk in the TD 5.2 dir I've changed the name of the SQL.ini in the SQLBase dir so there is only one avaialble.



current SQL.ini

_____________________________________________________________________________________________________

; SQL.INI 03-25-2010
[winclient]
clientname=WinClient

[winclient.dll]
comdll=sqloraw


[win32client]
clientname=Win32User
clientruntimedir="C:\Program Files (x86)\Unify\Team Developer 5.2"


[win32client.dll]
comdll=sqlora32
comdll=sqlapipe
;comdll=sqlwsspx
;comdll=sqlntnbi
;comdll=sqlws32

[oragtwy]
; Modify remotedbname to reflect your Database configuration

remotedbname=XE,@TNS:XE


longbuffer=32760
fetchrow=20
maperror=OFF

____________________________________________________________________________________________________

tnsnames.ora

____________________________________________________________________________________________________
XE =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 199.5.83.199)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = XE)
)
)

EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
)
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
)
)

ORACLR_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
)
(CONNECT_DATA =
(SID = CLRExtProc)
(PRESENTATION = RO)
)
)


__________________________________________________________________________________________________

Thanks Gary

[Jeff Luther]

4 things come to mind:

** Comment out that sqlpipe entry in your SQL.IN, like this:
[win32client.dll]
...
; comdll=sqlapipe

** Probably is, but make sure you have the Oracle v10 client installed. 5.2 now only supports v10 and v11 clients

** Start with a simple connect-only test TD app in SAM_AppStartup, put it in your TD install folder and run it. What's the SQL Error? Same as in SQLTalk?

** As a test, comment out all those substitutes. Both I and a dev. guy noted that when I'd shown him your INI. Probably not an issue, but...

[44Tonner]

First the suggestion to try connecting with TD 5.2 helped. It gave me an ORA-06413 error. I looked for that on the net and got two good hits.

http://tim.bellette.net/2010/02/17/orac ... -open-x64/

http://portal.sqltrainer.com/2007/11/sq ... racle.html

The problem is being caused by TD 5.2 being installed the "Program Files (x86)" dir on the Windows 7 64 bit machine. Oracle doesn't like the "()".

The suggested fix is to insatall any applications in the "Program Files" dir. I've tried that twice and both times it ends up in in both dirs. Part of it installed in "Program Files" the rest in "Program Files (x86)" I told it to use the "Program Files" dir on the install. But something is forcing part of it to "Program File (x86)" dir.

Is there anyway to stop that????

The next fix is a possible patch to the Oracle 10GXE client.

In doing more research there are many 3th party apps having the same issue with the "()" as part of the directory name.

STOP THE PRESSES I FIXED IT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I tried reinstalling TD 5.2 in just the a UNIFY dir. That fixed it. I'm connected to XE throught SQLTalk and displaying tables fine. Now on to developing the applications

Thanks for all the help

Gary

[Jeff Luther]

YAY, success!! Thanks for letting us know Gary!