Kbase P78631: Can I Specify the ORACLE hint syntax that the DataServer passes directly to the ORACLE DBMS as part
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/29/2004 |
|
Status: Verified
GOAL:
Can I Specify the ORACLE hint syntax that the DataServer passes directly to the ORACLE DBMS as part of the query?
GOAL:
How do I specify my own index hint for DataServer to pass to Oracle?
GOAL:
Is there a way to control what hints are sent to Oracle?
FACT(s) (Environment):
Oracle DataServer
FIX:
The Progress QUERY-TUNING phrase has a hint option which specifies the ORACLE hint syntax that the DataServer passes directly to the ORACLE DBMS as part of the query. This allows you to control which hints are passed as opposed to the index hints that the DataServer passes when appropriate.
When you have to specify an index name in the hint syntax, use the name defined in the ORACLE database. Because the DataServer generates aliases for ORACLE tables using names from T0 through T9, use these aliases to refer to tables in the hint syntax.
The DataServer passes the opening symbols (/*+) and closing symbols (*/). For example, to pass the /*+ORDERED*/ hint syntax, you specify only HINT "ORDERED".
Passing incorrect hint syntax, inappropriate hints, or conflicting hints will not return an error but might give you unpredictable results. See ORACLE documentation for information on hint syntax.
The syntax is:
FOR EACH table QUERY-TUNING ( hint hint1 hint2 hint3 )
For example:
FOR EACH Customer WHERE order-num > 20
QUERY-TUNING(HINT "FIRST_ROWS"):