What causes a last_analyzed date of 00-000-00?

From: <Cherie_Machler_at_gelco.com>
Date: Tue, 29 May 2001 12:31:16 -0700
Message-ID: <F001.003127BE.20010529122457@fatcity.com>

I just migrated a database from 7.3.4 to 8.1.7.1 on Sun Solaris 2.6. I do not believe that there were any statistics on this database before it was migrated.

During the process of the migration, I followed the instruction and switched optimizer_mode from rule to choose.

After it was upgraded, there were some pockets of extremely poor performance. On a hunch, I looked at the last_analyzed date of all my non-system tables. I was surprised to see that about a third of the tables seemed to have "junk" statistics in existence with a last_analyzed date of 00-000-00.

What might have caused these statistics to be out there? I doubt that we had pre-existing statistics because I've had them prior to upgrades and afterwards they've continued to have the same valid dates on them as they had before the upgrade.

Anybody seen these "junk" statistics before? I got rid of them and everything was fine but I'd like to prevent them from being created the next time that we do a 7.3.4 to 8.1.7.1 upgrade.

Any light anyone can shed is appreciated.

Thanks,

Cherie

--

Please see the official ORACLE-L FAQ: http://www.orafaq.com
--

Author:
INET: Cherie_Machler_at_gelco.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------

To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Tue May 29 2001 - 14:31:16 CDT