Kbase 17842: Bug - Fast Schema Change & Binary Dump/Load before 8.2C
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/01/2000 |
|
Bug - Fast Schema Change & Binary Dump/Load before 8.2C
Bug - Fast Schema Change & Binary Dump/Load before 8.2C
-------------------------------------------------------
This is a very narrow scope bug and specific steps must
have been followed to hit this bug. They are:
1) make a fast schema update to your database
required steps to be a "FAST SCHEMA CHANGE"
1) disconnect all the clients from the database
2) start a client connect to the database
3) add a new field or fields to the schema using:
a) SQL ALTER TABLE statement
b) data dictionary
c) 4GL statement (not recommended)
4) the initial value of the new field(s) must be (?)
5) recompile code
2) dump your schema using the dictionary, now do a binary dump of
the database tables. You probably have not updated all your
records with the new fields. REMEMBER-with fast schema
change we change records as they are accessed or updated not at
time of schema change.
3) create a new database and load the schema. now load your data
and do an index rebuild.
You may then start seeing, on the newly loaded database, error
messages like:
SYSTEM ERROR: Cannot read field from record, not enough fields. (450)
SYSTEM ERROR: Failed to extract field <field-num> from <file-name>
record (table <table-num>) with recid <RECID>. (3191)
This is a bug is fixed in version 8.2C of Progress.
WORK AROUND
-----------
If you have not yet moved to 8.2C of Progress there is a work
around.
1) dump your schema again.
2) binary dump your data again.
3) edit the fast schema change "out" of your .df file (save it
another file for now).
4) create a new database and load your modified schema.
5) now enter the database and go to the data dictionary.
6) now add the fast schema change again. ******
7) exit the database.
8) load the binary data information and do an index rebuild.
****** Because this fast schema change is again added to the
database, the database will modify these records with the new
method, the database does not know there is a fast schema change in
some stage of incompletion and it assumes all records are complete
during the load.
Again, this is a bug is fixed in version 8.2C of Progress.
RVE (4/9/98)
Progress Software Technical Support Note # 17842