This section describes how to convert an existing database from one version to another.
When the Adabas Role-Based Security feature is enabled, proceed with the steps described in the section Upgrading Databases with Adabas Role-Based Security.
The sections below describe a conversion of databases without the security feature:
Modify the Security Configuration Files (Version 6.7.1 and above)
Upgrading Databases from Versions 6.7.1 through 7.0.1 and 7.1.1 to Version 7.2
Downgrading Databases with Version 7.2 to a Previous Version
The following procedural steps are highly recommended when converting a database:
Create a backup of your existing database.
Use the old version of ADABCK to backup the whole database.
Modify the security configuration files.
Convert the version of the database by performing the steps described below.
Validate the consistency of the database.
Use the FIELD and INDEX functions of the ADAVFY utility to validate the consistency of the database.
The following settings in the security configuration file adaauth.ini are mandatory:
ACTION=YES MODE=ADABAS
Please refer to the section Configuration of Adabas Role-Based Security for further information on the file location and content.
A database running a version prior to version 7.2 can be upgraded in several ways. The easiest and recommended way is to convert it in place by running ADACVT. If Adabas Role-Based Security is enabled, refer to the section Upgrading Databases with Adabas Role-based Security enabled.
You can also convert a database from an older version to Version 7.2 using the utility ADABCK. This is done by restoring a backup made with ADABCK of the older version and restoring it with ADABCK Version 7.2. ADABCK will make the necessary changes during the restore operation.
The internal structure of the database has changed. Therefore you must first delete the database in the target environment – then you can restore the database.
If the source database had been encrypted, the key management system used must provide the appropriate keys. For details refer to the section Adabas Encryption for Linux.
If you want to convert a database from Version 3 or Version 5, you must first upgrade the database to Version 6.7.1, as described in the Release Notes of the version-specific documentation, and then proceed as described above.
Two options are available to go back to a previous version. After having verified the security configuration files, you can either convert a database in place to a previous version, or you can make a backup of the database and restore it (to a different place). When the Adabas Role-Based Security feature is enabled, a downgrade to a version prior to 6.7.1 is not supported.
The following settings in the security configuration file adaauth.ini are mandatory:
ACTION=YES MODE=ADABAS
Please refer to the section Configuration of Adabas Role-Based Security for further information on the file location and content.
You can use the utility ADACVT to convert a database to a previous version. This is the recommended method. ADACVT converts the database in place to the selected target version. A downgrade is not possible if features introduced with a more recent version than the target version were used. This method is not applicable if the encrypted source database is to be decrypted – in this case proceed as described in the section Alternative Method to Convert from Version 7.2 to an older Version.
Please bear in mind that ADATCP is available since Version 6.7.1. Going back to an older version might imply changes in your infrastructure if ADATCP is in use.
It is also possible to convert a Version 7.2 database back to an older version using the utility ADABCK. This is done by restoring a backup made with ADABCK Version 7.2 with the utility ADABCK of the respective target version.
The internal structure of the database has changed. Therefore you must first delete the database in the target environment before you restore the database. However, this method is not applicable if features introduced in more recent versions than the target version were used. It is not recommended either, if the Adabas Role-Based Security feature is used.
Versions 6.7.1 and below do not support encryption; the encrypted database must first be decrypted. A backup of an encrypted database can be restored to an older version without encryption in a similar way. For this purpose, first run the restore operation with option ENCRYPTION=NO. The backup taken from the decrypted database can be used to restore the database for use in a previous version.
If the source database had been encrypted, the key management system used must provide the appropriate keys. For details refer to the section Adabas Encryption for Linux.
Please bear in mind that ADATCP is available since Version 6.7.1. Going back to an older version might imply changes in your infrastructure if ADATCP is in use.
This section describes how to convert a database when the Adabas role-based security feature is enabled. Note that a conversion is only supported for Adabas version 6.7.1 and above.
The procedure to convert a database with Adabas role-based security is:
Create a backup of your existing database, as described above;
Modify the security configuration files;
Convert the database using ADACVT;
Validate the consistency of the database, as described above.
The following settings in the security configuration file adaauth.ini are mandatory:
ACTION= YES MODE=ADABAS
Please refer to the section Configuration of Adabas Role-Based Security for further information on the file location and content.
Perform the following steps if the Authorization feature is enabled for your database:
Save the security definitions that are stored in the security configuration file adarbac.ini;
Use ADADBM RBAC_FILE to load the RBAC system file;
Use ADACVT to convert the database;
Use ADARBA to define your site-specific security definitions that are defined in the file adarbac.ini.
Save the security definitions that are stored in the RBAC system file;
Use ADACVT to convert the database;
The location and layout of the audit trail log file created by Authentication has been modified, please refer to the Audit Trail section of the document Adabas Role-Based Security.