Wrong logseq expected.
edited Oct 1, 2013 8:35PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 4 commentsAnswered
Hi,
I am facing an issue just after standby creation, i used a standby controlfile and a full backup+incr of 10.2.0.5 primary database.
For information we didn't use "duplicate for standby" command. When I start the recover archivelog are transferred but nothing is applied.
When I look in alert.log or mrp0.trc I have this messages:
In mrp0.trc:
Start recovery at thread 1 ckpt scn 620370 logseq 2 block 75981
In fact logseq 2 is from 2008 ! Does someone already facing this ?
I am facing an issue just after standby creation, i used a standby controlfile and a full backup+incr of 10.2.0.5 primary database.
For information we didn't use "duplicate for standby" command. When I start the recover archivelog are transferred but nothing is applied.
When I look in alert.log or mrp0.trc I have this messages:
FAL[client]: Failed to request gap sequence GAP - thread 1 sequence 2-101 DBID 2236488982 branch 665833900 FAL[client]: All defined FAL servers have been attempted.
In mrp0.trc:
Start recovery at thread 1 ckpt scn 620370 logseq 2 block 75981
In fact logseq 2 is from 2008 ! Does someone already facing this ?
0