cancel
Showing results for 
Search instead for 
Did you mean: 

SM37 Jobs

Former Member
0 Kudos

Hi Friends,

Hi,

The SM37 jobs have been failing, this is the message in the system log Failed to create log for job and in the log of the sm37 Job also cancelled due to process termination.

When checking the SM66, SM51 work process i could see all the process are in Stopped and private mode.

We have 2 application servers and on datbase server. On the application server one there are nearly 290 users where all the process went to the stopped private mode .

We have logon balancing. But idon't understand how it happened.

At the moment i have cancelled without core some of the processes.

Can some one help me to resolve regd the logon balancing and process in the stopped and private mode.

Please help regd the same.

Thanks.

Accepted Solutions (1)

Accepted Solutions (1)

markus_doehr2
Active Contributor
0 Kudos

Having "PRIV" mode and "stopped" doesn´t mean that the system isn´t running any more. PRIV means, that the available extended memory for the user context is exhausted and the system starts using heap memory which is exclusively assigned to the user/workprocess.

I´d first check SM04, add the "memory" column and check which users are using so much memory. You can also do that using ST02 - Detailed analysis - SAP Memory - Mode List

Also check the parameters

abap/heap_area_dia

abap/heap_area_nondia

abap/heap_area_total

Markus

Former Member
0 Kudos

I have checked as per your suggestion , the limit for the

abap/heap_area_dia 2000000000

abap/heap_area_nondia 2000000000

abap/heap_area_total 2000000000

I could see the below memory in SM04 in ascending order for the users.

365,795,172

348,111,488

237,102,264

216,614,252

208,653,876

171,436,640

143,294,584

130,758,676

97,564,588

Apart from increasing the parameter , is there anything i can do.

What could be the rsolution for the same.

thanks

markus_doehr2
Active Contributor
0 Kudos

> I could see the below memory in SM04 in ascending order for the users.

> 365,795,172

> 348,111,488

> 237,102,264

> 216,614,252

> 208,653,876

> 171,436,640

> 143,294,584

> 130,758,676

> 97,564,588

wow.. what HUGE applications...

Check note 425207 - SAP memory management, current parameter ranges

Markus

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

please check the ztta/roll_* parameter values.

refer to

http://help.sap.com/saphelp_nw70/helpdata/EN/dd/d0256805734b8b849c14c9cb33a266/content.htm

-Gokul

Former Member
0 Kudos

Hello Anoroop

Can u please check at the OS level and see if /sapmnt/SID directory is filled up.. Coz the job is getting cancelled with the error stating cant create a log ..

Regards,

Ershad Ahmed

Former Member
0 Kudos

Hi,

As suggested i have checked the /sapmnt/<SID>, it is 40% used.

The background jobs have failed again, the problem it is unable to create the job log, due to which is jobs have terminated., that too jobs are terminated only for 45 minutes and latter on they ran on fine.

What do you suggest in regd the same.

Thanks