ORA-16796: one or more properties could not be imported from the database [ID 358040.1]

最新推荐文章于 2023-06-11 21:01:32 发布

原创最新推荐文章于 2023-06-11 21:01:32 发布 · 8.6k 阅读

2 ·

CC 4.0 BY-SA版权

文章标签：

#database #properties #initialization #oracle #file

Oracle Data Guard 同时被 2 个专栏收录

38 篇文章

订阅专栏

Oracle Data Guard 全攻略

35 篇文章

订阅专栏

ORA-16796: one or more properties could not be imported from the database [ID 358040.1]

	Modified 29-MAY-2009 Type PROBLEM Status MODERATED

In this Document
  Symptoms
  Cause
  Solution

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.4
This problem can occur on any platform.

Symptoms

$ dgmgrl
DGMGRL for Linux: Version 10.2.0.1.0 - Production

Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys/<Password>
Connected.
DGMGRL> remove configuration
Removed configuration

DGMGRL> create configuration 'SHRUB' as
> primary database is 'SHRUB'
> connect identifier is 'SHRUB';
Configuration "SHRUB" created with primary database "SHRUB"

DGMGRL> add database 'WAGTAIL' as
> connect identifier is wagtail
> maintained as physical;
Error: ORA-16796: one or more properties could not be imported from the database

Failed.

Following error reported in the standby dataguard broker log

DG 2006-02-14-22:16:08 0 2 0 DMON: cannot open configuration file "/oracle/product/10.2.0/dbs/dr2wagtail.dat"

Cause

Noticed following file was not exists at standby server.

DG 2006-02-14-22:16:08 0 2 0 DMON: cannot open configuration file "/oracle/product/10.2.0/dbs/dr2wagtail.dat"

Solution

1) Stop the Data Guard Broker on both, the Primary and Standby Database using following Command:

SQL> alter system set dg_broker_start=false scope=both;

2) Remove the old Data Guard Broker Configuration Files specified by the Initialization Parameter 'DG_BROKER_CONFIG_FILE1|2' from Primary and Standby Site.

3) Start the Data Guard Broker on both Sites again:

SQL> alter system set dg_broker_start = true scope=both;

4) Recreate the Data Guard Broker Configuration