cancel
Showing results for 
Search instead for 
Did you mean: 

System start issue.

former_member759680
Contributor
0 Kudos

Hello,

Our SAP system is up and database is also up. We can see all the processes using ps -ef.

However, when we try connecting through SAP GUI, it gets stuck at 'Waiting for Response..'

Its a dual stack system. I have checked startsap_DVEBMGS01.log startsap_SCS02.log std_server0.out etc... they are all fine.

Please advise

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

This situation can happen due to archiver stuck.

Check /oracle/<SID>/oraarch filesystem space availability.

Former Member
0 Kudos

Hi

Please check the dispatcher work processes status using dpmon .

run the command in os level

dpmon pf=<Instance profile name path>.

Choose menu -> M -> P "processes list".

Check the available work processes , and check the error message in dev_w0, w1, w2.. files .

It may help you to get the root cause of the issue...

Regards,

Sureshram

former_member759680
Contributor
0 Kudos

Juan, there is enough free space in teh database filesystem.

Suresh,

This is display of dpmon. Please help me understanding it..

No Ty. Pid Status Cause Start Err Sem CPU Time Program Cl User

-


0 DIA 757896 Run yes 0 0 80948SAPMHTTP 000 SAPSYS

1 DIA 930004 Ended no 0 0 80948SAPMHTTP 000 SAPSYS

2 DIA 835754 Run yes 0 -33 80948SAPMHTTP 000 SAPSYS

3 DIA 938210 Ended yes 0 4 80948 000 SAPSYS

4 DIA 925920 Run yes 0 0 80948 000 SAPSYS

5 DIA 798862 Run yes 0 33 80943 100 9757F4061F1

6 DIA 782516 Down yes 0 4 0

7 DIA 807066 Down yes 0 4 0

8 UPD 819360 Down yes 0 4 0

9 UPD 868564 Down yes 0 4 0

10 UPD 454810 Down yes 0 4 0

11 ENQ 1241246 Down yes 0 4 0

12 BTC 1089688 Down yes 0 4 0

13 BTC 1196220 Down yes 0 4 0

14 BTC 884846 Down yes 0 4 0

15 SPO 975090 Down yes 0 4 0

16 UP2 389126 Down yes 0 4 0

17 UP2 458788 Down yes 0 4 0

JPReyes
Active Contributor
0 Kudos

can you please post the errors in dev_w1?

Regards

Juan

former_member759680
Contributor
0 Kudos

Its a pretty long log, but it ends with....

_____________________________________________________________________________

      • ERROR => EsILock: inconsistency, time = 3456288276 [esxx.c 3340]

M PfStatDisconnect: disconnect statistics

M Entering TH_CALLHOOKS

M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP

M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c 724]

M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 261]

M Entering ThSetStatError

M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=1)

M Entering ThReadDetachMode

M call ThrShutDown (1)...

B dbtbxbuf: Buffer TBX_SINGLE not available

M ***LOG Q02=> wp_halt, WPStop (Workproc 1 930004) [dpuxtool.c 260]

JPReyes
Active Contributor
0 Kudos

Thats good ... but seems like the error started earlier in the log... can you post the first error found on the logs...

regards

Juan

former_member759680
Contributor
0 Kudos

These are the errors in the log, they are repeated over and over . Is this a cumulative log??

____________________________________________________________________________

ThRollIn: roll in T36/U308/M0/I0 (level=7, abap_level=1, attach_em=1)

M *** ERROR => ThRollIn: no roll context for T36/U308/M0/I0 [thxxmem.c 802]

M ThIAMDel: delete tid/mode 36/0 (th_errno 23, release 1)

M ThAMCheck: T36/M0 not in use

___________________________________________________________________________

ABAP Program SAPLHR_RCF_CUST_01 .

A Source RCF_CUST_F01 Line 144.

A Error Code MESSAGE_TYPE_UNKNOWN.

A Module $Id: //bas/700_REL/src/krn/runt/abdynpro.c#13 $ SAP.

_____________________________________________________________________________

OCI-call failed with -1=OCI_ERROR

C SQL error 1013: 'ORA-01013: user requested cancel of current operation'

C SQL cancelled; calling registered fct. at 0x1105797d0

M program canceled

M reason = soft cancel

M user = SAPSYS

M client = 000

M terminal = 10.77.140.175

M report = SCMS_R3DB_SUB

M in_ThErrHandle: 1

______________________________________________________________________

Thu Dec 11 19:42:07 2008

M *** ERROR => ThIDbgFreeInbuf: MpiFreeInbuf for mpi <7ed> failed (13) [thxxdbg.c 753]

M *** ERROR => ThIDbgFreeInbuf: MpiFreeInbuf for mpi <7ed> failed (13) [thxxdbg.c 753]

M *** ERROR => ThIDbgFreeInbuf: MpiFreeInbuf for mpi <7ed> failed (13) [thxxdbg.c 753]

___________________________________________________________________________

Former Member
0 Kudos

Hi,

Is this happening to all users are only specific users?

Try to activate the "low Speed connection" connection feature in SAP Logon.

Please proceed according to note 161053.

If there are longer response times due to performance problems in

the network (in particular when you are using the SAPGUI in the WAN

you should use the configuration in the SAPLOGON for "Low Speed

Connection" (LSC) (see comments). You will find this setting option

in saplogon under: SAPLOGON > PROPERTIES > ADVANCED. You will

find further information on the network load in the SAP Service

Also check you network connection with note 500235 Network Diagnosis with NIPING

Cheers!

JPReyes
Active Contributor
0 Kudos

Check that the DB logs are not full...

Regards

Juan