Re: Trigger SMON to dump table statistics to ALL_TAB_MODIFICATIONS

From: "Ethan Post" <post.ethan@xxxxxxxxx>
To: "Alexander Fatkulin" <afatkulin@xxxxxxxxx>
Date: Wed, 6 Jun 2007 15:26:39 -0500

The issue here was the object was incorrect. The SQL was an INSERT into
table A, the query was showing an INSERT into table B.

On 6/6/07, Alexander Fatkulin <afatkulin@xxxxxxxxx> wrote:


The SGA monitoring counters are not fully serialized (imagine an
overhead otherwise).

The numbers are "about" and not 100% correct. You can insert and later
rollback - the counters will add up.

References:

Trigger SMON to dump table statistics to ALL_TAB_MODIFICATIONS
From: Ethan Post

Re: Trigger SMON to dump table statistics to ALL_TAB_MODIFICATIONS
From: Tim Gorman

Re: Trigger SMON to dump table statistics to ALL_TAB_MODIFICATIONS
From: Ethan Post

Re: Trigger SMON to dump table statistics to ALL_TAB_MODIFICATIONS
From: Alexander Fatkulin

Other related posts:

Browse oracle-l