Kbase P129257: The ORACLE DataServer NO-QUERY-UNIQUE-ADDED option of the QUERY-TUNING does not bypass the unique_id
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/27/2008 |
|
Status: Unverified
FACT(s) (Environment):
Oracle DataServer
OpenEdge 10.1B
SYMPTOM(s):
The NO-QUERY-UNIQUE-ADDED option of the QUERY-TUNING does not bypass the unique order adjustment at the query level.
The unique_id_0 ORACLE ROWID is still listed in the ORDER BY clause of the query sent to the ORACLE database
Specifying QUERY-TUNING(NO-QUERY-UNIQUE-ADDED) in the ABL query
The ORACLE table does not contain the PROGRESS_RECID column.
Starting the client session with the -zod startup parameter allows to bypass the unique_id_0 ORACLE ROWID.
CAUSE:
This is a known issue
FIX:
As a workaround, start the client session with the -zod startup parameter: prowin32 -zod < Other startup parameters>
The -zod startup parameters impact all queries executed in the session.
At compile-time, the following message appears when you use the -zod parameter:
zod suppressed ORDER BY unique_id_0 may cause inconsistent ordering