Kbase P123605: Errors 450 and 3191 on loading schema (.df) with Client Server connection
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
24/02/2009 |
|
Status: Verified
SYMPTOM(s):
Loading of .df fails with errors 450 and 3191 when using Client Server connection
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)
Errors 450 and 3191 on Delta.df load online
No corruption presents in the database
Loading of .df succeeds single user
Loading of .df succeeds self-service
Schema update succeeds after a dump and load of table(s) involved
mandatory fields in the delta .df raise error 16
SYSTEM ERROR: bffld: nxtfld: scan past last field. (16)
** File <file> - Cannot apply dictionary changes to existing records. (151)
Data Administration fails to load an incremental df with client server connection
FACT(s) (Environment):
OpenEdge 10.1B
OpenEdge 10.1B01 Service Pack
All Supported Operating Systems
CAUSE:
Bug# OE00148590
CAUSE:
This is a known issue being investigated by development. This issue is specific to online schema changes when connected client/server from an OpenEdge 10.1B client to an OpenEdge 10.1B server. The record reconstruction of a fragmented record is different when performed by the _mprosrv remote server as opposed to the _progres or prowin32 single-user.
FIX:
Upgrade to OpenEdge 10.1B02 or later where this issue has been addressed. Note that the fix is on both the client and the server side, so update both the OpenEdge 10.1B clients and OpenEdge 10.1B server.
Alternatively, there are four proposed Workarounds: (listed in order of preference)
1) Offline: Load the schema change (delta .df) in single-user mode.
2) Online: Use shared memory connection instead of client-server to load the schema change (delta .df)
3) Online: If the schema change must be loaded client server;
Split the schema change into multiple files separating out the TABLE | FIELD from the INDEX instructions,
then load definitions_1 client server then definitions_2 client server next:
definitions_1: containing the table(s) | field(s) schema changes,
definitions_2: containing the index(es) schema changes.
4) Online: If the schema change must be loaded client server;
Delete and reload the table in question against the new schema