Skip to Content
0
Mar 21, 2014 at 10:09 AM

Temse Part Size Limit reached. error 1 set in spool C call

594 Views


Hi Experts,

We have been recently facing one problem with job getting cancelled with error "error 1 set in spool C callerror 1 set in spool C call". Upon looking under the trace files we found below logs

"

Temse Part Size Limit reached: 2147478498 + 5142 + 144 + 10 -> 2147483794

*** ERROR => error 1 set in spool C call [rspoabap.c 622]

{root-id=8021280BFB4E1ED3ABC569C3FB7E5DA9}_{conn-id=00000000000000000000000000000000}_0

*** ERROR => error message 'Error from TemSe' in spool C call [rspoabap.c 865]

{root-id=8021280BFB4E1ED3ABC569C3FB7E5DA9}_{conn-id=00000000000000000000000000000000}_0

called by RSPO_SR_WRITE_OTF

*** ERROR => missing close of spool request [rspoooh.c 1175]"

Searching further on it; we found below link which states that "TemSe cannot administer objects that require more than two gigabytes of storage space, regardless of whether the objects are stored in the database or in the file system. Spool requests of a size greater than two gigabytes must therefore be split into several smaller requests"

http://help.sap.com/saphelp_nw04/helpdata/en/d9/4a8f9c51ea11d189570000e829fbbd/content.htm

We checked the spool size as well; it reached 2 GB when this error occured.

But users are complaining that they get spools more than 2 GB on jobs. The page limit is set to unlimited and spool size is around 39GB.

Could you please shed some light on this Temse limit of handling not ore than 2GB of spool request. Is it temporary size limit or limit of overall spool? And is it possible to have a spool request created by a job which is more than 2 GB?

Please advise so that we have a justification to force split the selection to reduce spool size.

Thanks

Varun