Re: Change block tracking and corruption detection in 10g
- From: "Jared Still" <jkstill@xxxxxxxxx>
- To: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
- Date: Tue, 14 Nov 2006 16:56:38 -0800
This does not necessarily defeat the purpose of the block change tracking
file.
The change file is used to speed up backups. If there is some reason to
suspect
database corruption (say, following a disk failure) you probably want to do
a full scan.
What I do care about is running a backup, finding out there are bad blocks,
fixing the problem and then running another backup.
The backup window gets rather crowded at times.
This is dependent on several things, such as your backup system,
and the size of the database.
Jared
On 11/14/06, Allen, Brandon <Brandon.Allen@xxxxxxxxxxx> wrote:
Yes, but then you're running a full scan on your database, which defeats
the purpose of using the block change tracking file.
------------------------------
*From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto:
oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Jared Still
This can be used to check for corruptions
run {
allocate channel d1 type disk;
allocate channel d2 type disk;
backup check logical validate database;
release channel d1;
release channel d2;
}
Privileged/Confidential Information may be contained in this message or
attachments hereto. Please advise immediately if you or your employer do not
consent to Internet email for messages of this kind. Opinions, conclusions
and other information in this message that do not relate to the official
business of this company shall be understood as neither given nor endorsed
by it.
--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
Other related posts:
