SAP interface not working

Hi Team,

Need ur help urgently....

We have 3 systems in the land space - BW,R/3 and SRM.Due to some issue in aix all went down.

We could bring everything up but the apps server related in the production of BW is still down. In AIX level the SAP system is up but when tried logging thru GUI it says Partner cannot be reached and also in SM51 of the central instance the SAP system is not seen,

Could someone help plzzzz

SAP Managed Tags:
Oracle Database

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (1)

Could be a network problem

Can you ping to the host.

In commnd promt run :

ping <ip address or hostname > -t

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

Thanks for the quick reply.

I have pinged and i get a proper response and so i am sure its not a network issue.

C:\Documents and Settings\prirav>ping 158.58.65.17 -t

Pinging 158.58.65.17 with 32 bytes of data:

Reply from 158.58.65.17: bytes=32 time=395ms TTL=247

Reply from 158.58.65.17: bytes=32 time=316ms TTL=247

Reply from 158.58.65.17: bytes=32 time=439ms TTL=247

Reply from 158.58.65.17: bytes=32 time=358ms TTL=247

Reply from 158.58.65.17: bytes=32 time=281ms TTL=247

Reply from 158.58.65.17: bytes=32 time=302ms TTL=247

Reply from 158.58.65.17: bytes=32 time=429ms TTL=247

Ping statistics for 158.58.65.17:

Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 281ms, Maximum = 439ms, Average = 360ms

can you pls send the logs of dev_disp from your BW apps server

Hi,

Here are the details under dev_disp in BWP Apps server.

bwpadm> more dev_disp

trc file: "dev_disp", trc level: 1, release: "640"

Sat Apr 19 17:56:47 2008

kernel runs with dp version 133000(ext=102000) (@(#) DPLIB-INT-VERSION-133000-UC)

length of sys_adm_ext is 524 bytes

sysno 10

sid BWP

systemid 324 (IBM RS/6000 with AIX)

relno 6400

patchlevel 0

patchno 155

intno 20020600

make: single threaded, Unicode, 64 bit

pid 299170

***LOG Q00=> DpSapEnvInit, DPStart (10 299170) [dpxxdisp.c 1100]

shared lib "dw_xml.so" version 155 successfully loaded

shared lib "dw_xtc.so" version 155 successfully loaded

shared lib "dw_stl.so" version 155 successfully loaded

shared lib "dw_gui.so" version 155 successfully loaded

shared lib "dw_mdm.so" version 155 successfully loaded

MtxInit: -2 0 0

ERROR => DpSysAdmExtCreate: ShmCreate (CREATE) [dpxxtool2.c 522]
ERROR => dispatcher already running ???? [dpxxtool2.c 523]
ERROR => I better EXIT before I do any (more) damage [dpxxtool2.c 525]

Hi Priyanka,

I think you have a shared mem issue :

On your CI can you run the cmd at OS level and let me know if there are any errors :

sappfpar check pf=<instance profile name>

Hi,

The ran the sappfpar check pf=BWP_DVEBMGS10_PSAPDB in the CI and below is the output. I see 2 errors in the end. Kindly help

bwpadm> sappfpar check pf=BWP_DVEBMGS10_PSAPDB

sappfpar=>sapparam(2): fopenU("BWP_DVEBMGS10_PSAPDB","r"): No such file or directory

sappfpar=>No Profile used.

sappfpar=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

================================================================================

== Checking profile: <no_profile>

================================================================================

***ERROR: Size of shared memory pool 10 too small

================================================================

SOLUTIONS: (1) Locate shared memory segments outside of pool 10

with parameters like: ipc/shm_psize_<key> =0

SOLUTION: Increase size of shared memory pool 10

with parameter: ipc/shm_psize_10 =152000000

***ERROR: Size of shared memory pool 40 too small

================================================================

SOLUTIONS: (1) Locate shared memory segments outside of pool 40

with parameters like: ipc/shm_psize_<key> =0

SOLUTION: Increase size of shared memory pool 40

with parameter: ipc/shm_psize_40 =112000000

Shared memory disposition overview

================================================================

Shared memory pools

Key: 10 Pool

Size configured.....: 19880000 ( 19.0 MB)

Size min. estimated.: 148649998 ( 141.8 MB)

Advised Size........: 152000000 ( 145.0 MB)

Key: 40 Pool for database buffers

Size configured.....: 14250000 ( 13.6 MB)

Size min. estimated.: 108975040 ( 103.9 MB)

Advised Size........: 112000000 ( 106.8 MB)

Shared memories inside of pool 10

Key: 1 Size: 2500 ( 0.0 MB) System administration

Key: 2 Size: 3998104 ( 3.8 MB) Disp. administration tables

Key: 11 Size: 500000 ( 0.5 MB) Factory calender buffer

Key: 12 Size: 6000000 ( 5.7 MB) TemSe Char-Code convert Buf.

Key: 13 Size: 60500000 ( 57.7 MB) Alert Area

Key: 14 Size: 4400000 ( 4.2 MB) Presentation buffer

Key: 16 Size: 22400 ( 0.0 MB) Semaphore activity monitoring

Key: 17 Size: 2672386 ( 2.5 MB) Roll administration

Key: 30 Size: 3072 ( 0.0 MB) Taskhandler runtime admin.

Key: 31 Size: 1806000 ( 1.7 MB) Dispatcher request queue

Key: 33 Size: 10240000 ( 9.8 MB) Table buffer, part.buffering

Key: 51 Size: 3200000 ( 3.1 MB) Extended memory admin.

Key: 52 Size: 40000 ( 0.0 MB) Message Server buffer

Key: 54 Size: 4202496 ( 4.0 MB) Export/Import buffer

Key: 55 Size: 8192 ( 0.0 MB) Spool local printer+joblist

Key: 57 Size: 1048576 ( 1.0 MB) Profilparameter in shared mem

Key: 58 Size: 4096 ( 0.0 MB) Enqueue ID for reset

Shared memories inside of pool 40

Key: 42 Size: 7232992 ( 6.9 MB) DB TTAB buffer

Key: 43 Size: 32534392 ( 31.0 MB) DB FTAB buffer

Key: 44 Size: 7958392 ( 7.6 MB) DB IREC buffer

Key: 45 Size: 4886392 ( 4.7 MB) DB short nametab buffer

Key: 46 Size: 20480 ( 0.0 MB) DB sync table

Key: 47 Size: 3073024 ( 2.9 MB) DB CUA buffer

Key: 48 Size: 300000 ( 0.3 MB) Number range buffer

Key: 49 Size: 2968344 ( 2.8 MB) Spool admin (SpoolWP+DiaWP)

Shared memories outside of pools

Key: 3 Size: 13714400 ( 13.1 MB) Disp. communication areas

Key: 4 Size: 503248 ( 0.5 MB) statistic area

Key: 6 Size: 159744000 ( 152.3 MB) ABAP program buffer

Key: 7 Size: 14838 ( 0.0 MB) Update task administration

Key: 8 Size: 67108964 ( 64.0 MB) Paging buffer

Key: 9 Size: 134217828 ( 128.0 MB) Roll buffer

Key: 18 Size: 917604 ( 0.9 MB) Paging adminitration

Key: 19 Size: 30000000 ( 28.6 MB) Table-buffer

Key: 41 Size: 25010000 ( 23.9 MB) DB statistics buffer

Key: 62 Size: 85983232 ( 82.0 MB) Memory pipes

Key: 63 Size: 409600 ( 0.4 MB) ICMAN shared memory

Key: 64 Size: 4202496 ( 4.0 MB) Online Text Repository Buf.

Key: 65 Size: 4202496 ( 4.0 MB) Export/Import Shared Memory

Key: 1002 Size: 400000 ( 0.4 MB) Performance monitoring V01.0

Key: 58900100 Size: 4096 ( 0.0 MB) SCSA area

Nr of operating system shared memory segments: 17

Shared memory resource requirements estimated

================================================================

Nr of shared memory descriptors required for

Extended Memory Management (unnamed mapped file).: 16

Total Nr of shared segments required.....: 33

System-imposed number of shared memories.: 1000

Shared memory segment size required min..: 159744000 ( 152.3 MB)

System-imposed maximum segment size......: 35184372088832 (33554432.0 MB)

Swap space requirements estimated

================================================

Shared memory....................: 755.7 MB

..in pool 10 19.0 MB, 747% used !!

..in pool 40 13.6 MB, 764% used !!

..not in pool: 502.0 MB

Processes........................: 29.0 MB

Extended Memory .................: 4092.0 MB

Total, minimum requirement.......: 4876.7 MB

Process local heaps, worst case..: 1907.3 MB

Total, worst case requirement....: 6784.1 MB

Errors detected..................: 2

Warnings detected................: 0

Thats it, your have the SHM issue

correct the values of the below parameter in the instance profile and restart

ipc/shm_psize_10 =152000000

ipc/shm_psize_40 =112000000

As you can see -->

SOLUTION: Increase size of shared memory pool 10

with parameter: ipc/shm_psize_10 =152000000

SOLUTION: Increase size of shared memory pool 40

with parameter: ipc/shm_psize_40 =112000000

In instance profile.

Regards.

Hi,

I check them in the CI directly under RZ10 and i see the below values mentioned.

ipc/shm_psize_10 292000000

ipc/shm_psize_16 0

ipc/shm_psize_31 0

ipc/shm_psize_40 160000000

ipc/shm_psize_52 0

ipc/shm_psize_62 0

Kindly help

You add them in the Default Profile too.and restart

Hi,

I have tried adding the below values in the Default profile and have restarted the CI.

ipc/shm_psize_10 292000000

ipc/shm_psize_40 160000000

I tried running sappfpar check pf=BWP_DVEBMGS10_PSAPDB in the CI again after the restart and gives me the same error message.

Kindly help.

Mention the default value as given in the listing

ipc/shm_psize_10 =152000000

ipc/shm_psize_40 =112000000

if the values are set too high also, you will get the SHM error

Hi,

I initially tried giving the same value mentioned in the default and tried restarted and checked , i got the same error message.

Then i thought may be the default and the instance must have the same value and so changed accordingly to higher and same values in both and tried restarting and checked the command and it still shows the same error message.

Do u want me to change to lower values both in default and Instance profile and then try??

Hi Shaji. "you will get the SHM error" but the instance will up and the PARTNER NOT REACHED It is not observed.

In this time can you login into system ?

Regards.

No dont change to lower values. Now what is the dev_disp showing.

Hi Sergo, yes you are right, but am not sure its displaying 'PARTNER NOT REACHED'

Priyanka, are you able to login now ?

Hi ,

I have tried restarted the Apps server too and tried to check whats in dev_disp and i get the below listed error message again.

bwpadm> startsap

Checking BWP Database

ABAP Database is running

Checking BWP Database

Starting SAP-Collector Daemon

08:30:59 20.04.2008 LOG: Effective User Id is root

***********************************************************************

This is Saposcol Version COLL 20.90 640 - AIX v6.55 5L-64 bit 060323
Usage: saposcol -l: Start OS Collector
saposcol -k: Stop OS Collector
saposcol -d: OS Collector Dialog Mode
saposcol -s: OS Collector Status
The OS Collector (PID 368700) is already running .....

************************************************************************

saposcol already running

Starting SAP Instance D10

Startup-Log is written to /home/bwpadm/startsap_D10.log

Instance on host psappbcs started

IGS on host psappbcs started

bwpadm> cd /usr/sap/BWP/D10

bwpadm> cd work

bwpadm> more dev_disp

trc file: "dev_disp", trc level: 1, release: "640"

Sun Apr 20 08:31:00 2008

kernel runs with dp version 133000(ext=102000) (@(#) DPLIB-INT-VERSION-133000-UC)

length of sys_adm_ext is 524 bytes

sysno 10

sid BWP

systemid 324 (IBM RS/6000 with AIX)

relno 6400

patchlevel 0

patchno 155

intno 20020600

make: single threaded, Unicode, 64 bit

pid 598232

***LOG Q00=> DpSapEnvInit, DPStart (10 598232) [dpxxdisp.c 1100]

shared lib "dw_xml.so" version 155 successfully loaded

shared lib "dw_xtc.so" version 155 successfully loaded

shared lib "dw_stl.so" version 155 successfully loaded

shared lib "dw_gui.so" version 155 successfully loaded

shared lib "dw_mdm.so" version 155 successfully loaded

MtxInit: -2 0 0

ERROR => DpSysAdmExtCreate: ShmCreate (CREATE) [dpxxtool2.c 522]
ERROR => dispatcher already running ???? [dpxxtool2.c 523]
ERROR => I better EXIT before I do any (more) damage [dpxxtool2.c 525]

I also tried to login thru SAP GUI but it still gives me the same error message as " PARTNER NOT REACHED"

What is the Kernel level you using now ? May be you need to upgrade the Kernel.

Before changing the Kernel :

Stop your BW including the DB

run at OS Level :

Cleanipc <instance no> -

> to display

Cleanipc <instance no> remove -

>remove the SHM

also check using :

ipcs (if you see and PID of the BW instance, kill the PID>

ipcrm -s / -m <PID>

Then start the DB and the BW

Hi,

I just got a doubt.

Should i be trying this in CI or the Apps server??

Hi,

I am question to add...

Does it require the root access to remove the shared memory...

You need to do this on the CI, but no harm in running at the Apps Server.

cleanipc -> with sidadm

ipcs / ipcrm - > with root

If still not successfull check if this note applies to your BW version

Note 883843 - BW instances can no longer be started

Hi,

I dont have the root access now and wont be able to contact anyone in the AIX team till tomorrow evening as they all work in Brazil.

We have a reboot of the whole server today at around 7 pm SST and not sure if that could remove all the shared memory and assign it back.

I am hoping it to work after the whole system reboot if not i shall coordinate with the AIX and run those commands and will keep u posted with the updates.

Thank u so very much for your speedy reply. Thanks again.

Ofcourse, rebooting the server will solve the issue !!!

Good Luck

Hi Team,

Restarting also did not work.

I had my colleagues work on the same issue and we listed all the WP in that system thru

DPMON pf=/usr/sap/BWP/SYS/profile/BWP_D10_psappbcs and listed all the WP and found that one was stuck.

Killed the core processes and tried restarting , the system starting logging in thru SAP GUI.

Good !!!

So was that becz it had too many WP defined.

Hi,

There was one Dialog WP running and so we killed the WP manually using DPMON and the system started working fine.

I think we were troubleshooting the physical but the problem was logical.

Thanks for ur time and help though.

Regards,

Priyanka

Ask a Question

Top Q&A Solution Author

User

Count