Database Tutorials MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux 
Because the cluster_interconnects parameter is set incorrectly in the database instances on Exadata, one or more of the instances can be closed with the “kjzdattdlm: Can not attach to DLM” error. The same problem can be seen in ASM instances.
When trying to start instance, an error will be received as follows.
1 2 3 4 5 6 7 8 9 10 | [oracle@oradb01 ~]$ srvctl start instance -i ORCL2 -d ORCL PRCR-1013 : Failed to start resource ora.orcl.db PRCR-1064 : Failed to start resource ora.orcl.db on node oradb02 CRS-5017: The resource action "ora.orcl.db start" encountered the following error: ORA-03113: end-of-file on communication channel Process ID: 0 Session ID: 0 Serial number: 0 . For details refer to "(:CLSN00107:)" in "/u01/app/11.2.0.3/grid/log/oradb02/agent/crsd/oraagent_oracle/oraagent_oracle.log". CRS-2674: Start of 'ora.orcl.db' on 'oradb02' failed |
It is possible to see the following errors in the trace file specified in the error:
kjzdattdlm: Can not attach to DLM (LMON up=[TRUE], DB mounted=[FALSE]).
In this case, it is necessary to set the cluster_interconnects parameter to be the “interconnect ip” for all instances in the database and restart the database.
If private network server IPs are as follows;
1 2 3 4 5 6 7 8 | 192.168.10.1 orcldb01-priv 192.168.10.2 orcldb02-priv 192.168.10.3 orcldb03-priv 192.168.10.4 orcldb04-priv 192.168.10.5 orcldb05-priv 192.168.10.6 orcldb06-priv 192.168.10.7 orcldb07-priv 192.168.10.8 orcldb08-priv |
We can set the cluster_interconnects parameter for the intances as follows:
1 2 3 4 5 6 7 8 | alter system set cluster_interconnects='192.168.10.1' scope=spfile sid='ORCL1'; alter system set cluster_interconnects='192.168.10.2' scope=spfile sid='ORCL2'; alter system set cluster_interconnects='192.168.10.3' scope=spfile sid='ORCL3'; alter system set cluster_interconnects='192.168.10.4' scope=spfile sid='ORCL4'; alter system set cluster_interconnects='192.168.10.5' scope=spfile sid='ORCL5'; alter system set cluster_interconnects='192.168.10.6' scope=spfile sid='ORCL6'; alter system set cluster_interconnects='192.168.10.7' scope=spfile sid='ORCL7'; alter system set cluster_interconnects='192.168.10.8' scope=spfile sid='ORCL8'; |
Then you’ll have to restart the database.
1 2 | srvctl stop database -d ORCL srvctl start database -d ORCL |
