Re: DML Monitoring not working for table.

Hi Rich,

Thanks for the information. This is RAC database and last time we had abrupt shutdown as part of node eviction on 20th Apr. However, there are many records that got created on June and July month. So ideally should this make its entry to dba_tab_modifications? Or is there a bug (which anyone has experienced) / any sort of abnormal behavior that flags that this database is no more a candidate of getting monitored?

SQL> select distinct trunc(CREATED_DATE),count(*) from DR_STORE28.CONTENT_MIG_WORKFLOW group by CREATED_DATE;

TRUNC(CREATED_DATE COUNT(*)

------------------ ----------
10-JUL-19                   1
11-JUL-19                   2
26-JUN-19                   2
26-JUN-19                   4
22-JUL-19                   3
25-JUL-19                   3
10-JUL-19                   4
10-JUL-19                   7
11-JUL-19                   4
29-JUN-19                   1
03-JUL-19                   1
04-JUL-19                   1
23-JUL-19                   4
23-JUL-19                   6
24-JUL-19                   2
19-JUL-19                   1
23-JUL-19                   1
30-JUL-19                   1
26-JUN-19                   1
24-JUL-19                   3
25-JUL-19                   5
08-JUL-19                   1
10-JUL-19                   8
15-JUL-19                   1
25-JUL-19                   1
27-JUN-19                   1
26-JUN-19                   3
23-JUL-19                   3
25-JUL-19                   2
27-JUL-19                   1
10-JUL-19                   2
10-JUL-19                   5
10-JUL-19                   6
11-JUL-19                   7
17-JUL-19                   1
22-JUL-19                   1
20-JUL-19                   1
22-JUL-19                   2
22-JUL-19                   4
23-JUL-19                   2
25-JUL-19                   4
28-JUN-19                   1
11-JUL-19                   1
11-JUL-19                   5
18-JUL-19                   1
05-JUL-19                   1
06-JUL-19                   1
23-JUL-19                   7
24-JUL-19                   4
24-JUL-19                   5
24-JUL-19                   7
09-JUL-19                   1
10-JUL-19                   3
11-JUL-19                   3
26-JUL-19                   1
02-JUL-19                   1
12-JUL-19                   1
11-JUL-19                   6
16-JUL-19                   1
24-JUL-19                   1
29-JUL-19                   1
31-JUL-19                   1
21-JUL-19                   1
23-JUL-19                   5
23-JUL-19                   8
24-JUL-19                   6
24-JUL-19                   8
01-JUL-19                   1

BR,
Rakesh RA

On Wed, Jul 31, 2019 at 8:47 PM Rich J <rjoralist3_at_society.servebeer.com> wrote:

> On 2019/07/31 07:20, Rakesh Ra wrote:
>
> For couple of tables in one of 11.1.0.7 database, DML monitoring is not
> working.as expected. The stats got last gathered for the table on 4th Mar
> and that shows no records for the table. However, the table is
> having 355446 records for now.. The table stats is not locked as shown
> below below and neither it appears to be STALE in dba_tab_statistics. I am
> not sure what is causing this or even if I am doing something wrong. Can we
> have someone to provide some insights on this please?
>
>
>
> The first thing that comes to mind is to check for any termination of the
> instance, other than SHUTDOWN NORMAL. I believe that SHUTDOWN ABORT can
> cause loss of DML update counts, and I'm not sure about SHUTDOWN IMMEDIATE,
> although I suspect it flushes the DML update counts to disk before shutdown
> like NORMAL does. And of course a server crash or other instance crash
> would cause a similar loss.
>
> Something to check on anyway...
>
> Rich
>
>
>
>

--
http://www.freelists.org/webpage/oracle-l