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

[former_member325638]

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

[former_member185239 · Accepted solution]

Hi Varun Kumar,

Please follow the below sapnote

857075 - TemSe: Core DUMP in rstsf_tel_040_22707_131

With Regards

Ashutosh Chaturvedi

[former_member325638 · Accepted solution]

Thanks Ashutosh,

Within note 857075; I found another note 1890546; which states that the limit no longer applies by upgrading to latest kernel. But as per recommendation; we are already at a higher kernel patch.

We are checkign further. These two notes helped us in moving a step further

Thanks

Varun

[former_member325638 · Accepted solution]

Hi All,

According to note 1890546, found with the help of note provided by Ashish. We noticed that the issue should nto occur in our kernel version. Based on this; wle raised this to SAP and their development team has now come up with an answer that the issue will be resolved in kernel patch level 225. Till then, 2GB limit issue will remain there and cannot be avoided

Thanks

Varun

[Former Member]

I had an issue with my TEMSE space. The daily program we were using to clear out our TEMSE space was out of date and SAP had a new one. Our TST03 table grew out of control. Actually Oracle created a LOB file for it of 180 GBs.

I had to truncate TST03 and TST01, use the proper SAP job and now it's working perfect.

You can also change the settings to dump your Temse into the file system,

Google around, tons of info out there.

[Former Member]

My issues in detail.   http://scn.sap.com/thread/3441525

[former_member325638]

Thanks Joshua for the details;

But the link provides solution related to overall space. We have enough space on filesystems and tablespaces etc. We face issue when one Temse object of an active process touches 2 GB.Note 1890546 found; appears close to the issue; but we have required kernel patch.

Thanks

Varun

[former_member188883]

Hi Varun,

Whats the kernel patch level  and SAP release of the system ?

Regards,

Deepak Kori

[former_member325638]

Hi Deepak,

Kernel patch level is 721_EXT patch level 210. Solaris on 64-Bit Unicode.

SAP_BASIS release 731 patch level 6 (SAPKB73106).

Thanks

Varun

[former_member188883]

Hi Varun,

With help from OS admin could you please adjust the ulimit to unlimited.

Some information in link http://www.sunsolarisadmin.com/general/ufs-maximum-file-size-2gb-restriction-in-sun-solaris/

Hope this helps.

Regards,

Deepak Kori

[Former Member]

Hi Varun,

SAP can handle spools that are with <2 GB only as per the SAP link provided by you.

So there  is no other alternative apart from from splitting the data that you are trying to process.

Regards,

Srini

[former_member188883]

Hi Varun,

From the SAP help link

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.

Check whether splitting is possible.

Regards,

Deepak Kori