Please help me

[Former Member]

Hi Guys!!!

when I am executing the transaction GD23, am getting time out dump error,how can I identify which select statment getting so late to fetch the data.is there any transaction to find out the solution?

Thanks in advance

Richard

[Former Member]

HI RICHARD,

performance of an SQL query can be checked out in

the transaction ST05...

this may surely help you,

plz reward if helpful,

thanks and regards,

srikanth tulasi.

[Former Member]

Hi Srikanth,

Please tell me how to check the ST05.

Thanks

Richard

[Former Member]

Hi,

SQL Trace

Use

The SQL Trace function is an on-demand log of selected SQL statements that are issued against the database through the Open SQL Engine. The SQL Trace can be switched on or off dynamically. The log format is database independent. Besides the SQL statement text, each log record contains information about the point in time when the statement was executed, its duration, its input parameters and results (where applicable) as well as context information.

Features

The SQL Trace is especially useful for:

· Development

SQL Trace can help JDO, enterprise beans, servlet and JSP developers to learn which kind of database accesses their code produces.

· Performance analysis

Typically, performance issues are caused by inefficient database accesses. In this case SQL Trace can be used to show the issued SQL statements and their duration, thus helping to identify inefficient SQL statements.

Activities

Typically, you should use the SQL Trace when you need to check the behavior of a particular application. This is the following scenario:

...

1. You launch the SQL Trace application.

2. You activate the SQL Trace.

3. You run the application that you want to trace.

4. You deactivate the SQL Trace.

5. You set filters optionally.

6. You evaluate the trace.

You can also evaluate a trace that already exists.

The SQL Trace also provides functions for file administration.

SQL Trace is less suitable for detecting general performance issues. Therefore, we do not recommend that you keep it constantly activated, as it consumes additional resources.

The transaction is ST05.

Regards,

Renjith Michael.

[Former Member]

Hi Guys!!!

Thanks for your all support and help, when I am executing the Transaction GD23,the dump analysis were occurred in the program (GP$GLX$ZZSL01A).Using the transaction ST05, I found the time taken place using in debugging mode, below code are taking so much of time, what is the reason for that, how will act FETCH statement in ABAP.

[Former Member]

Hi Guys!!!

Thanks for your all support and help, when I am executing the Transaction GD23,the dump analysis were occurred in the program (GP$GLX$ZZSL01A).Using the transaction ST05, I found the time taken place using in debugging mode, below code are taking so much of time, what is the reason for that, how will act FETCH statement in ABAP.

L_COUNTER = 0.

C_S_CURSOR-SUBRC = 0.

WHILE I_PACKAGE_SIZE EQ 0 OR

L_COUNTER LT I_PACKAGE_SIZE.

FETCH NEXT CURSOR C_S_CURSOR-CURSOR

INTO CORRESPONDING FIELDS OF TABLE G_T_RECORDS

PACKAGE SIZE L_PSIZE.

IF SY-SUBRC EQ 0.

Hoping you for reply

Richards

[Former Member]

Since this is a standard transaction i would sugget you to once look at the dump analysis of the same in ST22 and the additional info of the dump like source code extract.

Refer the same to your basis consultant .

Vijay

[Former Member]

HI richard,

go to st05

1)click on activate trace,

2)go to your program and run it

3)again in st05 click deactivate trace

4)then click display trace

you can know the information clearly

regarding the time taken by select queries.

plz reward if you find this helpful,

regards,

Srikanth Tulasi.