Kbase 20439: Dump and Load Problems from Progress 9.1x to Progress 7.3x.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
24/02/2010 |
|
Status: Unverified
GOAL:
What are some errors that occur due to inconsistencies that might arise when going backwards to load data and df.
GOAL:
Possible errors when doing a load of a Progress 9.X dbase into an older version of Progress (i.e. Progress 8.x or 7.x)
FACT(s) (Environment):
Progress 9.x
Progress 7.x
FIX:
The following are possible errors that might appear when trying to perform a load of Progress 9.x data definitions / data into a Progress 7.x database:
1) ERROR
Error during ADD TABLE Invoice
Table: In
Field ** Line 2 AREA Info Area
Index:
Sequence: Unknown TABLE keyword
-
<OK>
2) ERROR
Database: ** Error during ADD FIELD Invoice-Num **
Table:
Field: ** Line 10 POSITION 2
Index:
Sequence: Unknown FIELD keyword
-
<OK>
3) ERROR
Database: ** Error during ADD FIELD Invoice-Num **
Table:
Field: ** Line 10 SQL-WIDTH 4
Index:
Sequence: Unknown FIELD keyword
-
<OK>
4) ERROR 83
The numeric formats of this PROGRESS-session
and the .d-file don't match!
Please exit PROGRESS and start a new session
with the -E startup parameter.
-
<OK>
-
5) ERROR 147
** The month of a date must be from 1 to 12. (80)
Press OK to continue or Cancel to stop processing.
-
<OK> <Cancel>
-
6) Load of database contents completed.
Errors listed in .e files placed into same directory as .d files
$ more customer.e
>> ERROR! -d <mdy> or -yy <n> settings of dump were dmy-1950
** but current settings are mdy-1900. May cause load errors.
Possible Workarounds:
For the last two screen errors that are listed above, the .d files must be edited so that the numformat line and the dateformat lines are removed. Alternately the dateformat could be changed so that it is correct.
This is a small excerpt from the .d file:
??..
PSC
filename=Customer
records=0000000000083
ldbname=sports
timestamp=2000/12/19-09:38:12
numformat=44,46
dateformat=dmy-1950
map=NO-MAP
cpstream=ISO8859-1
Another thing that might help resolve some of these errors are to modify the data definition (df) files. The following is a small excerpt from the .df file.
The three lines that begin with "AREA", "POSITION" and "SQL" must be removed.
ADD TABLE "Invoice"
AREA "Info Area"
DESCRIPTION "This contains transactions for the Receivables system"
DUMP-NAME "invoice"
TABLE-TRIGGER "CREATE" NO-OVERRIDE PROCEDURE "sports/crinv.p" CRC "?
"
TABLE-TRIGGER "DELETE" NO-OVERRIDE PROCEDURE "sports/delinv.p" CRC
"?"
ADD FIELD "Invoice-Num" OF "Invoice" AS integer
FORMAT ">>>>>9"
INITIAL "0"
POSITION 2
SQL-WIDTH 4
VALEXP "invoice-num > 0"
VALMSG "Invoice number cannot be zero"
ORDER 10