RE: DB Corruption

From: Powell, Mark D <mark.powell_at_eds.com>
Date: Fri, 1 Oct 2004 12:51:13 -0400
Message-ID: <564DE4477544D411AD2C00508BDF0B6A2133DF1F@usahm018.exmi01.exch.eds.com>

Is scn_to_timestamp a version 10 specific function? I do not find it in my version 9.2.0.5 test system.

• Mark D Powell --

-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Jamie Kinney Sent: Thursday, September 30, 2004 7:01 PM To: thump_at_cosmiccooler.org
Cc: oracle-l_at_freelists.org
Subject: Re: DB Corruption

David,

These views/tables each have CORRUPTION_CHANGE# in them. You could use the SCN_TO_TIMESTAMP function to get the time that the corruption was detected.

>From the docs, this column stores the "Change number at which the
logical corruption was detected. Set to 0 to indicate media corruption."

-Jamie

select scn_to_timestamp(1711819000) from dual;

SCN_TO_TIMESTAMP(1711819000)

---

30-SEP-04 03.57.42.000000000 PM On Thu, 30 Sep 2004 15:02:32 -0700 (PDT), David <thump_at_cosmiccooler.org> wrote:
> We just realized we have a corrupted db. An export revealed this. RMAN
> records corruption to v$backup_corruption in the db and
> rc_backup_corruption in the catalog.
>
> How can we tie that info to determine when the corruption occured so we
> can consider our options.
> --
> ..
> David
> --

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

Received on Fri Oct 01 2004 - 11:48:13 CDT