| | |
| | | # |
| | | INFO_890_UPGRADE_1=With this upgrade, the Berkeley DB Java Edition JAR will be \ |
| | | upgraded to version 3.2.13 which introduces incompatibilities to the data \ |
| | | format. Consequently if at a later time you wish to revert this installation \ |
| | | format. Consequently if at a later time you wish to revert this installation \ |
| | | to its prior version you will have to export the data from this server and \ |
| | | reimport it once the reversion has finished |
| | | INFO_890_REVERSION_2=With this reversion, the Berkeley DB Java Edition JAR \ |
| | | will be downgraded to an older version which uses a different data format \ |
| | | than the current version. In order to revert this server you will have to \ |
| | | than the current version. In order to revert this server you will have to \ |
| | | export the data from this server and reimport it after the reversion has \ |
| | | finished |
| | | INFO_1582_UPGRADE_3=This upgrade introduces improvements to the data format \ |
| | | which are not backward compatible with the current version. Consequently if \ |
| | | which are not backward compatible with the current version. Consequently if \ |
| | | at a later time you wish to revert this installation to its prior version you \ |
| | | will have to export the data from this server and reimport it once the \ |
| | | reversion has finished |
| | | INFO_1582_REVERSION_4=With this reversion the data format used to store data \ |
| | | by the server will be reverted to a prior version. In order to revert this \ |
| | | by the server will be reverted to a prior version. In order to revert this \ |
| | | server you will have to export the data from this server and reimport it \ |
| | | after the reversion has finished |
| | | INFO_2049_UPGRADE_5=This upgrade introduces improvements to the data format \ |
| | | which are not backward compatible with the current version. Consequently if \ |
| | | which are not backward compatible with the current version. Consequently if \ |
| | | at a later time you wish to revert this installation to its prior version you \ |
| | | will have to export the data from this server and reimport it once the \ |
| | | reversion has finished |
| | | INFO_2049_REVERSION_6=With this reversion the data format used to store data \ |
| | | by the server will be reverted to a prior version. In order to revert this \ |
| | | by the server will be reverted to a prior version. In order to revert this \ |
| | | server you will have to export the data from this server and reimport it \ |
| | | after the reversion has finished |
| | | INFO_2974_UPGRADE_7=This upgrade introduces an incompatible property change \ |
| | | for the default password storage scheme and deprecated password storage \ |
| | | schemes associated with a password policy. The schemes are now referenced \ |
| | | by DN rather than by name. Upgrade is not possible because the scheme name \ |
| | | schemes associated with a password policy. The schemes are now referenced \ |
| | | by DN rather than by name. Upgrade is not possible because the scheme name \ |
| | | cannot be automatically translated into a DN |
| | | INFO_2974_REVERSION_8=It is not possible to revert to a revision before 2974 \ |
| | | because the default password storage scheme and deprecated password storage \ |
| | | scheme references in the password policy have been converted from names to \ |
| | | DNs, and it is not possible to revert from the DN back to the scheme name |
| | | INFO_3294_UPGRADE_9=This upgrade introduces a new security framework that is \ |
| | | not backwards compatible. Upgrade is not possible |
| | | INFO_3294_REVERSION_10=The revision 3294 introduces a new security framework. \ |
| | | not backwards compatible. Upgrade is not possible |
| | | INFO_3294_REVERSION_10=The revision 3294 introduces a new security framework. \ |
| | | Revert is not possible |
| | | INFO_3708_UPGRADE_11=This upgrade introduces a change in the backend \ |
| | | configuration that is not backwards compatible. Upgrade is not possible |
| | | configuration that is not backwards compatible. Upgrade is not possible |
| | | INFO_3708_REVERSION_12=The revision 3294 introduces a change in the backend \ |
| | | configuration. Revert is not possible |
| | | configuration. Revert is not possible |
| | | INFO_3873_UPGRADE_13=This change introduces a change to the way in which \ |
| | | distinguished names are normalized. In order to upgrade this server you \ |
| | | distinguished names are normalized. In order to upgrade this server you \ |
| | | will have to export the data from this server and reimport it after the \ |
| | | upgrade has finished |
| | | INFO_3873_REVERSION_14=With this reversion the normalized form of \ |
| | | distinguished names will be reverted to a prior version. In order to \ |
| | | distinguished names will be reverted to a prior version. In order to \ |
| | | revert this server you will have to export the data from this server and \ |
| | | reimport it after the reversion has finished |
| | | INFO_5134_UPGRADE_15=The revision 5134 introduces a change to the \ |
| | |
| | | In order to upgrade this server you will have to export the data from \ |
| | | this server and reimport it after the upgrade has finished |
| | | INFO_5134_REVERSION_16=With this reversion the normalization of attribute \ |
| | | or assertion value will be reverted to a prior version. In order to revert this server \ |
| | | or assertion value will be reverted to a prior version. In order to revert this server \ |
| | | you will have to export the data from this server and reimport it after the \ |
| | | reversion has finished |
| | | INFO_5278_REVERSION_17=Reversion from version 2.0 to a previous version is \ |