This section is intended to assist a user upgrading from an older version of Adabas to the current version.
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 is 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 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 Start menu under: .
Note:
In the above description n.n
represents the current version of Adabas: the 1st digit denotes the major
version, the 2nd digit – the minor version.
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
> All Programs > Start Menu group name > Administration > Adabas n.n > Deactivate Installation
Open a command prompt with
> All Programs > Start Menu group name > Administration > Adabas n.n > 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
> All Programs> Start Menu group name > Administration > Adabas n.n > Activate Installation
Notes:
After installing Adabas, the databases to be used need to be prepared for use with this version. Several options to convert those databases are described in the Release Notes. The conversion back to a previous version is also described there.
Before a database is converted to a different version, you are strongly recommended to make a backup of that database with utilities provided for the version of the database, and, following successful conversion, to run ADAVFY’s FIELD and INDEX functions to check the consistency of the database.
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=Vnnn00
where nnn is the Adabas version (1st digit = major version, 2nd digit = minor version, 3rd digit = service pack, 4th - 5th digit are always zero).
AUTOSTART=V67000
This means major version = 6, minor version = 7, service pack = 0, fix = 00.
AUTOSTART=V70000
This means major version = 7, minor version = 0, service pack = 0, fix = 00.
For further information see Adabas Services on Windows.
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