app-prev

Appendix 6 - Previous Version Owners Previous Chapter: Various API Users who have previously installed and used databases under Altera SQL Server have to make certain steps in order to retain their databases and port them under Ovrimos.
These steps are slightly tricky and the user is advised to follow all of them carefully, without making any shortcuts.
Promise! There will be no such difficulty in the future when upgrading from Ovrimos version 2.5 to later versions.

Win 32 Altera SQL Server upgrade

WARNING! DO NOT UNINSTALL ALTERA SQL SERVER! UNINSTALLING WILL DELETE REGISTRY DATA THAT WILL BE REQUIRED FOR THE PORTING OF EXISTING DATABASES.
DO NOT DELETE ANY FILES AND DIRECTORIES.

1. Use the Database Manager program to stop all running databases.

2. Use the Remove DBManager icon of the Altera Application Folder to uninstall the database manager. This will stop the database manager service and will remove the services from database testbase.

3. Install Ovrimos (as described in Installation in Win 32). This step will make make entries for Ovrimos Server and the new testbase in the Registry. If you do not wish to use the default application root path, do not use your previous path. Choose another directory name.

Note! Installation will create a new testbase database. Since the NT services for the previous testbase were previously running and it takes a while before the removal of the services is registered, users may have to postpone installation for a while. Otherwise, the new testbase may not be installed.

4. Use regedit to edit the Registry.
Go to HKEY_LOCAL_MACHINE\SOFTWARE\ALTERA\SQLSERVER\DATABASES.
For each database you wish to port to Ovrimos, open the pertinent key and use Export to write the key data to a file.

Now go to
HKEY_LOCAL_MACHINE\SOFTWARE\OVRIMOS\SQLSERVER\DATABASES.
For each database you wish to port, create a key and use Import to fetch the key data from the appropriate file.

5. You will have to note the values of SERIALNUM and LICENSE, which are written under HKEY_LOCAL_MACHINE\SOFTWARE\ALTERA\SQLSERVER
and assign them to respective keys under
HKEY_LOCAL_MACHINE\SOFTWARE\OVRIMOS\SQLSERVER.
You may decide to cut/paste these values.

6. You may have to do the same for the database manager password (or simply modify the password) from the database manager form.

7. If you have made additions in files mime.typ and init.scm you will have to cut and paste these modifications into the newly installed Ovrimos files.

8. At this point the databases' porting is almost complete. The old services for the databases must be removed. Go to the new application bin subdirectory and for each database (except testbase) type:
dbmcore <dbase> -remove
sqlcore <dbase> -remove

9. The new services for the databases must be installed.
For each database (except testbase) type:
dbmcore <dbase> -install
sqlcore <dbase> -install

10. Run the database manager.
For each of the ported databases go to Edit and update all parameters that appear to have value -1. These are new parameters added in version 2.5. For the meaning of these parameters see Per-database Parameters and the Database Manager.

Unix - Linux Altera SQL Server upgrade

DO NOT REMOVE ANY FILES OR DIRECTORIES. YOU WILL HAVE TO USE EXISTING INFORMATION PORT THE ALTERA DATABASES TO OVRIMOS.

1. Stop all running databases.

2. Kill the dbman running process.

3. Choose a new database installation root. Do not use the existing one.

4. Install Ovrimos (as described in Installation for Unix - Linux).

5. For each database you wish to port. go to the <dbase>.ini file and edit parameter GLOBAL (the dbman.ini file). Put the new dbman.ini path.

6. Open the old dbman.ini file and note LICENSE and SERIALNUMBER parameters. Copy these values to the new dbman.ini. You may decide to cut/paste these values.

7. You may have to do the same for the password or change the password from the database manager form.

8. If you have made additions in files mime.typ and init.scm you will have to cut and paste these modifications into the newly installed Ovrimos files.

9. Run the database manager.
For each of the ported databases go to Edit and update all parameters that appear to have value -1. These are new parameters added in version 2.5. For the meaning of these parameters see Per-database Parameters and the Database Manager.

Previous Chapter: Various API