Kbase 34831: Binary load from script fails when encountering errors 6183 and 6272
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/15/2000 |
|
Solution ID: P4831
SYMPTOM(s):
Binary load being run within a script fails
Running proutil dbname -C load (binary load)
Table <name> is number <num> in dump file and <num> in schema (6183)
The table numbers do not match, but the number of fields are the same
between the schema and dump file. Continue? (Yes/No, Default = No) (6272)
CAUSE:
The script fails when no proper acknowledgement is made by the script to the 6272 message and resulting prompt. 6183 is only an informational message.
These messages occur when a source and target databases have different table numbers for the same table. If the original database has had some tables added and deleted, there will be an inconsistency in table number between the source and target database. Table numbers are assigned in ascending order and are not reused. If the .df file is dumped from the source database and loaded it into a new empty database, this message would not be encountered.
FIX:
Run binary load from the command line rather than a script. This allows you to respond to the required prompt of 6272.