Migrating from Sqlbase 7.6.0 to Sqlbase 11.7

Discussion forum about all things SqlBase.
chrisocm
Malaysia
Posts: 71
Joined: 12 May 2017, 16:07
Location: Kuala Lumpur

Migrating from Sqlbase 7.6.0 to Sqlbase 11.7

Post by chrisocm » 07 Mar 2014, 14:16

Hi all,

I've some questions regarding the topic above;

1) What needs to be done for the migration?
2) Can Sqlbase 11.7 runs on Windows XP - 32 bit machine?
3) Is report builder 2.1 compatible with 11.7

Thanks a lot.

Chris

Mike Vandine

Re: Migrating from Sqlbase 7.6.0 to Sqlbase 11.7

Post by Mike Vandine » 10 Mar 2014, 01:08

Hi Chris,

For the conversion, the easiest thing is just to unload the database on the 7.6 server (creates a text file of the whole database) and then load that data into a new database on the 11.7 version. Here is a script to use:

On the 7.6.0 server, using SQLTalk:

CONNECT databasename SYSADM/sysadmpassword;
UNLOAD DATABASE databasename.SQL ON SERVER;
EXIT;

Take the databasename.SQL file to the new server.

SET SERVER servername/serverpassword;
CREATE DATABASE databasename;
SET SERVER OFF;
CONNECT databasename SYSADM/SYSADM;
SET RECOVERY OFF;
SET ERRORLEVEL 3;
LOCK DATABASE;
LOAD SQL databasename.SQL ON SERVER LOG databasename.LOG;
COMMIT;
UPDATE STATISTICS ON DATABASE;
UNLOCK DATABASE;
SET RECOVERY ON;
EXIT;

Yes, SQLBase 11.7 can be run on an XP machine, but I would highly recommend that you upgrade to something a bit newer.

Yes, all versions of Report Builder are compatible with 11.7.

Best regards,

Mike

chrisocm
Malaysia
Posts: 71
Joined: 12 May 2017, 16:07
Location: Kuala Lumpur

Re: Migrating from Sqlbase 7.6.0 to Sqlbase 11.7

Post by chrisocm » 28 Mar 2014, 07:35

Thanks Mike for the info.

chrisocm
Malaysia
Posts: 71
Joined: 12 May 2017, 16:07
Location: Kuala Lumpur

Re: Migrating from Sqlbase 7.6.0 to Sqlbase 11.7

Post by chrisocm » 03 Mar 2015, 12:18

Hi Mike,

Would like to ask for your expert opinion. I'll be installing Sqlbase 11.7 on my client's server this Sunday. Do I need to install on the other PCs (workstation)? The other PCs are already running the runtime of Sqlbase 7.60. Your help is much appreciated.

Chris

Mike Vandine

Re: Migrating from Sqlbase 7.6.0 to Sqlbase 11.7

Post by Mike Vandine » 03 Mar 2015, 23:58

Hi Chris,

Yes, you should install the SQLBase client of 11.7 on the PCs.

Best regards,

chrisocm
Malaysia
Posts: 71
Joined: 12 May 2017, 16:07
Location: Kuala Lumpur

Re: Migrating from Sqlbase 7.6.0 to Sqlbase 11.7

Post by chrisocm » 05 Mar 2015, 14:26

Hi Mike,

Thanks for the info. :wink:

Regards,
Chris

chrisocm
Malaysia
Posts: 71
Joined: 12 May 2017, 16:07
Location: Kuala Lumpur

Re: Migrating from Sqlbase 7.6.0 to Sqlbase 11.7

Post by chrisocm » 09 Mar 2015, 09:40

Hi Mike,

I managed to successfully install SQLbase 11.7 and the database on my client's server. I noticed in the SQLBASE 117 folder, the is no cfgwi10.exe or sqlconfig.exe for me to set the path of the database and so on. Another thing is, the main menu (my software developed using CTD 1.1.2) does not run on the server. It gives me an error 3703. But on the workstations, the menu works fine. Below is the server sql.ini file.

;
; 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.

[dbntsrv]
;dbname=ISLAND
;dbname=SBTASK
ANSIJoinSyntax=1
centurydefaultmode=1

; 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.
;readonly=0

; To get process logging, specify a log file and display level.
;log=c:\dbsrv.log
;displevel=4

;
; 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
;
NamedPipes=LocalOnly
servername=Server1
Password=GN3M7GR2
autolocktable=0
batchpriority=0
cache=64000
dbdir=d:\Database
tempdir=C:\ProgramData\Gupta\SQLBase11764B

;
; 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
;
; USECLIENTCOUNTRY=0

DBNAME=STEELBIZ
[dbntsrv.gui]

[dbntsrv.dll]
comdll=sqlws32
;comdll=sqlapipe

[dbntsrv.apipe]

[dbntsrv.ws32]
ListenPort=2155

; 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)

[win32client]
; 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.
clientname=Win32User

; The transports option overrides the [win32client.dll] section.
; Possible values for transports are
;
; npipe,tcpv4,tcpv6,apipe
transports=npipe,tcp,apipe
clientruntimedir=C:\Program Files\Gupta\SQLBase117

;
; 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.
;
;[win32client.dll]
;comdll=sqlws32
;comdll=sqlapipe

[win32client.npipe]

[win32client.apipe]
autostartserverpath="C:\Program Files\Gupta\SQLBase117\dbntsrv.exe"
serverpath=Server1

[win32client.ws32]
serverpath=Server1,localhost/steelbiz

Your assistance and expert opinion is much appreciated.

Regards,
Chris
Last edited by Anonymous on 09 Mar 2015, 09:42, edited 1 time in total.

Mike Vandine

Re: Migrating from Sqlbase 7.6.0 to Sqlbase 11.7

Post by Mike Vandine » 10 Mar 2015, 04:56

Hi Chris,

The 3707 error probably means that the runtime of your Menu isn't picking up the right sql.ini file. Try this to see:

In the server's sql.ini ifile, put in a known error:

[win32client]
xxx=xxx

Now try to run your application. Do you get an error about an invalid configuration entry? If not, then you are picking up a different sql.ini file.

Best regards,

Mike

chrisocm
Malaysia
Posts: 71
Joined: 12 May 2017, 16:07
Location: Kuala Lumpur

Re: Migrating from Sqlbase 7.6.0 to Sqlbase 11.7

Post by chrisocm » 11 Mar 2015, 10:47

Hi Mike,

Tried that and it's reading that sql.ini. After removing the xxxx=xxxx, the system now gives me error "INCOMPATIBLE ERROR.SQL FOUND LOOKING UP ERROR 03703"

PATH is set as c:\Program Files\Gupta\SQLBase117\

Any ideas?

Regards,
Chris

Mike Vandine

Re: Migrating from Sqlbase 7.6.0 to Sqlbase 11.7

Post by Mike Vandine » 16 Mar 2015, 05:20

Hmmmm. Something else must have changed. Just removing that line that you put in shouldn't give you a different error.

What it is saying now is that the error.sql file that it is picking up to display the error isn't the right version. I suspect it may be picking up the one from your 7.6.0 installation.

Try renaming ALL error.sql files on your system and see if it tells you that it can't find an error.sql file. Something isn't quite right about your setup...

Best regards,

chrisocm
Malaysia
Posts: 71
Joined: 12 May 2017, 16:07
Location: Kuala Lumpur

Re: Migrating from Sqlbase 7.6.0 to Sqlbase 11.7

Post by chrisocm » 19 Mar 2015, 03:18

Hi Mike,

FYI, this is a fresh installation on a new IBM server running Windows server 2012R. I'll try your method and will keep you posted. Thanks

Regards,
Chris

chrisocm
Malaysia
Posts: 71
Joined: 12 May 2017, 16:07
Location: Kuala Lumpur

Re: Migrating from Sqlbase 7.6.0 to Sqlbase 11.7

Post by chrisocm » 19 Mar 2015, 03:19

Another thing Mike, the error has been all this while 03703 and not 03707.

chrisocm
Malaysia
Posts: 71
Joined: 12 May 2017, 16:07
Location: Kuala Lumpur

Re: Migrating from Sqlbase 7.6.0 to Sqlbase 11.7

Post by chrisocm » 22 Mar 2015, 05:16

I tried renaming the error.sql file and the system can't find the file when I ran the program. It's reading the correct error.sql (C:\Program Files\Gupta\SQLBase117\). BTW, the first line of the error.sql file is "1.0.0 SQLBase Errors Guide". Is this the correct version? I'm attaching the sql.ini file below. Have missed out something?

;
; 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.

[dbntsrv]
;dbname=ISLAND
;dbname=SBTASK
ANSIJoinSyntax=1
centurydefaultmode=1

; 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.
;readonly=0

; To get process logging, specify a log file and display level.
;log=c:\dbsrv.log
;displevel=4

;
; 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
;
NamedPipes=LocalOnly
servername=Server1
Password=GN3M7GR2
autolocktable=0
batchpriority=0
cache=64000
dbdir=d:\Database
tempdir=C:\ProgramData\Gupta\SQLBase11764B

;
; 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
;
; USECLIENTCOUNTRY=0

DBNAME=STEELBIZ
[dbntsrv.gui]

[dbntsrv.dll]
comdll=sqlws32
;comdll=sqlapipe

[dbntsrv.apipe]

[dbntsrv.ws32]
ListenPort=2155

; 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)

[win32client]
;xxxx=xxxx
; 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.
clientname=Win32User

; The transports option overrides the [win32client.dll] section.
; Possible values for transports are
;
; npipe,tcpv4,tcpv6,apipe
;transports=npipe,tcp,apipe
;clientruntimedir=C:\Program Files\Gupta\SQLBase117

;
; 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.
;
;[win32client.dll]
;comdll=sqlws32
;comdll=sqlapipe

[win32client.npipe]

[win32client.apipe]
autostartserverpath="C:\Program Files\Gupta\SQLBase117\dbntsrv.exe"
serverpath=Server1

[win32client.ws32]
serverpath=Server1,localhost/steelbiz

Mike Vandine

Re: Migrating from Sqlbase 7.6.0 to Sqlbase 11.7

Post by Mike Vandine » 23 Mar 2015, 05:04

Hi Chris,

Well, I've stripped out all the 'unnecessary' bits (commented out and not used) and added a few bits that were missing. Save the old copy (just in case) and replace with this one:

-------------
[dbntsrv]
ANSIJoinSyntax=1
centurydefaultmode=1
NamedPipes=No
servername=Server1
Password=GN3M7GR2
autolocktable=0
batchpriority=0
cache=64000
dbdir=d:\Database
tempdir=C:\ProgramData\Gupta\SQLBase11764B
DBNAME=STEELBIZ

[dbntsrv.gui]

[dbntsrv.dll]
comdll=sqlws32

[dbntsrv.ws32]
ListenPort=2155

[win32client]
clientname=Win32User
transports=tcp,npipe
clientruntimedir=C:\Program Files\Gupta\SQLBase117

[win32client.dll]
comdll=sqlws32

[win32client.ws32]
serverpath=Server1,localhost/steelbiz
-------------
Note that we're forcing a TDP connection with the namedpipes=no, transports=tcp,npipe. Probably the two biggest bits were the missing transports= statement and the clientruntimedir=, both commented out in your version.

Best regards,

chrisocm
Malaysia
Posts: 71
Joined: 12 May 2017, 16:07
Location: Kuala Lumpur

Re: Migrating from Sqlbase 7.6.0 to Sqlbase 11.7

Post by chrisocm » 27 Mar 2015, 14:20

Hi Mike,

I replaced the original sql.ini file with the one given by you and this is the error message

WIN32CLIENT: error found in file c:\Program Files\Gupta\SQLBase117\SQL.INI at line 24
WIN32CLIENT: section [win32client]
WIN32CLIENT: transport=tcp,npipe
WIN32CLIENT: invalid keyword

when I remarked this line, the error goes to line 25, same sort of error message.

I'm baffled. :?

Return to “General Discussion”

Who is online

Users browsing this forum: [Ccbot] and 0 guests