Kbase P23461: How to avoid the bi 2 GB limit when doing a Fast Schema Change
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/3/2009 |
|
Status: Verified
GOAL:
How to avoid the bi 2 GB limit when doing a Fast Schema Change
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
FIX:
Fast Schema Change was first introduced in version 8.2A.
It is documented in the Progress 8.2A System Administration Guide Chapter 4, Section 4-5 Changing the Database Schema, page 4-13. This is the default for Progress version 8.2A+.
It can be turned off by specifying -populate, see System Administration Reference page 4-87.
By following the steps outlined in the Progress Admin. Guide book the schema change will happen faster and take less .bi file space. This is so when adding a field or fields to a table. The field or fields will be added when the record is updated or added instead of when the schema change is applied. These fields have to defined as an unknown value to take advantage of a fast schema change. The Progress Admin Guide book goes on to explain how to use fast schema change and
later update the field if an initial value is required.
This new feature may help get around the 2 GIG .bi file limitation. When updating the schema to add field(s) to a large database (1 GIG+), very often
the .bi file could hit 2 GIG. If this occurs one or both of the following errors may be received:
SYSTEM ERROR: rlbinext: past end of cluster (3829)
or
SYSTEM ERROR: rlrdprv: There are no more notes to be read. (865)
Fast schema change helps limit the size of .bi space required and potentially could prevent these errors.