topic Re: Runtime analysis, SE30, ERROR in Application Development and Automation Discussions

Runtime analysis, SE30, ERROR

Former Member — Mon, 12 May 2008 04:42:56 GMT

hi all,

today i just ran a report for runtime analysis on SE30 for a particular report and i got an error saying

"Unable to end the measurement (error number 5, Error when measuring)"..

what does this error mean?

its not an exceeded time limit error as its getting over by 10-15 mins...

as a result i m not able to track the performance issues with the report..

kindly guide me how to solve this issue... i tried viewing the file generated from report run.... but it was not the proper analysis...

kindly help

Re: Runtime analysis, SE30, ERROR

Former Member — Mon, 12 May 2008 04:45:46 GMT

Re: Runtime analysis, SE30, ERROR

Former Member — Mon, 12 May 2008 04:52:16 GMT

hi..

can you please provide some suggestion?

Re: Runtime analysis, SE30, ERROR

Former Member — Mon, 12 May 2008 04:53:23 GMT

HI,

If the session time that is limited by basis settings is completed even the program is not executed

completely such error may come.

try to improve the performance of ur code.

See the following link.

http://help.sap.com/saphelp_nw70/helpdata/en/c6/617cafe68c11d2b2ab080009b43351/content.htm

Performance Measurements

Use

If you want to monitor the performance of your system, or compare its performance at different times, you can perform a runtime analysis. You usually start the runtime analysis (after performing certain activities in the system) with transaction SE30.

You use transaction SICF to activate the runtime analysis both for ICF runtime and for applications that run using ICF runtime. You can evaluate the results with transaction SE30.

Activities

Activate the Runtime Analysis

1. Start the runtime analysis with transaction SICF.

2. Choose Edit –> Runtime Analysis ® Activate.

3. Enter the service path that you want the runtime analysis to be activated for.

You can set the option User-Dependent to activate the runtime analysis for a specific user or client (all users in a client) You can also implement a measurement variant. To do this, you need to enter the variant user (owner of the variant), the variant itself, and the measurement precision.

Any active runtime analyses must be deactivated after the requests have been executed. You deactivate the requests in transaction SICF by choosing Edit –> Runtime Analysis –> Deactivate.

Display/Evaluate Result

You can now evaluate the recorded runtime measurements in transaction SE30..

If you set the User-dependent flag when activating the runtime analysis in transaction SICF, the measurement results will be stored under the corresponding user. The entries are then stored in transaction SE30 under the user with which you performed the requests. If the option User-Dependent is not active, the entries are saved under pseudo user SAPSYS.

4. You can find the measurement entries for specific users in transaction SE30 under Runtime Analysis ® Performance Data File ® Other File. Enter the relevant user name here and choose .

5. Select the files that you want to display and choose Analyze (Evaluate). The subsequent graphic shows you the runtimes for the various main components (program environment, database, system).

6. By choosing Goto, you can call various hit lists, which display the runtimes for the various functions and methods separately or by category.

7. By choosing Sort, you can sort the displayed elements according to runtime. This helps you to see which method and function calls are the most time-consuming

Re: Runtime analysis, SE30, ERROR

Former Member — Mon, 12 May 2008 04:56:26 GMT

Hi,

generally such error occurs when the runtime exceeds certain limit...this will cause to do a performance tuning to ur program as it is exceeding some time limit for execution.

Regards

Kiran Sure

Re: Runtime analysis, SE30, ERROR

Former Member — Mon, 12 May 2008 07:55:55 GMT

i have used run time analysis before...

i have done analysis for programs running for 20-30 mins. the program i was doing analysis of, is executed in 10-15 mins.

so, i dont think its giving error because its taking too long to execute..

Moreover, i changed the "restriction variant" (the one that is shown on SE30 screen and not the program variant) to accept runtime of 2 hours, but still the same error is shown..

please help.

Re: Runtime analysis, SE30, ERROR

Former Member — Wed, 21 May 2008 10:08:52 GMT

hey,

i found the reason why it was giving error.

it was because of the "call transaction" syntax in report.

when i commented the statement, it gave me no error!

thanks all.

Re: Runtime analysis, SE30, ERROR

Former Member — Wed, 21 May 2008 10:11:00 GMT

i found the answer myself.

see the last reply for more details.

thanks