fuzzy files on standby when applying incremental backups
From: HansP <Hans-Peter.Sloot_at_atosorigin.com>
Date: Tue, 13 Sep 2011 04:37:28 -0700 (PDT)
Message-ID: <8e14c62f-fd44-4e6c-bcd9-de242be4d009_at_eb1g2000vbb.googlegroups.com>
Db version 11.1.0.7.0 EE
OS : Linux
Date: Tue, 13 Sep 2011 04:37:28 -0700 (PDT)
Message-ID: <8e14c62f-fd44-4e6c-bcd9-de242be4d009_at_eb1g2000vbb.googlegroups.com>
Db version 11.1.0.7.0 EE
OS : Linux
I am playing around with standby and doing the scenario decribed in
section 11.10 of the Oracle Data Guard Concepts and Administration
manual.
The first time I play the scenario everything is fine.
But the second time something goes wrong.
The scenario (see section 11.10 of the manual for the exact steps).
1. duplicate data for standby 2. configure broker 3. ctas with nologging 4. determine nologging scn on standby 5. BACKUP INCREMENTAL FROM SCN <scn> DATABASE of primary 6. transfer backup to standby 7. catalog backup on standby 8. recover database noredo 9. open the database read only
If you do steps 3 to 9 for a 2nd time you will see the database
complaining about fuzzy files.
WARNING! Recovering data file 1 from a fuzzy file. If not the current
file
it might be an online backup taken without entering the begin backup
command.
Looks like a bug, doesn't it?
regards HansP Received on Tue Sep 13 2011 - 06:37:28 CDT