My Oracle Support Banner

PRIMARY_DB_UNIQUE_NAME column not populated in standby database (Doc ID 2491642.1)

Last updated on APRIL 03, 2020

Applies to:

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

Symptoms

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:

Database Unique Name:  BOSTON

***********

PRIMARY_DB_UNIQUE_NAME column value is null in v$database on the standby database, even though the MRP is running and the standby is in sync.

SQL> select name,open_mode,database_role,PRIMARY_DB_UNIQUE_NAME from v$database;

DB_UNIQUE_NAME   OPEN_MODE       DATABASE_ROLE      PRIMARY_DB_UNIQUE_NAME
--------- -------------------- ---------------- ------------------------------
BOSTON      READ ONLY WITH APPLY   PHYSICAL STANDBY

SQL> show parameter DB_UNIQUE_NAME

NAME       TYPE         VALUE
------ ------------------------------ ----------- ------------------------------
db_unique_name  string  BOSTON



Cause

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
Symptoms
Cause
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.