When you try to create an 11.2 database instance on 18c Grid Infrastructure using DBCA or “srvctl add database” command, instance registration fails with CRS-0245 as below. Modify the IP address at network layer, DNS and /etc/hosts file to reflect the change or modify the MAC address at network layerĪbove change can be done in rolling method, one node at a time.Ĭhange IP address at OS layer.If the change is only public IP or VIP address and the new ones are still in the same subnet, same interface, or if the change is only for public IP MAC address, IP/interface/subnet/netmask all remain the same, nothing needs to be done at clusterware layer, all changes need to be done at OS layer to reflect the change. Once the DB Home addition is complete, use srvctl to check the status of registered DB and instances and add them if required.Changing public IP or VIP only without changing interface, subnet or netmask or changing MAC address only without changing anything else addNode.sh -silent 'CLUSTER_NEW_NODES='Ĩ. Will explain the impact of this error in the subsequent steps.ĥ.

PRVF-5431 : Oracle Cluster Voting Disk configuration check failed PRVF-5449 : Check of Voting Disk location “ORCL:DISK6(ORCL:DISK6)” failed on the following nodes: If possible, redirect the output of above to some file so that it can be reviewed and any issues reported can be rectified.įor this case, since the OCR and Voting disk resides on ASM and ASMLIB is in use, the most impacting errors were cluvfy stage -pre nodeadd -n node2 -verbose Run the Run the Cluster Verification Utility. Now starts the actual step of adding node. Perform the similar for Database Home as well : /u01/oracle/product/11.2/oui/bin/runInstaller -updateNodeList ORACLE_HOME=/u01/oracle/product/11.2 CLUSTER_NODES=node1 -silent -localĤ. Clear the inventory for reimaged host for GI and DB Homes.įrom the surviving node, execute : /u01/grid/11.2/oui/bin/runInstaller -updateNodeList ORACLE_HOME=/u01/grid/11.2 'CLUSTER_NODES=node1' CRS=TRUE -silent -local Remove the VIP information of reimaged host from OCR Execute the following on existing node : To verify the success of above step, execute “olsnodes” on surviving node and the reimaged host shouldnot show up in list.Ģ. Clearing the OCR entries for re-imaged host. – After the OS reinstall, user equivalence has been set and all required packages have been installed along with setup of ASMLIBġ. – Voting disk and OCR are on ASM( ASMLIB is being used to manage the shared disks )

We need to remove them first and then perform a node addition. In such cases, just a normal node addition would not help since the OCR still contain the references of original node. There could be a scenario of node crash due to OS/hardware issues and a reinstall/reimage of the same.

Runinstaller updatenodelist failed