SAP WebAS Data Services Fault Probes do not function for dpmon, SAP dispatcher is not monitored.
State
10-Fix Delivered (Fix available in build)
Category:Subcategory
suncluster:ha-sapwebas
Keywords
Responsible Engineer
Hemachandran Namachivayam
Reported Against
Duplicate Of
Introduced In
Commit to Fix
3.2_patch_04
Fixed In
3.2_patch_04
Release Fixed
3.2_patch(3.2_patch_04)
Related Bugs
Submit Date
12-March-2007
Last Update Date
30-March-2007
Description
There is no monitoring of the SAP dispatcher by SAP WebAS data services. If the dispatcher dies the is no restart. This is a regression of previous releases from 3.1X.
This problem happens in both the global and local zones.
Test procedure:
1) Verify the SUNW.sapwebas is online.
sapnode1 # clrs status jsc-webas-res
Cluster Resources ===
Resource Name Node Name State Status Message
------------- --------- ----- --------------
jsc-webas-res sapnode1 Online Online - Service is online.
sapnode2 Offline Offline
2) Verify the SUNW.sapwebas is monitored.
sapnode1 # scrgadm -pv -j jsc-webas-res
(jsc-D00-rg) Res name: jsc-webas-res
(jsc-D00-rg:jsc-webas-res) Res R_description:
(jsc-D00-rg:jsc-webas-res) Res resource type: SUNW.sapwebas:4
(jsc-D00-rg:jsc-webas-res) Res type version: 4
(jsc-D00-rg:jsc-webas-res) Res resource group name: jsc-D00-rg
(jsc-D00-rg:jsc-webas-res) Res resource project name: default
(jsc-D00-rg:jsc-webas-res{sapnode1}) Res enabled: True
(jsc-D00-rg:jsc-webas-res{sapnode2}) Res enabled: True
(jsc-D00-rg:jsc-webas-res{sapnode1}) Res monitor enabled: True
(jsc-D00-rg:jsc-webas-res{sapnode2}) Res monitor enabled: True
3) Verify Successful logon to SAP via the SAP GUI.
4) Verify the SAP dispatcher is running correctly.
sapnode1:jscadm 1% dpmon -info
dpmon=>sapparam(1c): No Profile used.
dpmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
name: jsc-D00-srv_JSC_00
path: dw.sapJSC_DVEBMGS00
systemid: 370 (Solaris on SPARCV9 CPU)
relno: 7000
patchlevel: 0
patchno: 58
intno: 20050900
pid: 4557
5) Kill the dispatcher
sapnode1:jscadm 2% kill -9 4557
6) Verify the connection to SAP is broken via the SAP GUI.
7) Verify that no action is taken by the SAP WebAS data service
# clrs status jsc-webas-res
Cluster Resources ===
Resource Name Node Name State Status Message
------------- --------- ----- --------------
jsc-webas-res sapnode1 Online Online - Service is online.
sapnode2 Offline Offline
8) Verify the dispatcher is NOT running correctly.
sapnode1:jscadm 3% dpmon -info
dpmon=>sapparam(1c): No Profile used.
dpmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
/usr/sap//D00/log/SLOG00: No such file or directory
rslgwr1(11): rstrbopen cannot open SysLog file.
SysLog:mQ0I20070312112117000392500000MO
: 0
: connect146 NiPConnconnectnixxi.cp2454
connection to dispatcher failed
9) Verify that no messages are logged to /var/adm/messages.