-----Original Message-----
Ari,
A quick question I hope. We have a system running an Oracle database
that is generating an exceptionally large archive logs as compared to other
installations of the system. Is their a way we can examine the contents of
the archive log file to determine exactly what tables are being changed to
cause this? Or some other method?
Thanks in advance,
Pete
-----------------
Peter W. Baljet
Manager Integration Services
ICC/GR Software
voice: 404-255-8336
fax: 404-250-0602
baljetp@genrad.com
---- Reply --------------
Peter,
Two things usually cause extra redo usage:
1) If your tablespaces are in hot-backup mode, then extra redo activity is
generated for the tablespaces in hot-backup mode.
2) If SQL_TRACE is true, then there may be more activity in the database.
To determine the top SQL statements, you can do:
(For most rows processed:)
SELECT SQL_TEXT, ROWS_PROCESSED FROM V$SQLAREA ORDER BY 2;
(For most disk reads - not a redo causing problem :)
SELECT SQL_TEXT, DISK_READS FROM V$SQLAREA ORDER BY 2;
As for examining the redo logs, in UNIX you can issue:
strings -a |more
This will give you some cryptic data. If you can analyze it, let me know and
I'll share it on my webpage!
Best regards,
-Ari Kaplan
Independent Oracle DBA Consultant
<-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><->
<-> For 210+ Oracle tips, visit my Web Page: <->
<-> <->
<-> www.arikaplan.com <->
<-> <->
<-> email: akaplan@interaccess.com <->
<-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><->
Back to Ari Kaplan's Home Page