Wow.
SYS@():2277,313> desc uet$
Name Null? Type
----------------------------------------- -------- ----------------------
SEGFILE# NOT NULL NUMBER
SEGBLOCK# NOT NULL NUMBER
EXT# NOT NULL NUMBER
TS# NOT NULL NUMBER
FILE# NOT NULL NUMBER
BLOCK# NOT NULL NUMBER
LENGTH NOT NULL NUMBER
Regards,
JT
On Thu, 12 Nov 2015 at 18:43 Cary Millsap <cary.millsap@xxxxxxxxxxxx> wrote:
Back in Oracle version 6.0.36, I asked in an enhancement request for a
timestamp column in UET$.
Is it *still* not there? :-)
Cary Millsap
Method R Corporation
Author of *Optimizing Oracle Performance <http://amzn.to/OM0q75>* and *The
Method R Guide to Mastering Oracle Trace Data <http://amzn.to/173bpzg>*
Get the MOTD book free (PDF) at method-r.com <http://method-r.com>
On Wed, Nov 11, 2015 at 4:13 PM, Upendra nerilla <nupendra@xxxxxxxxxxx>
wrote:
Hello all -
I am trying to track the growth of a few problem tables.. if there is a
runaway process, they might continue to write without dying.. I looked at
dba_hist_seg_stat.space_used_delta, it doesn't seem to be consistent in
tracking the growth. Especially for situations like, if the table gets
truncated or if there are massive deletes, this data doesn't accurately
represent reality..
Any suggestions on how it could be tracked?
Worst case I am thinking of dumping the dba_segment data into a table
nightly to track it. Trying to see if there are better ways to handle this.
Thanks
-Upendra
