SPOOL_INTERNAL_ERROR

[Former Member]

Dear All

we have found following Run time errors

"SPOOL_INTERNAL_ERROR" C

"SAPLKKBL" or "LKKBLF01"

"LIST_OUTPUT_NEW"

"SPOOL_INTERNAL_ERROR" C

"RSPFDB_SEL_COLLECT" or "RSPFDB_SEL_COLLECT"

"START-OF-SELECTION"

"SPOOL_INTERNAL_ERROR" C

"ZMMR_PAC" or "ZMMR_PAC"

"START-OF-SELECTION"

"SPOOL_INTERNAL_ERROR" C

"SAPLKKBL" or "LKKBLF01"

"LIST_OUTPUT_NEW"

"SPOOL_INTERNAL_ERROR" C

"RSBDCREO" or "RSBDCREO"

"PROTOCOL_REORG"

pl reply with correct solution

[Former Member]

This message was moderated.

[former_member227283]

Hi,

did you impliemented note as said by amber.

If not, then impliment it , it will resolve your issue.

Thanks

Anil

[Former Member]

i have checked in SP01 most of the spool are in waiting status

[Former Member]

Hi

Can you please paste the dump over here.

Cheers

Gopal.

[Former Member]

Listen to Amber and Anil. they have given the right answer. Oh, I see gopal vvs also pointed to the same answer. You have to schedule the report every day till kernel update (version 238)

Edited by: M. Loohuizen on Jan 18, 2010 4:47 PM

[Former Member]

Dear All

the problem is resolved, actually some of file system in OS level are full, we have moved some file now it is working fine

regards

[former_member227283]

Hi,

check how many spool request are there on your system.

Thanks,

Anil

[Former Member]

Today 43 same runtime error occured

[former_member198270]

Hi Baikeriker, There is a bug in all SAP releases with started to happen after Dec, 23rd 2009.

All spool requests are created with a false deletion date (i.e. 2099/12/31 or 2100/01/01) causing that the spool files are not deleted within the normal retention time and may cause spool overflows to become more likely.

Details are described in note 1422843. If not implemented you need to implement it.

Regards, Amber S

_______________

[Former Member]

Hi ,

Check the whether the current spool value is above the spool retention value.

Goto Tcode snro in 000 client -> object as spo_num . You can get the current value and the range over there, till you implement the note above specified, you can check and change the spool retention value till 99999 as per SAP note 48284 . Also schedule the check and schedule the standard spool reorganization job this might delete few spool requests, which might free few spool number.

Cheer

Gopal

[Former Member]

Hi,

Run SP12 to check spool consistancy and add the same as your weekly monitoring activity.

for now delete all completed/error spool requests from SP01

Note 48284 - Creating more than 32000 spool requests

Note 130978 - RSPO1041 - Replacement for RSPO0041

Regards,

Nick Loy