RE: dba_tab_mod view

  • From: "Deas, Scott" <Scott.Deas@xxxxxxx>
  • To: "veeeraman@xxxxxxxxx" <veeeraman@xxxxxxxxx>, ORACLE-L <oracle-l@xxxxxxxxxxxxx>
  • Date: Tue, 12 May 2015 14:48:22 +0000

Ram,

After you issue DML, but before you run statistics, you can run
dbms_stats.flush_database_monitoring_info to update the views.

http://docs.oracle.com/cd/E11882_01/appdev.112/e40758/d_stats.htm#ARPLS68568

Thanks
Scott

From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Ram Raman
Sent: Monday, May 11, 2015 7:13 PM
To: ORACLE-L
Subject: dba_tab_mod view

List,

After seeing lots of global services enqueue deadlock errors in our rac, I was
looking up the trace files. I was able to see the sql; the trace files are huge
(in GBs) . The sql was simple and was updating one table only repeatedly. I
wanted to know how many updates had happened in the table, but the dba_tab_mod
view is empty for that table. The table was last analyzed last night. Does this
mean that the updates did not happen at all due the deadlock errors?

To my knowledge, the DTM view is emptied out after a stats collection. Is there
anything else that would cause the no rows selected for a table from that view.
v11.2

Ram.

Notice of Confidentiality: **This E-mail and any of its attachments may contain
Lincoln National Corporation proprietary information, which is privileged,
confidential,
or subject to copyright belonging to the Lincoln National Corporation family of
companies. This E-mail is intended solely for the use of the individual or
entity to
which it is addressed. If you are not the intended recipient of this E-mail,
you are
hereby notified that any dissemination, distribution, copying, or action taken
in
relation to the contents of and attachments to this E-mail is strictly
prohibited
and may be unlawful. If you have received this E-mail in error, please notify
the
sender immediately and permanently delete the original and any copy of this
E-mail
and any printout. Thank You.**

Other related posts: