Kbase P22806: DBADMIN dump reports Array subscript 6 is out of range. (26)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
29/06/2009 |
|
Status: Verified
SYMPTOM(s):
DBADMIN dump returned message Array subscript 6 is out of range. (26)
Array subscript 6 is out of range. (26)
** Array subscript <value> is out of range. (26)
FACT(s) (Environment):
DBADMIN tool being used in shared memory
Multiple DBADMIN dump sessions
All Supported Operating Systems
Progress/OpenEdge Product Family
OpenEdge Category: Database
CAUSE:
The Array field being read cannot read the subscript entry mentioned for some reason. For example, the Salesrep.MonthQuota [12] field in the sample sports2000 database would report Array subscript 13 is out of range. (26) if there were corruption so that there were more than 12 entries for the array.
When a record is corrupt, it is not included in the dump.d
The corruption itself could be due to hardware failure or 4GL update issues. Both these causes would have to be investigated out of scope of this Progress Solution. We cannot recover this record.
FIX:
To ascertain what the impact of this situation would have on the new database: It could be only 1 record, or it could be a large percentage of the table.
For example, if there were records:
1
2
3
...
END OF RECORDS
and record 3 is the one that is corrupt, we need to ascertain if the dump "skipped" 3 and continued onto 4,5,6,7 .. etc; or if the dump stopped at 2.
To investigate this:
+ perform a dbanalys against the database being dumped from (DB1) and
+ a dbanalys against database being loaded to (DB2)
Then compare the record count between the two for the selection of tables being dumped when the message appeared (26).
Alternatively, if it is a single table in question, dump the table from DB2 once loaded and compared the table_DB1.d record count to table_DB2.d record count. There may be a dump.e file in the directory that was being dumped into at the time, which will help to narrow this investigation down.
Once the impact has been ascertained, further decisions can be made in terms of recovering this data from site records.