Josef Anwar Panerio, January 18, 2018 - 5:08 pm UTC
I checked the DBA_AUDIT_TRAILS and I have not found any traces the dbms_stats.delete_table_stats was executed, same as the table was re-created.
Josef Anwar Panerio, January 18, 2018 - 5:13 pm UTC
... the extracted data from audit trail was from the period there was values in num_rows and last_analyzed columns, to the date it was noticed it became null.
I also asked the application DBA if they did such commands, and said they have not performed dbms_stats.delete_table_stats, and the table was not re-created.
the only thing they did was dbms_stats.gather_table_stats but they manually terminated it as it took too long, as the table was too big.
January 19, 2018 - 11:56 am UTC
but they manually terminated it as it took too long
...sounds like we have a prime suspect for the cause
Josef Anwar Panerio, January 19, 2018 - 2:11 pm UTC
... does manually terminating the gather stats (dbms_stats) can cause the dba_tab_statistics num_rows and last_analyzed columns empty?
I simulate on my local machine (windows 7; DB version 11.2.0.4) and manually terminating the gather stats and it did not empty or null the previous table statistics.
January 19, 2018 - 3:22 pm UTC
I didn't think it would either. But it seems the most likely cause given other known reasons have been ruled out...