Kbase P125140: Recently Discovered Corruption of Indices Issue
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
03/08/2007 |
|
Status: Verified
GOAL:
Recently Discovered Corruption of Indices Issue
GOAL:
Progress client crashes when updating a character field that participates in an index
FACT(s) (Environment):
OpenEdge 10.x
All Supported Operating Systems
FIX:
Dear Valued Partner and Customers,
Progress Software has recently become aware of an issue within the OpenEdge database product.
The items below reference the recently discovered issue. In addition, it highlights the solution that describes the problem in full.
This defect has the potential to crash the client or corrupt word indices from 10.0A to 10.1B01 and corrupt normal indices in a database with Large Key Entry support enabled in 10.1B and 10.1B01 when ALL of the following conditions are true:
1) Word indices, from 10.0A
- A client using -cpinternal UTF-8 against a non-UTF-8 database
- A word index on a character field
- A value in the character field that, when converted to the database codepage, exceeds 200 bytes
2) Normal indices, from 10.1B
- A client using -cpinternal UTF-8 against a non-UTF-8 database
- The database has Large Key Entry support enabled
- A character field that is part of an index
- A value in the character field that, when converted to the database codepage, exceeds 200 bytes
P125102, "Progress clients crash and index corrupted when using Unicode client against non-Unicode database"
This issue has been corrected in OpenEdge 10.1B02.
If you have any questions or concerns regarding this issue, please follow up with Progress Technical Support in your region.
http://www.progress.com/openedge/support/tech_support/contact_support/index.ssp