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

本文详细介绍了如何解决Oracle Server Enterprise Edition版本10.2.0.1到10.2.0.4中出现的ORA-16796错误,包括停止DataGuardBroker、移除旧配置文件、重新启动配置以及重建配置等步骤。

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


Modified29-MAY-2009TypePROBLEMStatusMODERATED

In this Document
Symptoms
Cause
Solution


This document is being delivered to you via Oracle Support'sRapid 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

Copyright (c) 2000, 2005, Oracle. All rights reserved.

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

Noticedfollowing file was not exists atstandby 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


------------------------------------------------------------------------------

### ORA - 15032: not all alterations performed 此错误表明并非所有的更改操作都已执行。在引用[1]中,执行 `alter diskgroup archdg online disks in failgroup fg1` 语句时出现了该错误,同时伴随其他如 `ORA - 15130`、`ORA - 15335` 等错误,可能是磁盘组存在元数据损坏等问题。解决此问题可按以下步骤: 1. 检查磁盘组的状态,确保没有正在进行的操作,如卸载磁盘组等。 2. 检查磁盘组的元数据是否损坏,若存在损坏,可能需要进行修复操作。 3. 确认 `COMPATIBLE.ASM` 属性设置为 11.1 者更高,因为某些特性依赖此设置。 ```sql -- 查看 COMPATIBLE.ASM 属性 SELECT name, value FROM v$asm_attribute WHERE group_number = (SELECT group_number FROM v$asm_diskgroup WHERE name = 'ARCHDG'); -- 修改 COMPATIBLE.ASM 属性 ALTER DISKGROUP archdg SET ATTRIBUTE 'compatible.asm' = '11.1'; ``` ### ORA - 15242: could not set attribute compatible.rdbms 根据引用[2],`compatible.asm` 和 `compatible.rdbms` 是 ASM 磁盘组的兼容性属性,`compatible.rdbms` 处理数据库实例(磁盘组的使用者)的兼容性。此错误表示无法设置 `compatible.rdbms` 属性,可能是当前设置不满足操作要求。解决方法如下: 1. 确认当前 `compatible.rdbms` 属性值,确保其符合操作要求。 2. 若要设置 `compatible.rdbms` 属性,需保证数据库实例的版本支持该值。 ```sql -- 查看当前 compatible.rdbms 属性值 ASMCMD [+DATA/rac] > lsattr -G DATA -l | grep compatible.rdbms -- 修改 compatible.rdbms 属性 ALTER DISKGROUP data SET ATTRIBUTE 'compatible.rdbms' = '11.2.0.0.0'; ``` ### ORA - 15137: The ASM cluster is in rolling patch state 该错误提示 ASM 集群处于滚动补丁状态,在此状态下某些操作可能会受到限制。解决此问题可按以下步骤: 1. 等待滚动补丁操作完成,确保 ASM 集群恢复正常状态。 2. 检查滚动补丁操作的日志,确认是否存在异常情况。 3. 若滚动补丁操作失败,可能需要手动清理相关状态重新执行补丁操作。
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值