cancel
Showing results for 
Search instead for 
Did you mean: 

Errors Always Appears in our SOLMAN 7 EHp1 Server

Former Member
0 Kudos

Dear Guru's

I've tried to solve this problem for almost a week but still have not found the right way and correctly,

I'm the newbie in the SAP system. Please give me the suggestion about this problem as below. Thank you for

your kindness. We have SOLMAN 7 EHP1 in Sun Sparc Ent T5220 within 32Code 16GB Mem.

-


Problems and warning at SM21 :

-


07:43:32 DP Q0 G Request (type NOWP) cannot be processed

07:43:32 DP Q0 G Request (type NOWP) cannot be processed

07:43:32 DP Q0 G Request (type NOWP) cannot be processed

07:43:32 DP Q0 G Request (type NOWP) cannot be processed

07:43:32 DP Q0 G Request (type NOWP) cannot be processed

07:43:32 DP Q0 G Request (type NOWP) cannot be processed

07:45:45 DIA 004 999 SERVICE_COMM P0 3 Role File Overflow (032768 Blocks)

07:45:45 DIA 004 999 SERVICE_COMM R0 B Roll out failed, return code -32

07:45:45 DIA 004 999 SERVICE_COMM R0 B Roll out failed, return code -01

07:45:45 DIA 004 999 SERVICE_COMM R0 H Error handling canceled

07:50:44 DIA 004 999 SERVICE_COMM P0 3 Role File Overflow (032768 Blocks)

07:50:44 DIA 004 999 SERVICE_COMM R0 B Roll out failed, return code -32

07:50:44 DIA 004 999 SERVICE_COMM R0 B Roll out failed, return code -01

07:50:44 DIA 004 999 SERVICE_COMM R0 H Error handling canceled

07:55:44 DIA 004 999 SERVICE_COMM P0 3 Role File Overflow (032768 Blocks)

07:55:44 DIA 004 999 SERVICE_COMM R0 B Roll out failed, return code -32

07:55:44 DIA 004 999 SERVICE_COMM R0 B Roll out failed, return code -01

07:55:44 DIA 004 999 SERVICE_COMM R0 H Error handling canceled

-


Log dev_w4 :

-


R Fri May 21 00:03:31 2010

R *** ERROR => <ROLL-FL> get block: no more free blocks [rrol.c 2170]

M ***LOG P03=> 032768 [rrol.c 1294]

M ***LOG R0B=> ThRollOut, rrol_out (-32) [thxxmem.c 1791]

M ***LOG R0B=> ThISend, ThRollOut (-01) [thxxhead.c 10188]

M in_ThErrHandle: 1

M *** ERROR => ThISend: ThRollOut (step 5, th_errno 8, action 1, level 1) [thxxhead.c 10651]

M ThResetEmMagic: reset em magic for T204/M0/I0

M

M ThCheckMemoryState (0, 0, 1)

M *** ERROR => ThCheckMemoryState: no roll context [thxxmem.c 311]

M *** ERROR => ThIAMDel2: failed to roll in context, cleanu might fail [thxxmode.c 2855]

M ThIAMDel2: last active mode (0) delete tid (204)

M ThIUsrDel (23, 1)

M ThCheckMemoryState (0, 0, 1)

M *** ERROR => ThCheckMemoryState: no roll context [thxxmem.c 311]

M ThIGetT100: read tskh msg 23 from msg area 14 (db rel 701)

M ThCleanPrevUser: clean U13657 T337 M0 I0 no VM clean state DP_DEFAULT_CLEANING clean counter 1

M ThCleanPrevUser: saved MODE_REC = 80

M PfStatDisconnect: disconnect statistics

M ThCleanPrevUser: set clean state of T337/M0 to DP_DEFAULT_CLEANING

M ThIAMDel: delete tid/mode 337/0 (th_errno 23, release 1)

M ThIDeleteMode (337, 0, 3, ><, 0, 255, TRUE)

M ThIDeleteMode: no modes found ..

M no sub modes

M ThCheckMemoryState (0, 0, 1)

M *** ERROR => ThCheckMemoryState: no roll context [thxxmem.c 311]

M *** ERROR => ThIAMDel2: failed to roll in context, cleanu might fail [thxxmode.c 2855]

M ThIAMDel2: last active mode (0) delete tid (337)

M ThIUsrDel (23, 1)

M ThCheckMemoryState (0, 0, 1)

M *** ERROR => ThCheckMemoryState: no roll context [thxxmem.c 311]

M ThIGetT100: read tskh msg 23 from msg area 14 (db rel 701)

M ThPlgSendErrTxt2: plugin in state DP_PLUGIN_ERROR_SENDING, ignore

M ThResFree: no complete user context, switch to short free

M ThResFree: free resources of U13657 M0 I0 (normal mode, short free) at level 3, errno=23, db_action=TH_DB_ROLLBACK, pooling=1

M ThResFree: reset spa state for user T337/U13657/M0

M ThCheckEmState: check ATTACH for em hdl 1162

M ThCheckEmState: call EmContextAttach (em_hdl=1162)

-


Edited by: Agus Wibawa on May 21, 2010 8:22 AM

Accepted Solutions (1)

Accepted Solutions (1)

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

As per logs, it looks like the problem with Roll parameters. Fine tune your roll memory parameters.

Thanks

Sunny

Answers (1)

Answers (1)

Paul_Babier
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Agus

The error message indicates that the dispatcher process was not able to

deliver a NOWP message to a user context that does no longer exists.

This happens if a batch process issues an asynchronous RFC that shall

send a response when it finishes. However, the batch job does not wait

to collect the answer.

When the dispatcher tries to pass the result of the aRFC to the batch

process, it realizes that the context that issued the RFC no longer

exists and prints out the message.

YOu can safely ignore the message.

And for more information, Please refer to the notes:

27617 Syslog Q0G, scratch area too small

191234 Syslog: Q0G K request (type NOWP) cannot be ...

681085 Scratch area is too small, opcode 6

62239 Termination when maintaining syslog filters

This information should help a lot.

Regards,

Paul