【翻译自mos文章】当指定asm disk 为FRA时,11.2.0.3的dbua hang住
2015-07-10 08:04
537 查看
当指定asm disk 为FRA时,11.2.0.3的dbua hang住
来源于:
11.2.0.3 DBUA Hangs While Specifying ASM Disk To FRA (文档 ID 1427179.1)
适用于:
Oracle Database Upgrade Assistant - Version 10.2.0.1 and later
Oracle Server - Standard Edition - Version 10.2.0.1 and later
Oracle Server - Enterprise Edition - Version 10.2.0.1 and later
Information in this document applies to any platform.
症状:
DBUA hangs if ASM disk is specified to FRA (Fast Recovery Area).
DBUA trace.log shows the following errors:
原因:
While moving FRA to ASM disk, as a part of validation, DBUA compares disk group and RDBMS compatibilty. The validation fails with null pointer exception because the compatible parameter was not set in the pfile (or spfile) of the source database.
解决方案:
Set the compatible parameter in the pfile of the source database as shown below and rerun DBUA.
where x.x.0.0 is the value of the compatible parameter set in the source database.
For example, if the source database is 10.2.0.5 then it could be set as:
来源于:
11.2.0.3 DBUA Hangs While Specifying ASM Disk To FRA (文档 ID 1427179.1)
适用于:
Oracle Database Upgrade Assistant - Version 10.2.0.1 and later
Oracle Server - Standard Edition - Version 10.2.0.1 and later
Oracle Server - Enterprise Edition - Version 10.2.0.1 and later
Information in this document applies to any platform.
症状:
DBUA hangs if ASM disk is specified to FRA (Fast Recovery Area).
DBUA trace.log shows the following errors:
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException at oracle.sysman.assistants.util.InstallUtils.compareVersion(InstallUtils.java:266)---注意此行 at oracle.sysman.assistants.util.asm.ASMUtils.validateDiskGroup(ASMUtils.java:1154) at oracle.sysman.assistants.dbma.backend.CloneValidator.isDiskGroupCompatible(CloneValidator.java:654) at oracle.sysman.assistants.dbma.backend.CloneValidator.isRecoveryAreaValidated(CloneValidator.java:431) at oracle.sysman.assistants.dbma.ui.OracleBasePage.doNext(OracleBasePage.java:956)
原因:
While moving FRA to ASM disk, as a part of validation, DBUA compares disk group and RDBMS compatibilty. The validation fails with null pointer exception because the compatible parameter was not set in the pfile (or spfile) of the source database.
解决方案:
Set the compatible parameter in the pfile of the source database as shown below and rerun DBUA.
compatible=x.x.0.0
where x.x.0.0 is the value of the compatible parameter set in the source database.
For example, if the source database is 10.2.0.5 then it could be set as:
compatible=10.2.0 or compatible=10.2.0.5
相关文章推荐
- n每个计数的概率和发生骰子--动态规划
- PHP情人:p十几天来学习hp第一天
- Spark:Yarn-cluster和Yarn-client区别与联系
- java基础——static 关键字小节
- 创业中,感受书本和现实的距离——北漂18年(16)
- 【剑指Offer学习】【面试题52:构建乘积数组】
- 字典转模型&加载xib&加载plist
- 【翻译自mos文章】当点击完 finish按钮后,dbca 或者dbua hang住
- @property的参数说明
- android值传递
- Xcode中常用的快捷键
- 在 RHEL/CentOS 7.0 中安装 LAMP
- IntSet() DEMO
- cong
- Linux 进程关系
- scala 单元测试
- 【翻译自mos文章】使用dbua升级时,需要手工设置CLUSTER_DATABASE参数么?
- Qt中文支持和文件读写
- Android Studio无法下载sdk问题
- 一个短小的JS函数,用来得到仅仅包含不重复元素的数组