ENABLING SOLARIS PROJECT SETTINGS FOR CRS
(Doc ID 435464.1)
Last updated on FEBRUARY 26, 2019
Applies to:Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
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 Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
Oracle Clusterware (CRS) and patchsets 10.2.0.1 - 220.127.116.11
Sun Solaris Sparc and x86-64 (64-bit)
This Note discusses options available to enable automatic start of CRS with Solaris 10 project settings.
Due to the CRS fixes available in CRS versions later than 18.104.22.168 this note ultimately applies only to
CRS versions not including a fix for bug 9442360 (i.e. the defect affecting 11.2.0.x CRS versions) or
bug 5629487 (defect affecting 10.2.0.x - 11.1.0.x CRS versions).
If a fix for bug 5629487 or bug 9442360 is present in the CRS install then
this note can be ignored or read as informational.
Please notice that both Solaris Operating System and Oracle Database still support the old method of
supplying these values for shared memory and semaphore parameters in /etc/system.
The various methods presented in this document are thus not explicitly recommended
although they have been verified to work.
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
|Short Remark on CRS and multiple Solaris projects|