Re: Tracking down NOLOGGING objects
- From: "Andrey.Kriushin" <Andrey.Kriushin@xxxxxxxx>
- To: pythianbrinsmead@xxxxxxxxx
- Date: Tue, 02 Sep 2008 13:27:22 +0400
Hi Mark,
Perfect point. Thanks!
Assuming that the one, not very familiar with the current operations on
the database and having no other input to identify NOLOGGING, still
tries to figure it out... And has a standby (as many of us do)...
-- Andrey
Mark Brinsmead wrote:
> But it /does/ track them at the /block/ level! If you have a physical
> standby, at least. Blocks affected by non-logged operations will
> manifest there as "corrupt" blocks. Something like an RMAN "BACKUP
> VALIDATE" will be sufficient to find them; they will be reported both
> in the RMAN output and a dictionary view (V$BLOCK_CORRUPTION maybe).
--
//www.freelists.org/webpage/oracle-l
Other related posts:
