Solaris Cluster 3.x SUNW.oracle_server or SUNW.oracle_listener or Application Failures after Adding zpool to Zpools property of HAStoragePlus Resource used in Non-global Zone
(Doc ID 2157557.1)
Last updated on AUGUST 14, 2020
Applies to:Solaris Cluster - Version 3.2 to 3.3 U1 [Release 3.2 to 3.3]
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)
The issue occured in a Solaris Cluster 3.2 with a Resource Group (RG) configured to have Non-Global Zones (NGZ's) in the Nodelist. (GZ= Global Zone)
Group: oracle-rg <GZ1>:<NGZ1> Online No
Group: oracle-rg <GZ2>:<NGZ1> Offline No
The SUNW.HAStoragePlus (HASP) resource in the group:
(oracle-rg:oracle-hastp-rs) Res resource type: SUNW.HAStoragePlus:6 <------<<<
(oracle-rg:oracle-lh-rs) Res resource type: SUNW.LogicalHostname:2
(oracle-rg:ora-srv-rs) Res resource type: SUNW.oracle_server:6
(oracle-rg:ora-lsn-rs) Res resource type: SUNW.oracle_listener:5
The original working Zpool:
(oracle-rg:oracle-hastp-rs:Zpools) Res property value: oracle
The problem Zpool was named 'archive'. When it was added to the HASP resource above the /var/opt/SUNWscor/oracle_listener/*log* file showed:
The following simple lab testing (RG with only HASP resource) with Solaris Cluster 3.3u2 shows HASP probe failures and the resource and RG going offline when adding a wrongly created zpool to the HASP resource.
A new zpool (archive) was created and added to the Zpools property of the HASP resource.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!