APPLIES TO:Oracle Cloud Infrastructure - Database Service - Version N/A and laterOracle 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. SYMPTOMSWhile trying to start clusterware, ASM was not able to start. Errors in the CRS alert<hostname>.log contains: 2017-06-25 22:23:30.928: and while trying to start using sqlplus, the following is displayed: SQL*Plus: Release 11.2.0.4.0 Production on Mon Jun 26 08:30:34 2017 Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to an idle instance. SQL> startup CHANGESProblems with hardware, ending up changing server, and kept previous spfile configuration for ASM CAUSEASM instance had in the spfile, as displayed in the alert_+ASM3.log, the following information for cluster_interconnects: /file: alert_+ASM3.log
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*.cluster_interconnects='172.xx.xx.107' by issuing: SQL> alter system reset cluster_interconnects SCOPE=SPFILE SID='*'; System altered. SQL> 2) restart asm
|