RE: Re: Oracle XE Corruption

  • From: "Daniel Fink" <daniel.fink@xxxxxxxxxxxxxx>
  • To: Oracle-L@xxxxxxxxxxxxx
  • Date: Tue, 24 Aug 2010 19:10:41 +0000

"Probably less time than it takes to replace the differential in my car.  :)"
Would that be on race day or between races?

smon_scn_time table is the table that Oracle uses to keep track of the 
relationship between scns and timestamps for flashback operations. It contains 
up to 5 uptime days of data (unless you have hacked it...but that is another 
story and NOT to be done on a PRODUCTION database!). It is relatively small 
(thousands of rows, not millions) so it should not take long to rebuild it...if 
it can be rebuilt. Since this table is constantly inserted/updated by smon, the 
window may be small, but the small size of the table should work for your 
benefit. I've never rebuilt the index, so I can't say for certain.

As smon_scn_time is owned by SYS, it can't be exported. However, you could try 
a rebuild on a NON-PRODUCTION system first.

------- Original Message -------
On 8/24/2010 6:50 PM Jared Still wrote:
On Tue, Aug 24, 2010 at 11:40 AM, Evan Pettrey <jepettrey@xxxxxxxxx> wrote:

The ''smon_scn_time_tim_idx' index is found in the "smon_scn_time" table.
Probably less time than it takes to replace the differential in my car.  :)

More seriously though, it really depends on the entire environment:
* HW
* how busy is it
* storage system capacity
* etc, etc, etc.

Export the table (if possible) and import it to a database on a development
or test server. --

Other related posts: