Kbase P59016: Error 137 during a binary or Ascii dump
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
GOAL:
Consequences of error(s) 137 during a binary dump
FIX:
Occurrence(s) of
SYSTEM ERROR: Record continuation not found, fragment recid <recid>. (137)
during a binary dump should not stop that dump.
The resulting .bd file(s) has(have) all the records of your table, except the ones for which a fragment was missing.
A "SELECT COUNT(*) FROM <table>" run on the original table and then run on the "reloaded" table, after the primary index has been rebuild, should show that the number of records missing in the new table is the number of occurrences of System Error 137