Load error.

[ron]

I'm preparing to dump/reload a large number of DBs that have not been dumped/reloaded for a long time (in many cases since Progress 7). The version of Progress is now 9.1E - under AIX 5.3

During testing I get a failure loading a table:

Start DATE/TIME for edi-func-key Thu 03 Mar 11 21:55:43
PROGRESS Version 9.1E as of Tue Oct 12 17:19:22 EDT 2004

The number of fields in the schema is 4, expected 5. (6271)
Binary Load failed. (6255)
Finish DATE/TIME edi-func-key Thu 03 Mar 11 21:55:43
​

As best as I can figure from KBs - it looks like a field has been deleted from the table in the past.

The existing schema defines 4 fields for this table - all CHAR.

The thing that puzzles me is that this table is empty ....

Start DATE/TIME for edi-func-key Thu 03 Mar 11 21:51:52
PROGRESS Version 9.1E as of Tue Oct 12 17:19:22 EDT 2004
Using index 754 for dump of table edi-func-key. (6101)
Dumped 0 record(s). (6127)
Binary Dump complete. (6254)
Finish DATE/TIME edi-func-key Thu 03 Mar 11 21:51:52
​

So ... why is proutil complaining. There is no "data", per se, for it to look at.

I have to presume, therefore, that a binary dump produces some sort of "header" that defines the format of the table data. Is that correct?

Since the table is empty I presume that my best strategy is to just simply skip attempting to load this table. I can't see any "downside" from that.

Any comments?

Ron.

 

[RealHeavyDude]

I might be wrong, but, Progress V9 introduced the fast schema change. AFAIK when you delete a field that is not indexed the data stays in the table until it is touched. If a record in the table is never touched it will still contain the data and AFAIK the binary dump will happily dump it because it will always dump the record as is. I think as soon as you do a simple FOR EACH on the offending table that touches each record in the table your problem should be fixed.

IMHO, at least it's worth a try.

Heavy Regards, RealHeavyDude.