【翻译自mos文章】当指定asm disk 为FRA时,11.2.0.3的dbua hang住
2016-01-30 14:00
323 查看
当指定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
相关文章推荐
- 中医教你如何调理女性内分泌失调
- 排序2
- Linux sed 批量替换字符串和更多用法
- react-native:unexpected token
- 嵌入式Linux之相关网络环境的搭建
- 机器视觉开源代码集合
- 大并发服务器架构 && 大型网站架构演变
- 二叉树遍历解析
- POJ1182带权并查集
- 图片由小图放大裁剪至全屏显示大图,Google Photos 点击图片预览的效果
- 理解 bashrc 和 profile
- CTCall
- JSTL 中的十二个核心标签
- CTCallCenter
- orcale链接问题
- 进制转换:十六进制,二进制,八进制的互相转换
- CTCarrier
- CTSubscriber
- hdu 2161 Primes
- Java位操作的一个例子