OpenEdge DataServer for Oracle crashes on INDEXED-REPOSITION

The introduction of the position independent r-code feature in OpenEdge 11.0 causes a regression where the OpenEdge DataServer for Oracle process is susceptible to crash on a query that includes the NDEXED-REPOSITION keyword.

Nov 22, 2018
Knowledge

Title

URL Name

OpenEdge-DataServer-for-Oracle-crashes-on-INDEXED-REPOSITION

Article Number

000135398

Environment

Product: OpenEdge Version: 11.x OS: All supported platforms Other: All supported Oracle RDBMS versions

Question/Problem Description

OpenEdge DataServer for Oracle crashes on INDEXED-REPOSITION.

The position independent r-code feature in OpenEdge 11.0 causes a regression where the OpenEdge DataServer for Oracle process is susceptible to crash on a query that includes the INDEXED-REPOSITION keyword in combination with the FIELDS phrase.

The following query reproduces the issue:

DEFINE VARIABLE hQuery AS HANDLE NO-UNDO.
DEFINE VARIABLE QueryString AS CHARACTER NO-UNDO.
DEFINE VARIABLE RowIdToReposition AS ROWID NO-UNDO.

DEFINE BUFFER b_Customer FOR Customer.
    

ASSIGN QueryString = "FOR EACH b_Customer FIELDS(custnum name city country) NO-LOCK  ":U +
        " BY b_Customer.custnum INDEXED-REPOSITION":U. 
    
/* get last and reposition backwards */
FOR FIRST b_Customer WHERE b_Customer.custnum = "2500":U :
    ASSIGN RowIdToReposition = ROWID(b_Customer).
END.    


CREATE QUERY hQuery.

hQuery:ADD-BUFFER (BUFFER b_Customer:HANDLE).

hquery:QUERY-PREPARE (QueryString).
hQuery:QUERY-OPEN().
hQuery:GET-FIRST().
MESSAGE SUBSTITUTE("YVW: &1 ~n FIRST &2":U, PROGRAM-NAME( 1 ), b_Customer.custnum ) VIEW-AS ALERT-BOX.
hQuery:REPOSITION-TO-ROWID (RowIdToReposition).
hQuery:GET-NEXT ().
MESSAGE SUBSTITUTE("YVW: &1 ~n REPOSITION &2":U, PROGRAM-NAME( 1 ), b_Customer.custnum ) VIEW-AS ALERT-BOX.
hQuery:GET-PREV ().  /* Crash occurs on the hQuery:GET-PREV () statement */
MESSAGE SUBSTITUTE("YVW: &1 ~n Previous &2":U, PROGRAM-NAME( 1 ), b_Customer.custnum ) VIEW-AS ALERT-BOX.
MESSAGE SUBSTITUTE("YVW: &1 ~n the end":U, PROGRAM-NAME( 1 ) ) VIEW-AS ALERT-BOX.

Steps to Reproduce

Clarifying Information

If you remove one field from the fields in the field phrases (does not matter witch field) the program runs fine.

Error Message

No Error message. The session crashes with no protrace generated

Defect Number

Defect ODIA-2507

Enhancement Number

Cause

This issue is a side effect of position independent rcode feature introduced in OpenEdge 11.0.

Resolution

The fix for this issue is expected to be in the upcoming release 11.7.5. As of November 2018, release 11.7.5 is scheduled to be released in Q1 2019, although dates and content of the release are subject to change.
Until the fix is available, use the workaround below.

Workaround

Use -znoposirc client startup parameter as a workaround.
The -znoposirc switch is for backward compatibility and has the effect of disabling the position-independent r-code feature developed in version 11.0 for the explicit purpose of decoupling column position on the server from field position in r-code for customers' deployment requirements.

Please note that when this parameter is used, all r-code in the session MUST also be compiled using the parameter. If this is not done a completely different algorithm is used to map the fields and unexpected behavior will occur.

Notes

Keyword Phrase

Last Modified Date

11/22/2018 12:13 PM

OpenEdge DataServer for Oracle crashes on INDEXED-REPOSITION

Files(0)

Was this article helpful?

Was this article helpful?

OpenEdge DataServer for Oracle crashes on INDEXED-REPOSITION

Information

Related Articles