The general steps taken by the driver for the map migration from 8.0 to 8.1 are as follows.

1. Create a config file using the existing 8.0 config file name as a starting point and add "-3" to the file name.
2. Use this new file to migrate the original 8.0 config file contents to the 8.1 format in the "-3" file.
3. If the config file migration is successful, rename the 8.0 config file to a file with "-2" in the name and then remove the "-3" from the migrated file name so that it is now using the original file 8.0 file name. The config file has now been replaced by the 8.1 version.
4. Create a native file using the existing 8.0 native file name as a starting point and add "-12" to the file name.
5. Use this new file to migrate the original 8.0 native file contents to the 8.1 format in the "-12" file.
6. If the native file migration is successful, rename the 8.0 native file to a file with "-2" in the name and then remove the "-3" from the migrated file name so that it is now using the original 8.0 file name. The native file has now been replaced by the 8.1 version.

At this point the map migration is complete. Here are the steps to revert the map files back to the 8.0 format based on failures that could occur at different points in the process.

Manually reverting after a failed migration

An existing directory with 8.0 schema files:



Failure Type #1 - .config fails to migrate

The .config file is migrated first. If that migration doesn't complete you will end up with an extraneous artifact of the failed migration (the <original>.config with the name <original>-3.config. The existence of this file doesn't affect the 8.0 driver but should be removed if you want to attempt another migration.



Failure Type #2 - .native fails to migrate

If the .config migrated successfully but the .native file did not we can end up in this state. In this case the <original>-12.native can be deleted. The <original>.config can also be deleted as it is the migrated config file. We'll also need to rename <original>-2.config back to <original>.config. Now the 8.0 driver can be used.



Failure Type #3 - migrated map fails to load

The migration step can succeed but the 8.1 driver might encounter an issue when trying to actually load/use the migrated map. This often results in the "general error" during an 8.1 connection attempt. In this scenario the original 8.0 .config and .native file will exist in the directory with the names <original>-2.config and <original>-11.native.

In this case everything can be deleted from the directory except for the files <original>-2.config and <original>-11.native. Those files should be renamed to remove the -2 and -11 suffix. At this point you can resume using the 8.0 driver and open a support ticket for assistance with migrating this 8.0 map to the 8.1 format.