DBCA Requires That All RAC Nodes to be Accessible When Adding A New Instance
(Doc ID 473287.1)
Last updated on MARCH 07, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.3 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Currently, Database Configuration Assistant (DBCA) requires that all nodes are accessible when adding a new instance to an existing Real Application Clusters (RAC) database.
Such as in a 3-node cluster / currently running 2-instance Cluster DB:
- the local instance is running - invoke DBCA
- the remote instance is stopped
- choose Real Application Clusters Database
- choose Instance Management
- choose 'Add an Instance'
- DBCA lists the available databases as active (at least one instance running) or inactive
- fill in sysdba username / password, click NEXT
- list of nodes and instances ... DBCA lists ACTIVE, INACTIVE for the instances respectively
- as long as one instance is active, you can click through
- then name the new instance and the node upon which it will run
- pop-up error box states:
PRKC-1030: Error checking accessibility for node node2, the operation has failed unexpectedly
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document