Kbase P123167: Can a 10.1B or 10.1C database be reverted to 10.1A database version?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/12/2011 |
|
Status: Verified
GOAL:
How to convert a 10.1B database to 10.1A version?
GOAL:
How to convert a 10.1C database to 10.1A version?
GOAL:
Why can't a 10.1B database be reverted to a 10.1A database?
GOAL:
Why can't a 10.1C database be reverted to a 10.1A database?
GOAL:
Why can't a 10.1B database be converted back to a 10.1A without a dump and load?
GOAL:
Why can't a 10.1C database be converted back to a 10.1A without a dump and load?
GOAL:
What is the PROUTIL REVERT utility?
GOAL:
How to use revert utility?
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.1B
OpenEdge 10.1C
FIX:
Reverting an OpenEdge 10.1B or 10.1C database to a 10.1A database.
Due to the limited interoperability between databases from Release 10.1A and Release 10.1B or 10.1C, the PROUTIL REVERT utility is available to revert the format of a 10.1B /C database to a 10.1A format, for databases that meet certain criteria.
The PROUTIL REVERT utility will analyze the existing offline 10.1B database and determine if it meets the conditions for reversion.
PROUTIL REVERT cannot revert a database if any of the following conditions exist:
? The database was created with Release 10.1B or 10.1C.
? The schema contains any INT64 fields.
? The database has enabled support for large key entries for indexes.
? The database has enabled support for 64-bit sequences.
? The database has a Type II area with a high water mark utilizing 64-bit DB Keys, this includes a LOB with segments utilizing 64-bit block values.
? The database has area numbers greater than 1000.
You can run proutil dbname -C describe to see a list of features present in the database.
If PROUTIL REVERT cannot revert the database, a dump and load of the database will have to be considered, after removing or restructuring any aspects of the database that cannot be reverted.
Please refer to ?Reverting your database manually? section on page 1?20 of the OpenEdge® Data Management documentation for more information.
Caution: PROUTIL REVERT is a non-recoverable utility. If PROUTIL REVERT terminates abnormally, the database must be restored from backup.
STEPS:
Use utility and environment that matches the version of the database, ie: 10.1B or 10.1C.
Take a full valid backup of the database before proceeding.
The syntax of PROUTIL REVERT command is as follows:
$ proutil db-name -C revert
PROUTIL REVERT executes against an offline database as follows:
1. Determines that the user has sufficient privilege to execute the command. The privilege check is limited to file system access to the database.
2. Analyzes the enabled features of the database to determine if the database can be reverted by the utility.
Should any of the criteria not be met, the utility issues messages indicating why the database cannot be reverted, and exits.
The following sample output is from an attempt to revert a database that does not meet the reversion requirements and it will return to the command prompt unchanged:
Revert Utility
---------------------
Feature Enabled Active
-------------------------------- ------- ------
64 Bit DBKEYS Yes Yes
Large Keys Yes Yes
64 Bit Sequences Yes Yes
Revert: The database actively supports Large Key Indexes. (13749)
Revert: The database can not be reverted. (13750)
Revert: The database contains 64-bit Sequences. (13751)
Revert: The database can not be reverted. (13750)
3. Prompts the user to confirm that the database has been backed up.
4. Performs the physical fixes necessary to revert the database. Fixes include the following:
? Reverting values in the database master block to 10.1A format.
? Reverting object block values to 10.1A format.
? Removing 10.1B / 10.1C VSTs and addin.g the 10.1A VSTs.
? Removing all 10.1B / 10.1C settings from the feature mask.
5. Disables 2-Phase commit, JTA, Replication, After-imaging, and AI Management, if active.
6. Truncates the BI file..