RE: How can I get the BBED password?
- From: "Parker, Matthew" <matthewp@xxxxxxxxxx>
- To: <Slava.Zayarny@xxxxxxx>, <Oracle-L@xxxxxxxxxxxxx>
- Date: Thu, 14 Apr 2005 19:14:31 -0700
We use monitors on v$database_block_corruption to see corruption that =
RMAN does not report in it's logs, but does always appear to report in =
the view, which is really rows stored in the controlfile.
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx =
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Slava Zayarny
Sent: Thursday, April 14, 2005 6:56 AM
To: Oracle-L@xxxxxxxxxxxxx
Cc: breitliw@xxxxxxxxxxxxx
Subject: Re: How can I get the BBED password?
Wolfgang,
I have recently been looking at what types of corruption RMAN notices
and how it reports them. I used dd and BBED to experiment with =3D
intentional
block corruption in 9.2.0.6/HP-UX 11.11.
I have not had the time to conclude all the trials I want but BBED only =
=3D
marks=3D20
a block "FRACTURED" as seen in V$DATABASE_BLOCK_CORRUPTION
after RMAN's "BACKUP VALIDATE CHECK LOGICAL DATABASE" is run. =3D20
For this type of corruption RMAN does NOT fail with an error after =3D
backup=3D20
validation: it logs an entry to the alert log and inserts rows into=3D20
V$DATABASE_BLOCK_CORRUPTION and V$BACKUP_CORRUPTION. Alert log would =
=3D
show
such intentionally fractured block in the alert log as:
"Bad header found during backing up datafile"
without the usual "ORA-XXX".
RMAN behaved differently in a recent case where corrupted block was
reported in alert log as:
"Bad header found during buffer read"
In that case RMAN failed with "ORA-19566: exceeded limit of 0 corrupt =
=3D
blocks for file".
It was also reported with "ORA-XXX" into the alert log. Unfortunately, =
=3D
I don't have=3D20
details on how it was reported in V$DATABASE_BLOCK_CORRUPTION.
I think it's important to know what kind of corruption RMAN can and =3D
cannot
report without the need to add auto monitoring of the alert log beyond =
=3D
the standard
"ORA-XXX" strings.
What I want to figure out conclusively by simulation is how RMAN reports =
=3D
the=3D20
other four types of corruption (as seen in V$DATABASE_BLOCK_CORRUPTION):
ALL ZERO, CHECKSUM, CORRUPT, LOGICAL
I will share my findings when I'm done, but in the meantime, I would =3D
welcome
your comments if you have any.
Cheers,
Slava Zayarny
Oracle DBA
-----------------------------------------------
Date: Wed, 13 Apr 2005 12:43:24 -0600
From: Wolfgang Breitling <breitliw@xxxxxxxxxxxxx>
Subject: Re: How can I get the BBED password?
I have used it to deliberately corrupt a block to find out how RMAN=3D20
report block corruptions. Of course there are other ways to corrupt=3D20
blocks but it seemed like a good excuse to build and use bbed.
Guerra, Abraham J wrote:
> Hello Tanel,
>=3D20
> Have you used the utility? If so, did you discover the password or =
=3D
=3D3D
> somebody else told it to you?
>=3D20
> Thanks.
>=3D20
> Abraham
>=3D20
--=3D20
Regards
Wolfgang Breitling
Centrex Consulting Corporation
www.centrexcc.com
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
