DBCA errors when cluster_interconnect is set

Asset ID:	1-72-1373591.1
Update Date:	2012-05-24
Keywords:

Solution Type Problem Resolution Sure

Solution 1373591.1 : DBCA errors when cluster_interconnect is set

Applies to:

Exadata Database Machine X2-2 Full Rack - Version Not Applicable and later
Oracle Exadata Hardware - Version 11.2.0.1 and later
Information in this document applies to any platform.

Symptoms

If the following advanced parameter is set from DBCA, you may see errors during the database creation:

cluster_interconnect

ORA-27504: IPC error creating OSD content
ORA-27300: OS system dependent operation: if_not_found failed with status: 0
ORA-27301: OS failure message; Error 0
ORA-27302: failure eoccurred at: skgxpvaddr9
ORA-27303: additional information: requested interface 192.168.10.4 not found. Check output from ifconfig command

Note: you would have had to explicitly gone into the advanced options and set this parameter - it is not set by default.

Cause

The problem happens because cluster_interconnect parameter is set to a specific IP. That IP is valid only for one node, but DBCA will use it for all others, and indeed, it will fail.

EXAMPLE: The correct setting on a spfile for cluster_interconnect is:

+ASM1.cluster_interconnect=192.168.10.1
+ASM2.cluster_interconnect=192.168.10.2
+ASM3.cluster_interconnect=192.168.10.3
+ASM4.cluster_interconnect=192.168.10.4

But these settings can't be made using DBCA through the GUI.

The database is created in cluster mode, with all the threads for the other nodes, but it fails when trying to bring the db and using the wrong value for cluster_interconnect.

Solution

The options are:

1. The database should have been created even with the error message, so we can modify the spfile of the database setting the right values:

EXAMPLE:

alter system set cluster_internconnect='192.168.10.1' scope=spfile sid='+ASM1';
alter system set cluster_internconnect='192.168.10.2' scope=spfile sid='+ASM2';
alter system set cluster_internconnect='192.168.10.3' scope=spfile sid='+ASM3';
alter system set cluster_internconnect='192.168.10.4' scope=spfile sid='+ASM4';

After this, it should be possible to start the instances.

2. Or on DBCA, don't specify cluster interconnect at creation time. Let the database be created, then modify the spfile afterwards. This is the preferred method.

Attachments

This solution has no attachment