Archive apply in standby fails ORA-19909 error.
Problem Details
Problem Statement
Archive apply fails in standby with ORA error related to incarnation
Applicable Error Code
ORA-00283 ,ORA-19909
Affected Versions
Should be version independent
Affected Platforms
Platform Independent
Description
Dbvisit fails to apply logs to the standby with the following error:
ORA-00283: recovery session canceled due to errors ORA-19909: datafile 1 belongs to an orphan incarnation
This may happen with a newly created standby, or with a standby that was recreated following activation.
A likely reason is that database files that belong to the previous incarnation have been left in FRA which causes Oracle to reset incarnation.
-
Remove old files from FRA. Check date subdirectories.
-
Reset incarnation using RMAN. See the attached note.
Primary: [dbvlab01:oracle:proddb]$ rman target / Recovery Manager: Release 11.2.0.4.0 - Production on Tue May 2 10:12:30 2017 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. connected to target database: PRODDB (DBID=493147293) RMAN> list incarnation; using target database control file instead of recovery catalog List of Database Incarnations DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time ------- ------- -------- ---------------- --- ---------- ---------- 1 1 PRODDB 493147293 PARENT 1 24-AUG-13 2 2 PRODDB 493147293 PARENT 925702 21-SEP-16 3 3 PRODDB 493147293 CURRENT 4151191593857 27-APR-17 Standby: [dbvlab03:oracle:proddb]$ rman target / Recovery Manager: Release 11.2.0.4.0 - Production on Tue May 2 10:12:41 2017 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. connected to target database: PRODDB (DBID=493147293, not open) RMAN> list incarnation; using target database control file instead of recovery catalog List of Database Incarnations DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time ------- ------- -------- ---------------- --- ---------- ---------- 1 1 PRODDB 493147293 PARENT 1 24-AUG-13 2 2 PRODDB 493147293 PARENT 925702 21-SEP-16 3 3 PRODDB 493147293 ORPHAN 4151191593857 27-APR-17 4 4 PRODDB 493147293 CURRENT 4151191636948 27-APR-17
Check the incarnation in both primary and secondary reset the incarnation to current one in the primary on the standby
On primary: 3 3 PRODDB 493147293 CURRENT 4151191593857 27-APR-17 On standby: 4 4 PRODDB 493147293 CURRENT 4151191636948 27-APR-17 Connect to standby and run the below rman target / RMAN> reset database to incarnation 3;
Anna MacNaughtan March 31, 2015 12:25
Comments