Kbase P103749: Bulkload is unable to read an ascii dump trailer - error 9271
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/4/2010 |
|
Status: Verified
SYMPTOM(s):
Bulkload is unable to read an ascii dump trailer
Warning: Unable to read the .d trailer. Do you want to use <code-page> as the code page for conversion? [y
]: (9271)
Bulkload prompts for code page verification.
Bulkload Utility execution aborted. (9272)
Running the bulkload with an "echo y" pipe STDIN
The ascii dump (.d) file in question was exported via Data Administrator
The ascii dump (.d) file in question can be loaded via Data Administrator
FACT(s) (Environment):
Progress 8.3x
All Supported Operating Systems
OpenEdge 10.x
Progress 9.x
CAUSE:
A small history behind the inclusion of this extra (9271) prompt to the bulkload operation:
The inclusion of the (9271) message was introduced to avoid the automatic (bulk)loading of the ASCII .d files using a default code page. This was to prevent a potentially dangerous Version 8.3A issue (Bug# 19981130-007) regarding the proutil bulkload and trailer information. If Progress could not read trailer information from .d file (codepage, date and number format), a warning message was issued: "defaults are used" and Progress continued with the load. This default behavior was undesireable because there was no option given to specify the desired parameters and / or stop the process. When the database was created, a different default code page could have been used. In that case, the database could contain characters from two code page sets after the load and could be corrupted.
Given that when the bulkload utility is unable to read the code page name from the .d trailer, the Warning: "Do you want to use <code-page> as the code page for conversion?", asks for a response to confirm the utilities assumption. Upon a negative response or no response, the Bulkload execution will abort. As the Bulkload was being run with a piped "echo y", only the first .d file that had issues with the trailer suceeded having received a positive response. Subsequent .d's with the same issue were not piped the response and therefore defaults to a "n" response so the utility aborts the Bulkload operation up to the point of exit.
FIX:
Provided that the code page being suggested by the message is correct, create a response file that responds to the (9271) prompt and redirects it back into the PROUTIL command then re-run the bulkload operation as follows:
$DLC/bin/proutil dbname -C bulkload dbname.fd < /tmp/y_file
In the response file, number of "y"'s can either be set up for every table in the database, as there is no harm in having more "y" responses than needed, or for every .d file that has question-marks in the footer or no footer at all. The response file would then look simiar to this:
y
y
y
Should the desired response NOT be positive, please contact Progress Technical Support to analyse exactly what the issue with the .d footer is.