Kbase P117479: How to ASCII load tables > 2 GB
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/13/2008 |
|
Status: Verified
GOAL:
How to ASCII load tables > 2GB
GOAL:
How to load tables 2GB in the data dictionary
GOAL:
Database Administration tool fails to load large table
GOAL:
Why loading a table fails with ** Array subscript 11 is out of range. (26)
GOAL:
How to workaround ** Unable to update Field. (142) when loading a .d file
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.0x
OpenEdge 10.1A
OpenEdge 10.1B
All Supported Operating Systems
FIX:
The Data Dictionary load or Database Administration Load utilities are essentially 4GL utilities. So, on a file system without 2Gb limits or user limits/quotas, the 4GL will be able to create a dump file larger than 2Gb: as the output is just appended to, leaving the environment to control the file limit.
When the resulting ASCII dump succeeds in creating a dump file GT 2 GB, prior to OpenEdge 10.1C the limitation on the product is that the trailer information (even if manually entered) cannot be read while loading the resulting GT 2 GB dump file as the lseek position is still 32-bit limited and therefore fails. Typically with error messages:
** Array subscript 11 out of range (26)
** Unable to update Field (142)
A simple 4GL load as follows would succeed in loading the ascii dump file, PROVIDED that the client session is started with the correct codepage, date format, number format etc.
INPUT FROM "<fully qualified path to ASCII dump file><dumpfilename.d>".
DO WHILE NOT ERROR-STATUS:ERROR TRANSACTION:
CREATE <table name>.
IMPORT <table name>.
END.
Otherwise, please refer to Solution P117480, "How to ASCII dump AND load tables > 2 GB"