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 Converting Databases with Adabas Role-Based Security.
The sections below describe a conversion of databases without the security feature:
Converting Databases from Versions 6.1 Through Version 6.7.1 to Version 7.0 or 7.0.1
Converting Databases with Version 7.0 or 7.0.1 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.
There is no conversion necessary when moving from Adabas 7.0 to 7.0.1.
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.
If you want to upgrade a database from Version 6.1 through Version 6.7.1 to Version 7.0 or 7.0.1, 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 7.0 database;
Unload the old database using ADABCK DUMP or ADAORD EXPORT with the utilities supplied for the old database version;
Load the new database using ADABCK RESTORE or ADAORD IMPORT with version 7.0 or 7.0.1 utilities;
Convert the data using the utility ADACVT of version 7.0 or 7.0.1. This utility converts an existing database in place.
The utilities ADACVT, ADABCK and ADAORD make the following modifications:
The structure level in 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;
The AUTOSTART options in the ADABAS.INI file are adapted.
If you want to convert a database from Version 3 or Version 5, you must first upgrade the database to any of the versions Version 6.1 through 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. 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. If the database was encrypted, you can only use the second method.
You can use the utility ADACVT to convert a database to a previous version. ADACVT converts the database in place to the selected target version (Version 6.3 through Version 6.7.1). A downgrade is not possible if features introduced with Version 7.0 or 7.0.1 were used.
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.0 or 7.0.1 database back to Version 6.3 through 6.7.1 using the utility ADABCK. This is done by restoring a backup made with ADABCK Version 7.0 or 7.0.1 with the utility ADABCK of the respective target version. Unless the database is restored from scratch, ADABCK's version and the version of target database must coincide. However, this method is not applicable if features introduced with Version 7.0/7.0.1 and the target version (Version 6.7.1 or below) were used. A backup of an encrypted Version 7.0/7.0.1 database is restored to an older version without encryption.
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.
Collation descriptors created with ICU Version 5.4 are not processed correctly with Adabas Versions 6.3 to 6.4. Therefore, after the conversion to the target version with ADACVT/ADABCK, it is necessary to perform an ADAINV REINVERT of the collation descriptors with the ADAINV of the target version.
Without the REINVERT, you may get unexpected errors or incorrect results when you try to access the collation descriptors.
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.
This section describes how to convert a database when the Adabas role-based security feature is enabled:
Authentication for Adabas
Authorization for Adabas
The procedure to convert a database with Adabas role-based security is:
Create a backup of your existing database, as described above;
If the database had been encrypted, delete it and restore it from the backup taken in step 1 with the option ENCRYPTION=NO;
Modify the security configuration files;
Create a backup of your existing security definitions;
Convert the database using ADACVT;
Load your security definitions;
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.
If the Authentication feature is enabled for your database, please contact your nearest Adabas support center for a detailed description on how to proceed.
Perform the following steps if the Authorization for Adabas Utilities 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;
Use ADARBA to define your site-specific security definitions.
The location and layout of the audit trail log file created by Authentication has been modified, please refer to the Audit section of the document Adabas Role-Based Security.