Re: DB File Sequential Read Waits

ralbertson_at_comcast.net (rjpfal) wrote in message news:<2932a99f.0312300754.5af48627_at_posting.google.com>...
> srivenu_at_hotmail.com (srivenu) wrote in message news:<1a68177.0312292314.71fc02e6_at_posting.google.com>...
>
> Answers below:

<snip>
> > During the period of collection, i think several long running
> > operations have ended.
> > Your hard parse ratio is horrible.
>
> Yes no bind variables being used at all. I am talking with developers
> about this now.
>
> > Did you do any customization ? I think your developers are not using
> > bind variables.
>
> None working on solution. Yes there is customization but even core
> code has no bind variables.
>

good luck running with an init.ora parameter of cursor_sharing = FORCE.
It is okay on 8.1.7.4.6, but on 8.1.7.4.12 (win32), you'll throw these:

ORA-00600: internal error code, arguments: [729], [28820], [space leak], [], [], [], [], []

I don't think that cursor_sharing = FORCE is particularly stable on 8.1.6.3.x, but its been several years since I worked with it, as it was de-supported long ago.

You would have had much more leverage if support for 8.1.7.x had not been pushed back (still burning over that one).

We're also running with 9.2.0.4 in production, with optimizer_features_enable=8.1.7 with good results. Beware of nested loops going to hash_joins, particularly with slow IO for full table scans.

Pd Received on Wed Dec 31 2003 - 12:33:36 CST