Job E2E_HK_CONTROLLER getting canceled daily after EHP1 upgrade

[Former Member]

Hi, All,

We upgraded solman system to EHP1.Since then; this job is getting canceled daily with following error:

Job Log:

Job started

Step 001 started (program E2E_HK_CONTROLLER, variant , user ID SMD_RFC)

Internal session terminated with a runtime error (see ST22)

Job cancelled

ST22 Dump log shows time out dump

Current patch level is 04

Kindly suggest how can this be solved

[Former Member · Accepted solution]

ST22 Dump log shows time out dump

Brief us in detail......Check how long it has executed in your system and comopare with your current porfile parameter value then increase if required.

OR

Paste ST22 log(only error/what exactly happened)

Regards

Nick Loy

[former_member305388]

Save Environment. Save Yourself.

Hi Mann,

It will be very much appreciable if you can share your experience on the above mentioned time out dump. Please do let us know how you solved it, as we too are getting time_out error in the same screen and same screen line.

User, transaction...

Client.............. 200

User................ "DFEJP"

Language key........ "J"

Transaction......... " "

Program............. "SAPLIBSELND "

Screen.............. "SAPMSSY1 3004"

Screen line......... 2

Kindly help us solve the issue.

Thanks a lot!!

- I'm not an Environmentalist. I'm an Earth Warrior.

[Former Member]

Hi,

After our SPS upgrade, for this same issue, we had to modify temporary the value of the parameter rdisp/max_wprun_time to 60000 via the transaction RZ11.

During the night, the program E2E_HK_CONTROLLER ran for more or less 6000 seconds (it performed millions of records deletions in the table /BI0/F0SMD_PE2H).

The next time this job will run (once every night), there will be really less data to delete and you could then reduce the value of the parameter to its previous value.

I was also advised to rerun the Initial and Basic configuration of the transaction solman_setup. Mostly to ensure the implementation of the last version of the SAP note 1468591 and its subsequent notes.

Kind regards,

Gaëtan Stasse

[Former Member]

I'm SPS 20. Have you re-run diagnostics set-up for monitoring system?

Are you ORACLE? Oracle and infocube has hits in OSS that suggest performance problems exist...

This job cancels with message infocube 0SMD_PE2H is not real time mode.

What does this mean? How can I correct?

This seems to affect EWA for non-abap in that no performance data is found in EWA.

Ken Chamberlain

University of Toronto

[Former Member]

HI Ken,

I'm also the same issue: not able to get the Performance data of a Java system in EWA.

"InfoCube 0SMD_PE2H is not in "real-time mode". Please change first" is log from the E2E_HK_CONTROLLER job.

Kindly help me in resolving this issue.

Regards,

Prasad

[Former Member]

Hi,

Details are:

Runtime Errors TIME_OUT

Date and Time 07.01.2010 01:30:54

Short text

Time limit exceeded.

What happened?

The program "SAPLRRSI" has exceeded the maximum permitted runtime without

interruption and has therefore been terminated.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

After a specific time, the program is terminated to make the work area

available to other users who may be waiting.

This is to prevent a work area being blocked unnecessarily long by, for

example:

- Endless loops (DO, WHILE, ...),

- Database accesses with a large result set

- Database accesses without a suitable index (full table scan)

The maximum runtime of a program is limited by the system profile

parameter "rdisp/max_wprun_time". The current setting is 3600 seconds. If this

.

.

.

Roll.... 16192

EM...... 594970672

Heap.... 0

Page.... 16384

MM Used. 585663104

MM Free. 9274032

r and Transaction

Client.............. 100

User................ "SMD_RFC"

Language Key........ "E"

Transaction......... " "

Transactions ID..... "4B446D5B2E061DFFE10000003630905C"

Program............. "SAPLRRSI"

Screen.............. "SAPMSSY1 3004"

Screen Line......... 2

Information on caller of Remote Function Call (RFC):

System.............. "PS1"

Database Release.... 701

Kernel Release...... 701

Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)

Call Type........... "synchron and non-transactional (emode 0, imode 0)"

Inbound TID.........." "

Inbound Queue Name..." "

Outbound TID........." "

Outbound Queue Name.." "

[sunny_pahuja2]

Hi,

As you can see the logs this job is failing because it is exceeding time limit set for dialog work process. Check whether this background job in your solution manager is fetching some data from any other system. If yes, then probable reason is in other system this program is executing in foreground. Change it to background. Then your problem will be resolved.

Thanks

Sunny