Instantiating class containing static temp-table in ASSIGN of database fields causes index corruption

Index corruption occurs when a class containing a static temp-table is instantiated within an ASSIGN statement for a database record where one or more fields are indexed.

Jun 6, 2013
Knowledge

Title

URL Name

P159883

Article Number

000154437

Environment

Product: OpenEdge Version: 10.x through 10.2B05 OS: All supported platforms

Question/Problem Description

Procedure is run which creates a database record.
Multiple fields assigned with single ASSIGN statement.
Static method from a class containing a static temp-table is invoked in ASSIGN statement.

The newly created database record cannot be found with the FIND statement using a simple WHERE clause (WHERE <field> = <value>). Error 138 will be raised ("** <table> record not on file. (138)")

If the field is a CHARACTER field and the TRIM function is applied to the field in the WHERE clause (WHERE TRIM(<field>) = <value>), the FIND succeeds.

A DELETE statement with either WHERE clause (with or without the TRIM function) fails with error 1422 ("SYSTEM ERROR: Index in for recid could not be deleted. (1422)")

Steps to Reproduce

1) Unzip the attached file 000030911.zip into the OpenEdge work directory 2) Create a copy of the Sports2000 sample database in the working directory: 3) Connect the Procedure Editor to Sports2000. 4) Run bugtest.p in the Procedure Editor. This procedure creates a record in the Customer table, and then runs a static method from class Dummy.cls. Dummy.cls also contains a static temp-table. 5) Run find.p in the Procedure Editor. Error 138 will be raised. 6) Run trim.p in the Procedure Editor. The record added by bugtest.p will be displayed. 7) Run delete.p in the Procedure Editor. Error 1422 will be raised.

Clarifying Information

The database table for which the index becomes corrupted and the static temp-table in the class that is instantiated do not have to be related in any way. For example, the temp-table does not have to be defined LIKE the database table, nor do they have to share any fields.

The temp-table does not have to be used in the code to cause the problem; it only has to be defined.

Error Message

** <file-name> record not on file. (138) SYSTEM ERROR: Index in for recid could not be deleted. (1422) Index rebuild complete. <number> error(s) encountered. (1644)

Defect Number

Defect OE00195049 / PSC00222733, OE00214476 / PSC00239059

Enhancement Number

Cause

While instantiating the class containing the temp-table, information is cleared that is needed to complete processing of the ASSIGN statement.

Resolution

To avoid this problem, upgrade to OpenEdge 10.2B06 or OpenEdge 11.0.

To correct the index corruption caused by this problem:

If the offending code has been run only once, run PROUTIL IDXBUILD to fix the index corruption so that the new record can be found or deleted.
If the code has been run more than once in an attempt to create the "missing" record, IDXBUILD may not fix the corruption. Error 1644 will be displayed:

Index rebuild complete. <number> error(s) encountered. (1644)

This is because the record was in fact created more than once with the same value for a unique index. In this case, the table must be dumped, deleted from the database, and loaded to remove the index corruption. After the dump and load, one copy of the newly created record will exist in the table and can be found or deleted.

Workaround

To avoid this problem, move the call to the static method outside of the assign statement.
Attached 000030911.zip also contains a workaroundtest.p that shows this, based on the bugtest.p.

As above, existing corruption needs to be corrected once the workaround is in place.

Notes

Defect OE00195049 / PSC00222733 was fixed as part of the fix for defect OE00214476 / PSC00239059, which was included in OpenEdge Service Pack 10.2B06 as well as OpenEdge 11.0.

References to Other Documentation:

Progress Article:

"Errors 129 and 11353 when trying to instantiate singleton"

Keyword Phrase

Last Modified Date

11/20/2020 7:35 AM

Instantiating class containing static temp-table in ASSIGN of database fields causes index corruption

Files(1)

Was this article helpful?

Was this article helpful?

Instantiating class containing static temp-table in ASSIGN of database fields causes index corruption

Information

Related Articles