Kbase 19655: Avoiding the 2GB BI file limitation when making V8 schema changes.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Verified
FACT(s) (Environment):
Progress 8.x
SYMPTOM(s):
SYSTEM ERROR: rlbinext: past end of cluster (3829)
Updating/changing the schema of a V8 database
CAUSE:
With Progress version 8 and earlier, schema changes (such as ADD FIELD ... OF ...) would cause Progress to write notes into the BI file for each record within the table being updated/changed. Thus, when these schema changes are committed to the database, the 2GB BI file size limitation can be encountered in the form of the (3829( error.
FIX:
To resolve the problem, two options can be considered:
1) You can use the -i client parameter to start the Data dictionary session. This will reduce the number of writes Progress makes to the BI file, but you run the risk of data integrity problems if the schema change doesn't complete successfully.
2) If you prefer not to use the -i client parameter (or you still reach the 2GB limit doing so), you can change the schema as follows:
Make the initial schema change while the database is down. Add the new field for the table that you want to change, using a "?" as the field's initial value. This allows the "Fast Schema Change" to occur as each record is written to later in production mode. Thus, new field creation is not dependent on the number of records already contained within the table.