【翻译自mos文章】当指定asm disk 为FRA时，11.2.0.3的dbua hang住

全栈程序员-站长 • 2022年1月25日下午9:00 • 未分类 • 阅读 44

大家好，又见面了，我是全栈君。

当指定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:

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

发布者：全栈程序员-站长，转载请注明出处：https://javaforall.net/116116.html原文链接：https://javaforall.net

【翻译自mos文章】当指定asm disk 为FRA时，11.2.0.3的dbua hang住

相关推荐

Android gif 录屏[通俗易懂]

什么是WPF_windows程序设计教程

Ubuntu下安装vscode_附近有安装etc的吗

字幕文件srt格式解析

WeakHashMap类

各大公司的大数据质量监控平台

发表回复