ORA-15204: database version 11.2.0.4.0 is incompatible with diskgroup DATA

0    784    2

Tags:

👉 本文共约1090个字,系统预计阅读时间或需5分钟。

现象

在执行rman还原控制文件时,报错了,“ORA-15204: database version 11.2.0.4.0 is incompatible with diskgroup DATA”:

分析

源库是11.2.0.3,新库是12.2.0.1,需要迁移升级。

所以,问题是参数的“DATABASE_COMPATIBILITY”不兼容。

解决

另外,可以直接修改compatible.rdbms属性,但是,我执行的时候卡住了,时间紧迫,我就不深究了:

本人提供Oracle、MySQL、PG等数据库的培训和考证业务,私聊QQ646634621或微信db_bao,谢谢!

参考

ORA-15204: database version 11.2.0.1.0 is incompatible with diskgroup DATA (Doc ID 1487320.1)

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:

Diskgroup used is +DATA_PROD

Customer was having a problem setting up a data guard standby database (11.2.0.3) using duplicate from active database (11.2.0.1) on ASM:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 08/23/2012 11:43:52
RMAN-05501: aborting duplication of target database
RMAN-06136: ORACLE error from auxiliary database: ORA-00200: control file could not be created
ORA-00202: control file: '+data_prod'
ORA-17502: ksfdcre:4 Failed to create file +data_prod
ORA-15001: diskgroup "DATA_prod" does not exist or is not mounted
ORA-15204: database version 11.2.0.1.0 is incompatible with diskgroup DATA_prod

CAUSE

The reason that the duplicate is failing with the error reported :

database version 11.2.0.1.0 is incompatible with diskgroup DATA_prod

is because the diskgroup DATA_prod has a value for compatibility of 11.2.0.3.0
and
the database version has a compatible version of 11.2.0.0.0

SOLUTION

The problem is that the target ASM instance has a (default) compatibility parameter that will not work with your source data. Compatibility settings on an ASMdiskgroup are set upon ASM diskgroup creation.

  1. ensure that you understand where your Clusterware voting disk are, and how they may be affected by dropping your existing ASM DATA_prod diskgroup. Once you are ready to drop your existing ASM DATA_prod diskgroup (losing everything stored on it) do the following:

    As oracle in ASM, drop your existing ASM DATA_prod diskgroup:

  1. to recreate your ASM DATA_prod diskgroup with compatible = 11.2.0.0.0:

As oracle in ASM, create the new diskgroup

标签:

头像

小麦苗

学习或考证,均可联系麦老师,请加微信db_bao或QQ646634621

您可能还喜欢...

发表回复

您的电子邮箱地址不会被公开。 必填项已用*标注

4 × 1 =

 

嘿,我是小麦,需要帮助随时找我哦
  • 18509239930
  • 个人微信

  • 麦老师QQ聊天
  • 个人邮箱
  • 点击加入QQ群
  • 个人微店

  • 回到顶部
返回顶部