Bug 26360024: Runinstaller not listing node name in proper order (Doc ID 2282653.1)

Last updated on JULY 02, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Information in this document applies to any platform.

Symptoms

DBCA is not listing node number properly

 

oracle@xxxxxxl21:/oracle/GRID/12102/bin> ./olsnodes -n
xxxxxxl21 1
xxxxxxl22 2
xxxxxxl23 3

[OUISetupDriver.JobExecutorThread] [ 2017-06-25 18:38:25.294 PDT ]
[ClusterInfo.getLocalNodeName:272] output.length=1
[OUISetupDriver.JobExecutorThread] [ 2017-06-25 18:38:25.294 PDT ]
[ClusterInfo.getLocalNodeName:276] output[0]=xxxxxxl21
[OUISetupDriver.JobExecutorThread] [ 2017-06-25 18:38:25.297 PDT ]
[Cluster.isSharedPath:1090] NodeList=[xxxxxxl21, xxxxxxl23, xxxxxxl22]
<<------
[OUISetupDriver.JobExecutorThread] [ 2017-06-25 18:38:25.297 PDT ]
[Cluster.isSharedPath:1115] pathName=/oracle/TST/12102/inventory
dirPath = /oracle/TST/12102/inventory
[OUISetupDriver.JobExecutorThread] [ 2017-06-25 18:38:25.297 PDT ]
[UnixSystem.checkSharedFileSystemPath:1683] dirPath=/oracle/TST/12102
[OUISetupDriver.JobExecutorThread] [ 2017-06-25 18:38:25.297 PDT ]
[UnixSystem.checkSharedFileSystemPath:1688]
pathName=/oracle/TST/12102/inventory
tempFile=CFSFileName14984411052975633063049194809050.tmp

File_name :: oraInstall2017-06-25_06-29-18PM.out

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms