My Oracle Support Banner

Solaris Cluster 3.X - After SAP Upgrade From 721 To 745, HA-SAP (SUNW.sapwebas) no longer works. (Doc ID 2578866.1)

Last updated on AUGUST 14, 2020

Applies to:

Solaris Cluster - Version 3.2 to 3.3 U2 [Release 3.2 to 3.3]
Information in this document applies to any platform.

Symptoms

Configuration:

(webas-rg:webas-hasp-rs) Res resource type: SUNW.HAStoragePlus:8 - Online
(webas-rg:webas-lh-rs) Res resource type: SUNW.LogicalHostname:3 - Online
(webas-rg:webas-rs) Res resource type: SUNW.sapwebas:5 - Offline <-----<<< Fails to start

Res Group name: webas-rg
(webas-rg) Res Group RG_description: <NULL>
(webas-rg) Res Group mode: Failover
(webas-rg) Res Group management state: Managed
(webas-rg) Res Group RG_project_name: default
(webas-rg) Res Group RG_SLM_type: manual
(webas-rg) Res Group RG_affinities: ++cs-rg
(webas-rg) Res Group Auto_start_on_new_cluster: True
(webas-rg) Res Group Failback: False
(webas-rg) Res Group Nodelist: Node1 Node2
(webas-rg) Res Group Maximum_primaries: 1
(webas-rg) Res Group Desired_primaries: 1
(webas-rg) Res Group RG_dependencies: <NULL>
(webas-rg) Res Group network dependencies: True
(webas-rg) Res Group Global_resources_used: <All>
(webas-rg) Res Group Pingpong_interval: 3600
(webas-rg) Res Group Pathprefix: <NULL>
(webas-rg) Res Group system: False
(webas-rg) Res Group Suspend_automatic_recovery: False

(webas-rg:webas-rs) Res resource type: SUNW.sapwebas:5
(webas-rg:webas-rs) Res strong dependencies: db-srv-rs db-lsnr-rs jscs-enq-rs jscs-msg-rs webas-hasp-rs
(webas-rg:webas-rs:Webas_Shutdown_Script) Res property value: /usr/sap/<SAP_SID>/SYS/exe/run/stopsap
(webas-rg:webas-rs:Webas_Startup_Script) Res property value: /usr/sap/<SAP_SID>SYS/exe/run/startsap
(webas-rg:webas-rs:SAP_Instance_Type) Res property value: J2EE
(webas-rg:webas-rs:SAP_User) Res property value: <SAP_SID>adm
(webas-rg:webas-rs:SAP_Instance_Name) Res property value: Jxx
(webas-rg:webas-rs:SAP_Instance_Number) Res property value: Jxx
(webas-rg:webas-rs:SAP_SID) Res property value: <SAP_SID_NAME>

--

Messages:

Jun 11 17:44:19 Node1 Cluster.RGM.global.rgmd: [ID 224900 daemon.notice] launching method <webas_svc_start> for resource
<webas-rs>, resource group <webas-rg>, node <Node1>, timeout <300> seconds

Jun 11 17:44:19 Node1 SC[,SUNW.sapwebas:5,webas-rg,webas-rs,webas_svc_start]: [ID 141062 daemon.error] Failed to connect
to host webas-lh-rs and port 50300: Connection refused.
Jun 11 17:44:19 Node1 SC[,SUNW.sapwebas:5,webas-rg,webas-rs,webas_svc_start]: [ID 805735 daemon.error] Failed to connect
to the host <webas-lh-rs> and port <50300>.
Jun 11 17:44:20 Node1 SC[,SUNW.sapwebas:5,webas-rg,webas-rs,webas_svc_start]: [ID 141062 daemon.error] Failed to connect
to host webas-lh-rs and port 50300: Connection refused.
Jun 11 17:44:20 Node1 SC[,SUNW.sapwebas:5,webas-rg,webas-rs,webas_svc_start]: [ID 805735 daemon.error] Failed to connect
to the host <webas-lh-rs> and port <50300>.
Jun 11 17:44:20 Node1 SC[,SUNW.sapwebas:5,webas-rg,webas-rs,webas_svc_start]: [ID 702018 daemon.notice] Waiting for the S
AP Application server to come online.
Jun 11 17:44:30 Node1 SC[,SUNW.sapwebas:5,webas-rg,webas-rs,webas_svc_start]: [ID 141062 daemon.error] Failed to connect
to host webas-lh-rs and port 50300: Connection refused.

(snip)

Jun 11 17:45:20 Node1 SC[,SUNW.sapwebas:5,webas-rg,webas-rs,webas_svc_start]: [ID 260883 daemon.error] In J2EE probe, fai
led to find http header in HTTP/1.0 503 Service Unavailable

(snip)

Jun 11 17:49:23 Node1 Cluster.RGM.global.rgmd: [ID 764140 daemon.error] Method <webas_svc_start> on resource <webas-rs>,
resource group <webas-rg>, node <Node1>: Timeout.

 

Changes

Customer upgraded the SAP kernel from 721 to 745.

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
Changes
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.