My Oracle Support Banner

Physical Standby Database Is Out Of Sync due to undo tablespace is offline at pdb level (Doc ID 2522709.1)

Last updated on FEBRUARY 04, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Information in this document applies to any platform.

Goal

NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the
Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual
environments, actual persons, living or dead, is purely coincidental and not intended in any manner.

For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:

Tablespace Names: UNDOTBS1,UNDOTBS2,UNDOTBS3,UNDOTBS4
ASM Disk Group Name: +DATAC1

**********

Problem Description
---------------------------------------------------
After rebuilding the standby database using active cloning MRP is waiting for gap that is looking for old log sequence.

Primary:-

INSTANCE_NAME HOST_NAME DATABASE_STATUS DATABASE_ROLE DB_UNIQUE_NAME STATUS
--------------- --------------- --------------- ---------------- --------------- ------
<instance_name>  <hostname> ACTIVE PRIMARY <db_unique_name> OPEN


  THREAD# MAX(SEQUENCE#)
---------- --------------
  4 76095
  3 73570

Standby:-

INSTANCE_NAME HOST_NAME DATABASE_STATUS DATABASE_ROLE DB_UNIQUE_NAME STATUS LOGINS
--------------- --------------- --------------- ---------------- --------------- --------------- ----------
<instance_name> <hostname> ACTIVE PHYSICAL STANDBY <db_unique_name> MOUNTED ALLOWED


  THREAD# MAX(SEQUENCE#)
---------- --------------
  3 73533
  4 76056

Alert Log error:-

Wed Jan 23 13:25:32 2019
FAL[client]: Failed to request gap sequence
 GAP - thread 3 sequence 66212-66311
 DBID 1319279401 branch 935632637
FAL[client]: All defined FAL servers have been attempted.
------------------------------------------------------------
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that's sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
----------------------------------------------------------
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.