Consultor Eletrônico

Status: Verified

GOAL:

How do I dump around a bad record?

FACT(s) (Environment):

All Supported Operating Systems
Progress/OpenEdge Product Family

FIX:

Here is how to dump around a bad record:

Dump around the bad records and then rebuild the file. If you are running a
QUERY or RUNTIME version of PROGRESS you are not allowed to create procedures
that modify the database schema. If you have a RUNTIME version of the product,
whoever distributed PROGRESS to you provided a utility for dumping and reloading
the database. Consult the documentation you got from the developer on how to do
this, or contact the application developer directly.
If you have FULL PROGRESS, export the records starting at the top of the file,
until the error occurs, writing to an output file name <filename>.d., where
<filename> represents the name of the corrupt database file currently in the
data dictionary as follows:
OUTPUT TO <filename>.d. FOR EACH <filename> BY
<field-name>: EXPORT <filename>. END.

note: You can also define another output
stream to display the primary index within the FOR EACH loop. You do this to see
the last index value dumped before the error occurs.

Export the records starting at the bottom of the file, until the error occurs,
writing to the same output file as follows:
OUTPUT TO <filename>.d
APPEND. FOR EACH <filename> BY <field-name> DESCENDING: EXPORT <filename>. END.

Use the PROGRESS Data Dictionary "Dump Data Definitions" to dump the schema of
the corrupt file.

Use the PROGRESS Data Dictionary "Delete" option to delete the corrupt table.

Use the PROGRESS Data Dictionary "Load Data Definitions" to load in the schema
dumped above.

Use the PROGRESS Data Dictionary "Load File Contents" to load in the data from
the file created above.

Recompile all procedures that use this file.