The procedure still isn 't scalable at all, but at least it runs -- for =3D
now. Since it 's a month-end job and it 's month-end, it 'll have to do =3D
for now. And we 'll be throwing hardware at our nasty SQLs in a month to =
=3D
make them run reasonably well again for a few years. And the cycle =3D
continues... <sigh >
THANKS for the help!!!
I 'm Rich Jesse, and I approve of this message.
Rich Jesse System/Database Administrator
rich.jesse@(protected) QuadTech, Sussex, WI USA
> -- --Original Message-- --
> From: oracle-l-bounce@(protected)
> [mailto:oracle-l-bounce@(protected)]
> Sent: Thursday, April 29, 2004 9:09 PM
> To: oracle-l@(protected)
> Subject: RE: INSERT...SELECT pegs CPU, but is waiting on=3D20
> scattered read?
>=3D20
>=3D20
> Rich,
>=3D20
> The Oracle kernel is not going to emit a trace line until=3D20
> either (a) it
> completes a "timed event " (like an OS read() call), or (b) it=3D20
> completes
> a db call (like an EXEC).
>=3D20
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe ' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
