【翻譯自mos文章】當指定asm disk 為FRA時，11.2.0.3的dbua hang住，11.2.0.3dbua

【翻譯自mos文章】當指定asm disk 為FRA時，11.2.0.3的dbua hang住，11.2.0.3dbua

當指定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.NullPointerExceptionat 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.0orcompatible=10.2.0.5