Introduction

This post is about Performance Using hint in Oracle EBS R12.

 

The issue was due to joins across remote sites where oracle optimizer might

Wrongly choose the driving site.

This can be resolved by using driving site hint.

It is always good to do all manipulations in one site and fetch the final

Results to the target site.

QUERY EXECUTED IN DATABASE 2

Select t1.column1, t2.column2, t2.column3

From table1 t1, xxsc.table2@db1todb2 t2

Where t1.column1 = t2.column1

Query, which was taking around 47 secs for execution

QUERY EXECUTED IN DATABASE 2

Select /*+driving_site(t2)*/  t1.column1, t2.column2, t2.column3

From table1 t1, xxsc.table2@db1todb2 t2

Where t1.column1 = t2.column1

Query which was taking around 15 msecs for execution.

 

Summary

This post described Performance Using hint in Oracle EBS R12.

 

Got any queries?

Do drop a note by writing us at doyen.ebiz@gmail.com or use the comment section below to ask your questions.

Recent Posts

Start typing and press Enter to search