topic Re: Response time low in Application Development and Automation Discussions

Response time low

Former Member — Thu, 24 Aug 2006 19:51:55 GMT

Hi,

In our Prod system the reponse time is very slow from past 20 min . I went to SM66 and there was large no.of errors with reason 6, for dialog work processes. Can you please tell me the reason and trouble shoot this issue? Is there any other ways that I can troubleshoot ?

Thanks in advance

Regards

Srinivas

Re: Response time low

sridhar_k1 — Thu, 24 Aug 2006 19:55:17 GMT

Is the number 6 in Err column, it means that many times the wp terminated abnormally. There are many reaons for wp termination, check OSS notes.

Regards

Sridhar

Re: Response time low

LeonardoAraujo — Thu, 24 Aug 2006 19:56:32 GMT

To approach a problem like this there are many options.

I would recommend taking a look at the system state right now, before analysing previous errors and causes.

Check Sm50 or SM66 for running Workprocesses. There you will see what uis currently taking up system "juice".

If that is not enough you may need to goe back at the errors to figure out what is going on. For that read short dumps and update cancellations (ST22 and SM13). Also, go to DB01 for Database deado locks. You may need Basis help on this one since the problem could be diskspace , for example.

Hope it helps,

Leonardo De Araujo

Re: Response time low

Former Member — Thu, 24 Aug 2006 20:13:40 GMT

Thanks for the information. Basically DB01 is fine and large no.of dumps in ST22.

In SM66, there are large no.of Roll Out with ROLL_ADM semaphore.

Re: Response time low

LeonardoAraujo — Thu, 24 Aug 2006 20:32:52 GMT

Could you please send here the header of one of the dumps (assuming most are the same error)?

Thanks

Leonardo De Araujo

Re: Response time low

Former Member — Thu, 24 Aug 2006 20:38:10 GMT

Are a lot of them time-outs?

Rob

Re: Response time low

LeonardoAraujo — Thu, 24 Aug 2006 20:45:01 GMT

If you have time-outs, you should check why the processes too so long.

For that, rely on work processes running right now. You may have some in "Running" mode. Click on refresh and pay attention to the column ACTION. There you will see which table is being accessed and if it is a table scan for example. Also you will see the program. To help narrowing down, identify if you see a pattern. Are them the same program? Same Table?

Leonardo De Araujo

Re: Response time low

Former Member — Thu, 24 Aug 2006 20:48:20 GMT

Here's the dump details. Please explain me,If any idea to troubleshoot this issue.

Occurred on 08/24/2006 at 15:42:10

Process terminated by signal 11.

What happened?

Error in the SAP Basis system

ABAP/4 processor detected an internal system error.

The current ABAP program "YVOL_R154_ORDER_OVERVIEW " had to be terminated

because the ABAP

processor discovered an invalid system state.

What can you do?

Please make a note of the actions and input which caused the error.

To resolve the problem, contact your

SAP system administrator.

Choose "Print" for a hard coopy of the termination message. You can

display and adminster short dump messages using Transaction ST22.

Error analysis

An SAP System process was terminated by an operating system signal.

Possible reasons for this are:

1. Internal SAP System error.

2. Process was terminated externally (by the system administrator).

Last error logged in SAP kernel

Component............ "NI (network interface)"

Place................ "SAP-Dispatcher odparp02_PPF_02 on host odparp02"

Version.............. 34

Error code........... "-6"

Error text........... "connection to partner broken"

Description.......... "NiPRead"

System call.......... "recv"

Module............... "niuxi.c"

Line................. 1204

The error reported by the operating system is:

Error number..... 131

Error text....... "Connection reset by peer"

How to correct the error

The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often

contains a file called 'core'.

Save this file under another name.

If you cannot solve the problem yourself, please send the

following documents to SAP:

1. A hard copy print describing the problem.

To obtain this, select the "Print" function on the current screen.

2. A suitable hardcopy prinout of the system log.

To obtain this, call the system log with Transaction SM21

and select the "Print" function to print out the relevant

part.

3. If the programs are your own programs or modified SAP programs,

supply the source code.

To do this, you can either use the "PRINT" command in the editor or

print the programs using the report RSINCL00.

4. Details regarding the conditions under which the error occurred

or which actions and input led to the error.

Regards

Srinivas

Re: Response time low

Former Member — Thu, 24 Aug 2006 21:01:22 GMT

Maybe note 350167 would apply.

Rob

Re: Response time low

LeonardoAraujo — Thu, 24 Aug 2006 21:20:07 GMT

I've noticed that it was a custom program. Are all the problems/dumps related to this program? you can see that on ST22.

If yes, was this program just changed? Probably yes. In this case, reverse the changes and figure out the problem in DEV or QAS.

Leonardo De Araujo

Re: Response time low

Former Member — Thu, 24 Aug 2006 21:36:49 GMT

Also, in the dump information, you should find the line where the dump occured. See if that tells you something or post that here.