My Oracle Support Banner

Solaris Cluster - After Rebooting Node 2 Fails To Start SCDPMD and cldev status returns cldev: (C173017) Could not initialize CCR. (Doc ID 2642206.1)

Last updated on MARCH 02, 2020

Applies to:

Solaris Cluster - Version 3.3 U2 to 4.4 [Release 3.3 to 4.4]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)

Symptoms

# cldevice status  (both nodes)
cldevice: (C173017) Could not initialize CCR.

-

  

  

-

Node2 messages:

 

Feb 23 03:58:30 Node2 cl_runtime: [ID 308814 kern.warning] WARNING: CCR: Updating table dpm_status_table failed to startup on node Node1 for cl
uster global.
Feb 23 03:58:30 Node2 Cluster.CCR: [ID 353467 daemon.warning] libscdpm: CCR exception for dpm_status_table table
Feb 23 03:58:30 Node2 cl_runtime: [ID 308814 kern.warning] WARNING: CCR: Updating table dpm_status_table failed to startup on node Node1 for cl
uster global.

Feb 23 03:59:54 Node2 cl_runtime: [ID 308814 kern.warning] WARNING: CCR: Updating table dpm_status_table failed to startup on node Node1 for cl
uster global.

(snip)

Feb 23 04:04:03 Node2 genunix: [ID 672855 kern.notice] syncing file systems...
Feb 23 04:04:03 Node2 genunix: [ID 904073 kern.notice] done
Feb 23 04:04:15 Node2 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.11 Version 11.3 64-bit
Feb 23 04:04:15 Node2 genunix: [ID 748049 kern.notice] Copyright (c) 1983, 2018, Oracle and/or its affiliates. All rights reserved.

Feb 23 04:05:04 Node2 cl_runtime: [ID 537175 kern.notice] NOTICE: CMM: Node Node1 (nodeid: 1, incarnation #: 1573192653) has become reachable.
Feb 23 04:05:04 Node2 cl_runtime: [ID 525628 kern.notice] NOTICE: CMM: Cluster has reached quorum.
Feb 23 04:05:04 Node2 cl_runtime: [ID 377347 kern.notice] NOTICE: CMM: Node Node1 (nodeid = 1) is up; new incarnation number = 1573192653.
Feb 23 04:05:04 Node2 cl_runtime: [ID 377347 kern.notice] NOTICE: CMM: Node Node2 (nodeid = 2) is up; new incarnation number = 1582410903.
Feb 23 04:05:04 Node2 cl_runtime: [ID 108990 kern.notice] NOTICE: CMM: Cluster members: Node1 Node2.
Feb 23 04:05:04 Node2 cl_runtime: [ID 279084 kern.notice] NOTICE: CMM: node reconfiguration #17 completed.
Feb 23 04:05:04 Node2 cl_runtime: [ID 499756 kern.notice] NOTICE: CMM: Node Node2: joined cluster.

Feb 23 04:05:06 Node2 Cluster.CCR: [ID 470336 daemon.notice] /usr/cluster/bin/scgdevs: DID instance cache was not initialized, failover performance may
be impacted.

Feb 23 04:05:11 Node2 Cluster.CCR: [ID 353467 daemon.warning] libscdpm: CCR exception for dpm_status_table table
Feb 23 04:05:11 Node2 Cluster.CCR: [ID 386282 daemon.error] ccr_initialize failure
Feb 23 04:05:11 Node2 Cluster.CCR: [ID 353467 daemon.warning] libscdpm: CCR exception for dpm_status_table table
Feb 23 04:05:11 Node2 Cluster.CCR: [ID 386282 daemon.error] ccr_initialize failure

Feb 23 04:05:11 Node2 Cluster.CCR: [ID 353467 daemon.warning] libscdpm: CCR exception for dpm_status_table table
Feb 23 04:05:11 Node2 Cluster.CCR: [ID 386282 daemon.error] ccr_initialize failure
Feb 23 04:05:12 Node2 Cluster.CCR: [ID 353467 daemon.warning] libscdpm: CCR exception for dpm_status_table table
Feb 23 04:05:12 Node2 Cluster.CCR: [ID 386282 daemon.error] ccr_initialize failure
Feb 23 04:05:12 Node2 svc.startd[14]: [ID 748625 daemon.error] system/cluster/scdpm:default failed repeatedly: transitioned to maintenance (see 'svcs -x
v' for details)
Feb 23 04:05:20 Node2 genunix: [ID 390243 kern.info] Creating /etc/devices/devid_cache
Feb 23 04:05:47 Node2 Cluster.CCR: [ID 353467 daemon.warning] libscdpm: CCR exception for dpm_status_table table
Feb 23 04:06:02 Node2 last message repeated 1 time

Feb 23 04:06:07 Node2 Cluster.CCR: [ID 353467 daemon.warning] libscdpm: CCR exception for dpm_status_table table
Feb 23 04:07:08 Node2 last message repeated 1 time
Feb 23 04:07:08 Node2 Cluster.CCR: [ID 386282 daemon.error] ccr_initialize failure
Feb 23 04:07:08 Node2 Cluster.CCR: [ID 353467 daemon.warning] libscdpm: CCR exception for dpm_status_table table
Feb 23 04:07:08 Node2 Cluster.CCR: [ID 386282 daemon.error] ccr_initialize failure
Feb 23 04:07:09 Node2 Cluster.CCR: [ID 353467 daemon.warning] libscdpm: CCR exception for dpm_status_table table
Feb 23 04:07:09 Node2 Cluster.CCR: [ID 386282 daemon.error] ccr_initialize failure
Feb 23 04:07:09 Node2 Cluster.CCR: [ID 353467 daemon.warning] libscdpm: CCR exception for dpm_status_table table
Feb 23 04:07:09 Node2 Cluster.CCR: [ID 386282 daemon.error] ccr_initialize failure
Feb 23 04:07:09 Node2 svc.startd[14]: [ID 748625 daemon.error] system/cluster/scdpm:default failed repeatedly: transitioned to maintenance (see 'svcs -x
v' for details)
Feb 23 04:07:45 Node2 Cluster.CCR: [ID 353467 daemon.warning] libscdpm: CCR exception for dpm_status_table table
Feb 23 04:10:20 Node2 fmd: [ID 377184 daemon.error] SUNW-MSG-ID: SMF-8000-YX, TYPE: defect, VER: 1, SEVERITY: major
Feb 23 04:10:20 Node2 EVENT-TIME: Sun Feb 23 04:10:20 IST 2020
Feb 23 04:10:20 Node2 PLATFORM: SPARC-T7-4, CSN: unknown, HOSTNAME: Node2
Feb 23 04:10:20 Node2 SOURCE: software-diagnosis, REV: 0.1
Feb 23 04:10:20 Node2 EVENT-ID: e07a6bda-e7ca-4368-83d3-fcecf18fd936
Feb 23 04:10:20 Node2 DESC: A service failed - the instance is restarting too quickly.
Feb 23 04:10:20 Node2 AUTO-RESPONSE: The service has been placed into the maintenance state.
Feb 23 04:10:20 Node2 IMPACT: svc:/system/cluster/scdpm:default is unavailable.
Feb 23 04:10:20 Node2 REC-ACTION: Run 'svcs -xv svc:/system/cluster/scdpm:default' to determine the generic reason why the service failed, the location
of any logfiles, and a list of other services impacted. Please refer to the associated reference document at http://support.oracle.com/msg/SMF-8000-YX for the la
test service procedures and policies regarding this diagnosis.

 

 

Cause

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
Symptoms
Cause
Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.