APPLIES TO:Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Information in this document applies to any platform.
While trying to start clusterware, ASM was not able to start. Errors in the CRS alert<hostname>.log contains:
and while trying to start using sqlplus, the following is displayed:
$ sqlplus / as sysasm
SQL*Plus: Release 22.214.171.124.0 Production on Mon Jun 26 08:30:34 2017
Copyright (c) 1982, 2013, Oracle. All rights reserved.
Connected to an idle instance.
Problems with hardware, ending up changing server, and kept previous spfile configuration for ASM
ASM instance had in the spfile, as displayed in the alert_+ASM3.log, the following information for cluster_interconnects:
$ ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
The /etc/hosts file had another entry for the private interface of this node, and not the old ip address of 172.xx.xx.107:
SOLUTION1) remove from spfile this entry
SQL> alter system reset cluster_interconnects SCOPE=SPFILE SID='*';
2) restart asm