en accessing dictionary
> objects as part of an app.
>
> hth
> connor
>
> --- [EMAIL PROTECTED] wrote: >
> > Bruce,
> >
> > Can you expand further on the following statement?
>
> > We use a lot of
> > synonyms (not in forms but in SQL).
> &
needed to (due to "bad" execution plan).
>
>
> Thanks,
>
> Cherie Machler
> Oracle DBA
> Gelco Information System
>
-----------------
>
> "Reardon, Bruce (CALBBAY)"
>Subject:
recipients of list ORACLE-L
> <[EMAIL PROTECTED]>
> to.com.au>
>cc:
>
Subject: Synonyms
ist ORACLE-L
> Subject: Re: Synonyms can be VERY bad for performance
>
>
> Greg,
>
> Hey! I resemble that remark ;)
>
> The data dictionary views are optimized to use the RBO
> or are heavily hinted to force a specific access path.
> ALL_ROWS and FIRST_ROWS force the C
ctober 31, 2001 3:30 PM
> To: Multiple recipients of list ORACLE-L
> Subject: Re: Synonyms can be VERY bad for performance
>
>
> Greg,
>
> Hey! I resemble that remark ;)
>
> The data dictionary views are optimized to use the RBO
> or are heavily hinted to force
Greg,
Hey! I resemble that remark ;)
The data dictionary views are optimized to use the RBO
or are heavily hinted to force a specific access path.
ALL_ROWS and FIRST_ROWS force the CBO to be used so a
different access path may be taken resulting in poor
performance.
Obligatory notes:
Note: 3
> Because we were in first_rows, queries
> against the data dictionary were
> optimized in first_rows mode rather than rule.
> This was despite us not having any statistics
> on system or sys objects.
Is this standard behavior?
What about the warnings not to analyze SYS because it's optimized fo
For your information and comment.
We have just had a situation where the use of synonyms in our Forms
application was very bad for performance.
In particular, opening a form was taking around 11 seconds, and 9.3 seconds
of that was spent in translating the synonyms.
A section of the tkprof outpu
