Page 1 of 1

Oracle Connection settings TD 6.3.sp1

PostPosted: Tue Jul 05, 2016 11:52 am
by mlachlan
Good afternon,
I'm using GUPTA since 1991 also later CENTURA).
The I stopped and now I'm back to perform a PoC for a customer using the latest Trial Version of TD and SqlBase.
Now I'm not able anymore to connect either to an Oracle nor a SQLServer DB.
It seems there has a lot changed over the last 15 years.

Im using an Oracle 11g 64bit DB and SQLServer 2014 also 64bit.
can someone get me how the SQL.ini file has to look like with this Versions ?

This is how my current SQL.ini Looks like:
; Unify Corporation 2008
; SQLBase INItialization file

; Win32 (Windows 2000, XP and Vista)
; This section is for the SQLBase Win32 database server. You can
; specify which communication protocol(s) the server can use as well as which
; protocol(s) a database can use.


; The default value for readonly is 1, which allows use of "read only" and
; "read committed" (RO and RC) isolation levels. Uncommenting "readonly=0"
; will disallow use of RO and RC isolation levels.

; To get process logging, specify a log file and display level.

; SQLBase supports communicating through named pipes. Named pipes
; support Windows network authentication and allows a client running
; on the same machine to find a server without explicit configuration
; Options are:
; namedpipes=No ; 0 - Named pipes not enabled
; namedpipes=Yes ; 1 - Named pipes are enabled for local and remote access
; namedpipes=LocalOnly ; 2 - Named pipes are enabled for local access only. Remote access is denied
dbdir=C:\ProgramData\Gupta\Team Developer 6.3\sqlbase
tempdir=C:\ProgramData\Gupta\Team Developer 6.3\sqlbase

; The USECLIENTCOUNTRY setting is used to require the client
; COUNTRY configuration setting to match what is being used on the server.
; 0 - Server assumes client COUNTRY setting is compatible with the
; one the server is using. The client no longer needs to specify
; the COUNTRY configuration parameter when the server has it set.
; However, the client should be using the same character set as
; the server.
; 1 - Client COUNTRY= setting must match what the server is using
; The default value is 0, COUNTRY setting not required





; Win32 (Windows 2000, XP and Vista)
; 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
; sqlws32 REMOTE database using TCP/IP (WinSock)

; On 11.7 and above, if the CLIENTNAME is not specified, the computername
; will be displayed on the server. Also, the CLIENTNAME is not limited to 12 characters.
; The transports option overrides the [win32client.dll] section.
; Possible values for transports are
; npipe,tcpv4,tcpv6,apipe

clientruntimedir="C:\Program Files (x86)\Gupta\Team Developer 6.3\sqlbase"

; The [win32client.dll] used to have a list of communication .dll's
; to use for communication. Communication .dll's have been removed.
; This section is read and interpreted to be backwards compatibible.
; The transports parameter now supersedes it.

autostartserverpath="C:\Program Files (x86)\Gupta\Team Developer 6.3\sqlbase\dbntsrv.exe"

comdll=sqlodb32;alias=SqlServer ODBC AX;dbname=AX_NAME_TEST_MMN
comdll=sqlodb32;alias=SqlServer ODBC NAME;dbname=NAME_Test


Please could someone reply ?


Re: Oracle Connection settings TD 6.3.sp1

PostPosted: Wed Jul 06, 2016 1:27 am
by frevelundfey
Hi Michael,

you can have 64Bit Oracle Server - but you have to use 32-Bit Oracle-Client!
You also have to configure ODBC32 Bit for sqlserver
(look for it here c:\windows\syswow64\odbcad32.exe).

Regards Thomas