Kbase P103652: Changing records errors with The total length of the fields in an index exceeds max key size. (129)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
20/03/2008 |
|
Status: Verified
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.0x
OpenEdge 10.1A
SYMPTOM(s):
Concatenating two fields and assigning the result to an indexed field.
The total length of the fields in an index exceeds max key size. (129)
Static SDO contains large calculated field.
CAUSE:
Enhancement Request# 20050201-014
CAUSE:
The resulting length of the indexed field exceeded the allowed maximum of 188 characters. A PROGRESS index consists of one or more fields. For an individual record, the sum of the lengths of all fields in any one index cannot be more than 188 characters (200 in total including the storage overhead). This is a limit.
FIX:
An enhancement has been implemented in the OpenEdge 10.1B in the form of the "proutil -C enablelargekeys" utility only for databases with 4KB or 8KB database blocksize. Once enabled, the new index key is limited to approximately 1970 characters.
Please refer to "OpenEdge Data Management: Database Adminstration" for further information.
Prior to OpenEdge 10.1B, the only fix is to modify the application to put a shorter string to an index or to use the BASIC collation.
Prior to OpenEdge 10.1B, the only solution is to either modify the data or the index definition to avoid exceeding this limit.