** Myself
SAP Work Process check step
-se.sapPRD_DVEBMGS20 Start OK.
-ms.sapPRD_DVEBMGS20 Start OK.
-co.sapPRD_DVEBMGS20 Start OK.
-dw.sapPRD_DVEBMGS20 died
Step check
Check disp work process at /usr/sap/PRD/DVEBMGS20/work/dev_disp
Example content
*** ERROR => DpWPCheck: WXX (pid XXX) died (severity=0, status=65280) [dpxxdisp.c 15787]
Check sapcpe working OK or not
###Almost case sapcpe not corrected
check kernel for example update kernel to 236 from 114
1 ) /sapmnt/PRD/exe and /usr/sap/PRD/SYS/exe/run (New kernel after upgrade 236)
- ls –lt ## for check time
- ./disp+work -version ## for check version
2 ) /usr/sap/PRD/DVEBMGS20/exe - (sapcpe not copy use old version 114)
- ls –lt ## for check time
- ./disp+work -version ## for check version
Solve 1 Copy from Develop/Test QA in case Development not problem
cp –p /usr/sap/DEV/DVEBMGS20/exe/* /usr/sap/PRD/DVEBMGS20/exe
Solve 2 Change DIR_EXECUTABLE at startup profile to correct path in “Note 1104735 - Upgrade to new instance-specific directory on UNIX”
Detail Note 1104735
Symptom
With SAP NetWeaver 2004s and associated products, SAP introduces a new directory structure on UNIX. This allows a kernel exchange in the running system.
The new directory structure is created only for new installations.
With the new directory structure, the SAP kernel is installed in central directory (indicated by the profile parameter DIR_CT_RUN). From there, the kernel is copied during the system start to the instance-specific kernel directories (indicated by the profile parameter DIR_EXECUTABLE). The kernel is replicated using the program sapcpe.
Each SAP instance uses the kernel from its own instance-specific directory.
This note describes how to configure SAP systems (for which you have performed an upgrade) for the new directory structure.
For releases based on SAP NetWeaver 7.10, the directory structure was changed again. The
changes now support the heterogeneous system installations more efficiently. The SAP NetWeaver 7.10 directory structure is not supported on systems based on SAP NetWeaver 2004s.
Other terms
Directory structure, UNIX
Reason and Prerequisites
Before you change the files to be changed, you must save them.
The following procedure requires a standard SAP NetWeaver 2004s directory structure.
Solution
In the following, replace <SID> with your system ID, <NUMBER> with the system number, and <HOSTNAME> with the name of your host.
1. Stop all instances of the SAP system.
2. In each instance of the system, you must create the directory $(DIR_INSTANCE)/exe (for example, /usr/sap/<SID>/DVEBMGS<NUMBER>/exe) under the user <SID>adm. The directory must be part of the group sapsys, and the authorization should be 755 (drwxr-xr-xr).
3. For each instance, add the entries described below to the start profile.
Search for the line that contains the definition of the variable DIR_EXECUTABLE. It might look something like:
DIR_EXECUTABLE = $(DIR_EXE_ROOT)/run
change that line to:
DIR_CT_RUN = $(DIR_EXE_ROOT)/run
Add the following lines:
#=============================================================
DIR_EXECUTABLE = $(DIR_INSTANCE)/exe
DIR_PROFILE = $(DIR_INSTALL)/profile
_PF = $(DIR_PROFILE)/<SID>_DVEBMGS<NUMBER>_<HOSTNAME>
SETENV_00 = DIR_LIBRARY=$(DIR_LIBRARY)
SETENV_01 = LD_LIBRARY_PATH=$(DIR_LIBRARY):%(LD_LIBRARY_PATH)
SETENV_02 = SHLIB_PATH=$(DIR_LIBRARY):%(SHLIB_PATH)
SETENV_03 = LIBPATH=$(DIR_LIBRARY):%(LIBPATH)
SETENV_04 = PATH=$(DIR_EXECUTABLE):%(PATH)
#--------------------------------------------------------------
# Copy SAP Executables
#--------------------------------------------------------------
Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF)
#=============================================================
Search for all Execute_XX parameters and increase their number by one (for example, Execute_01 changes to Execute_02). Make sure that all Execute_XX have an ascending number in the correct order, beginning with 00.
4. Copy the profile parameters DIR_CT_RUN, DIR_EXECUTABLE, DIR_PROFILE and _PF from the start profile to the instance profile. It is important that these are the same in both profiles.
5. Beginning with the central instance, start all the instances.
Do not change the values in the <SID>adm user scripts (.sapenv.sh, .sapenv.csh). Although the user <SID>adm still uses the command line tools from the directory /usr/sap/<SID>/SYS/exe/run, instances use their own copies in /usr/sap/<SID>/DVEBMGS<NUMBER>/exe.
Example trace file
---------------------------------------------------
trc file: "dev_disp.new", trc level: 1, release: "700"
---------------------------------------------------
sysno 20
sid PRD
systemid 370 (Solaris on SPARCV9 CPU)
relno 7000
patchlevel 0
patchno 236
intno 20050900
make: single threaded, Unicode, 64 bit, optimized
pid 16312
Tue Aug 31 17:31:17 2010
kernel runs with dp version 243000(ext=110000) (@(#) DPLIB-INT-VERSION-243000-UC)
length of sys_adm_ext is 576 bytes
*** SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (20 16312) [dpxxdisp.c 1287]
DwSLCheckVersion: shared library version mismatch:
shared lib "dw_xml.so" version 114 <-> kernel version 236
shared lib "dw_xtc.so" version 114 <-> kernel version 236
shared lib "dw_stl.so" version 114 <-> kernel version 236
shared lib "dw_gui.so" version 114 <-> kernel version 236
shared lib "dw_mdm.so" version 114 <-> kernel version 236
rdisp/softcancel_sequence : -> 0,5,-1
use internal message server connection to port 3920
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: start server >csmret81_PRD_20 <
DpShMCreate: sizeof(wp_adm) 56320 (1760)
DpShMCreate: sizeof(tm_adm) 180414080 (30064)
DpShMCreate: sizeof(wp_ca_adm) 208000 (104)
DpShMCreate: sizeof(appc_ca_adm) 208000 (104)
DpCommTableSize: max/headSize/ftSize/tableSize=6000/8/6576056/6576064
DpShMCreate: sizeof(comm_adm) 6576064 (1088)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm) 0 (104)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm) 0 (72)
DpShMCreate: sizeof(vmc_adm) 0 (2080)
DpShMCreate: sizeof(wall_adm) (1200056/1034328/88/192)
DpShMCreate: sizeof(gw_adm) 48
DpShMCreate: SHM_DP_ADM_KEY (addr: 0xffffffff64000000, size: 189706312)
DpShMCreate: allocated sys_adm at 0xffffffff64000000
DpShMCreate: allocated wp_adm at 0xffffffff64002388
DpShMCreate: allocated tm_adm_list at 0xffffffff6400ff88
DpShMCreate: allocated tm_adm at 0xffffffff6400ffe8
DpShMCreate: allocated wp_ca_adm at 0xffffffff6ec1e668
DpShMCreate: allocated appc_ca_adm at 0xffffffff6ec512e8
DpShMCreate: allocated comm_adm at 0xffffffff6ec83f68
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 0xffffffff6f2c9728
DpShMCreate: allocated gw_adm at 0xffffffff6f2c97a8
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 0xffffffff6f2c97d8
DpShMCreate: allocated wall_adm at 0xffffffff6f2c97e0
Tue Aug 31 17:31:18 2010
MBUF state OFF
DpCommInitTable: init table for 6000 entries
rdisp/queue_size_check_value : -> off
ThTaskStatus: rdisp/reset_online_during_debug 0
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 4096 kByte.
Using implementation std
<ES> Info: use normal pages (no huge table support available)
EsStdUnamFileMapInit: ES base = 0x0xfffffffd50000000
EsStdInit: Extended Memory 8192 MB allocated
<ES> 2047 blocks reserved for free list.
ES initialized.
mm.dump: set maximum dump mem to 96 MB
Tue Aug 31 17:31:21 2010
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1694]
Tue Aug 31 17:31:26 2010
*** ERROR => MsINiRead: NiBufReceive failed (NIETIMEOUT) [msxxi.c 2515]
*** ERROR => MsIAttachEx:MsINiRead (rc=NIETIMEOUT) [msxxi.c 762]
***LOG Q0L=> DpLoopInit, nomscon () [dpxxdisp.c 1828]
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
*** ERROR => DpWPCheck: W1 (pid 16322) died (severity=0, status=65280) [dpxxdisp.c 15787]
0 comments:
Post a Comment