We needed to perform incomplete recovery on our Primary Database and
then had to open the database with the RESETLOGS parameter. This
worked fine but now our Standby Databases are out of sync with the
Primary (They are expecting log 16133 but the logs have been reset to
1 on the Primary Database).

Error message in the alert log is: ORA-16069: Archive Log standby
database activation identifier mismatch

Oracle Database Version 9.2.0.6 on Linux RHEL 3.

So do I have to re-create the Standby Databases (Copying across
datafiles etc etc) or is there are quicker way around this? I have
RTFMs but could find nothing in there about what to do after
performing "ALTER DATABASE OPEN RESETLOGS" command.

Thanks,

As far as I know, you need to rebuild the standby in this situation. You won't be able to apply any redo logs until the datafiles are all in sync
again. You can either use RMAN to do it or put the tablespaces in backup mode and copy the datafiles.


--- Rich


On 25 Mar 2007 12:45:43 -0700, "DoobITFC" <iandoob@yahoo.co.uk> wrote:

>We needed to perform incomplete recovery on our Primary Database and
>then had to open the database with the RESETLOGS parameter. This
>worked fine but now our Standby Databases are out of sync with the
>Primary (They are expecting log 16133 but the logs have been reset to
>1 on the Primary Database).
>
>Error message in the alert log is: ORA-16069: Archive Log standby
>database activation identifier mismatch
>
>Oracle Database Version 9.2.0.6 on Linux RHEL 3.
>
>So do I have to re-create the Standby Databases (Copying across
>datafiles etc etc) or is there are quicker way around this? I have
>RTFMs but could find nothing in there about what to do after
>performing "ALTER DATABASE OPEN RESETLOGS" command.
>
>Thanks,