After upgrade to SAP Kernel 720/720_EXT, Solaris Cluster fails to start CI resource (SUNW.sap_ci_v2) because validation method cannot locate saposcol (Doc ID 1475319.1)

Last updated on OCTOBER 20, 2016

Applies to:

Solaris Cluster - Version 3.1 to 3.2U3 12/09 [Release 3.1 to 3.2]
Solaris Cluster Geographic Edition - Version 3.1x to 3.2U3 12/09 [Release 3.1 to 3.2]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86 (32-bit)
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on x86-64 (64-bit)

Symptoms

After upgrade of SAP Kernel, SAP CI Resource fails to be started by sap_ci_svc_start:

 

Changes

This happens, when SAP Kernel is upgraded to ≥ 720/720_EXT in Solaris Cluster 3.x

1) The SAP Kernel Release can be determined either by invoking '/usr/sap/<SID>/sys/exe/run/disp+work -v | grep "kernel release"' or in explorer <explorer-directory>/sap/<SID>/disp+work-v.out, e.g.:

-------------------- 
disp+work information 
-------------------- 
kernel release 720 


2) The Cluster Version can be determined either by invoking '/usr/cluster/bin/scinstall -pv|head -1' or in explorer <explorer-directory>/cluster/config/scinstall-pv.out e.g.:

Oracle Solaris Cluster 3.2u2 for Solaris 10 sparc

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms