This section is intended to assist a user upgrading to Adabas 6.6 from an older version of Adabas.
On Windows platforms, the default installation directory is C:\SoftwareAG and the default Start Menu Group name is Software AG.
If the same Adabas version is to be installed more than once, or if several different versions are to be installed on the same machine, each version or instance must be installed in a separate directory (under Windows also a separate Start Menu Group).
It will not possible to install more than one Adabas version into the same directory. You cannot overwrite an existing version, you can only uninstall it.
For further information see the section Important Information and follow the instructions in the section Installing Adabas.
Adabas 6.6 requires that every Adabas installation is licensed separately.
Follow the instructions in the section Completing the Installation to complete the installation and to activate the license.
If you have Adabas Version 6.3 or earlier installed:
Terminate your active databases.
Unset the global Adabas environment.
Activate the current installation via the menu under: .
Follow the instructions in the section Completing the Installation to verify the installation.
The environment variable ADADATADIR identifies the directory in which the databases are located; e.g. the dbnnn directories, where nnn is the three digit database number.
By default, ADADATADIR is the Program Data directory: %PROGRAMDATA%\Software AG\Adabas.
If your databases are allocated in the default location %PROGRAMDATA%\Software AG\Adabas, no additional configuration is required.
You can change the value of ADADATADIR for the current installation by running change_adadatadir.bat from an appropriate command prompt.
To run change_adadatadir.bat
Shut down all processes that are using the current installation.
Deactivate your installation with
Start Menu > All Programs > Start Menu group name > Administration > Adabas 6.6 > Deactivate Installation
Open a command prompt with
Start Menu > All Programs > Start Menu group name > Administration > Adabas 6.6 > Start Command Prompt
and then run change_adadatadir.bat.
Close all open command prompts.
Reactivate your installation to pick up the new value for ADADATADIR with
Start Menu > All Programs> Start Menu group name > Administration > Adabas 6.6 > Activate Installation
Note:
Although ADADATADIR can be different for each installation of
Adabas, the database numbers must be unique in your Windows environment.
If you want to upgrade a database from Version 6.1, 6.2, 6.3, 6.4 to or 6.5 to Version 6.6, there are two options available to you:
Convert the data using either the utility ADABCK or ADAORD. This option requires that you:
Create a new Version 6.6 database;
Unload the old database using ADABCK DUMP or ADAORD EXPORT (old version);
Load the new database using ADABCK RESTORE or ADAORD IMPORT (version 6.6).
Convert the data using the utility ADACVT (for further information see Utilities Manual). This utility converts an existing database in place.
If you want to upgrade a database from Version 5, you must first upgrade the database to Version 6.1, 6.2, 6.3, 6.4 or 6.5 (as described in the Release Notes of the version-specific documentation) and then proceed as described above.
The utilities ADACVT, ADABCK and ADAORD make the following modifications:
The structure level of the General Control Block (GCB) is increased;
The structure of the FDT is changed, when a Version 6.1 database is converted;
Databases are included in the ADABAS.INI file, when a DBxxx.INI file exists;
Important:
Software AG strongly recommends that you perform the
following actions: before converting a database, use ADABCK to dump the
database, then after a database has been converted, use the ADAVFY FIELD and
INDEX functions to verify the consistency of the database.
If you want to convert a database from Version 5, you must first upgrade the database to Version 6.1, 6.2, 6.3 or 6.4, as described in the Release Notes of the version-specific documentation, and then proceed as described above.
If your database is to be started automatically when the Adabas Database Service starts, the AUTOSTART value needs to be adapted to the new Adabas version. Execute
ADASRV Set <dbid> AUTOSTART=Vnnnnn
where nnnnn is the Adabas version (1st digit = major version, 2nd digit = minor version, 3rd digit = service pack, 4th - 5th digit = fix number).
AUTOSTART=V66000
This means major version = 6, minor version = 6, service pack = 0, fix = 00.
For further information see Adabas Services on Windows.
You have got two options to convert a Version 6.6 database back to a previous version, provided new features introduced with Adabas Version 6.6 were not used.
Use the utility ADACVT to convert a database to a previous version. The database will be converted in place.
Alternatively you can convert a database using ADABCK. To achieve this, make a backup with ADABCK Version 6.6 and restore the database with the appropriate version of ADABCK.
Care should be taken if collation descriptors were used. As collation descriptors created with ICU version 5.4 are not processed correctly with Adabas Version 6.3 and Adabas Version 6.4, you must reinvert those descriptors.
When you start the Adabas nucleus, and the runtime requirements of a user exit or hyperexit differ to those of the nucleus, a message similar to the following will be recieved:
MSVCRxxx.dll is missing or cannot be found.
Microsoft recommends that the manifest file be embedded in the C/C++ application in order to ensure that the correct runtime is used, and thus avoid such issues.
Please refer to the following Microsoft documentation topics for further details about how to do this:
How to: Embed a Manifest Inside a C/C++ Application
Isolated Applications and Side-by-side Assemblies