Split the schema area to separate the application schema from the metaschema, sequences, and SQL statistics, making future major version metaschema upgrades to OpenEdge more transparent to the user.

Splitting the schema area to improve the database structure is typically a one-time exercise for the life of the database. Splitting reduces the size of the area, which is limited to the maximum area size of 256 GB. When the split is complete and the split application schema are subsequently moved to a Type II area, application data can benefit from all the database features and management operations that specifically cannot be done on the schema area, which is always a Type I storage area.

To split the schema area, run the Schema Mover utility (PROUTIL MVSCH). The Schema Mover truncates the schema area as follows:
  • Renames the current Schema Area to Old Default Area.
  • Creates a new Schema Area.
  • Moves the database metaschema, sequences, and SQL statistics from the old area into the new schema area.

For more information about moving application schemas, see Use the Schema Mover and PROUTIL MVSCH qualifier.