cancel
Showing results for 
Search instead for 
Did you mean: 

problems with TemSe object

Former Member
0 Kudos

Hi Friends,

Jobs are cancelling in our system due to below reason.

Job Log:- Job also cancelled due to process termination. See the system log

SM21 log at the same time :-

Error deleting a TemSe object file.
xxxx\sapmnt\PRD\SYS\global\300JOBLG\0001X02301602X82026, error 13

Database error: TemSe->XRTAB(4)->64 for table TST01 key
XXXXXX\sapmnt\PRD\SYS\global\400JOBLG\0001X023016

02X82

Database error: TemSe->XRTAB(4)->64 for table TST01 key
XXXXXX\sapmnt\PRD\SYS\global\400JOBLG\0001X130005

00X14

Database error: TemSe->XRTAB(4)->64 for table TST01 key [300]JOBLGX13000500X14753,1

Database error: TemSe->XRTAB(4)->64 for table TST01 key [300]JOBLGX13000500X14753,1

Please help me in this regards.

Gnanaprakasam

Accepted Solutions (0)

Answers (4)

Answers (4)

0 Kudos

Dear Gnanaprakasam,

I would suggest you to do the following:

Please do a consistency check of the BTC Processing System as follows:

1. Run Transaction SM65

2. Select Goto ... Additional tests

3. select these options: Perform TemSe check

Consistency check DB tables

List

Check profile parameters

Check host names

Determine no. of jobs in queue

All job servers

and then click execute.

4. Once you get the results check to see if you have any inconsistencies in any of your tables.

5. If there are any inconsistencies reported then run the "Background Procesing Analyses" (SM65 .. Goto ... Additional Tests) again.

This time check the "Consistency check DB tables" and the "Remove Inconsistencies" options.

6. Run this a couple of times until all inconsistencies are removed from the tables.

Make sure you run this SM65 check when the system is quiet and no other batch jobs are running as this would put a lock on the TBTCO table till it finishes. This table may be needed by any other batch job that is running or scheduled to run at the time SM65 checks are running.

Regards,

Abhishek

Former Member
0 Kudos

Hello,

It could due to inconsistency in TemSe. Please run consistency check from SP12 and delete the ones marked in red. Then after please schedule spool/temse reorg jobs as per note 48400.

Good Luck.

Thanks,

Siva Kumar

Former Member
0 Kudos

Hi,

I think there might be an issue with file permissions please check the permissions.

there might be issues with read and write permission....

-Srini

Former Member
0 Kudos

Hello

To fix this issue immediately go to sp12-> Temse data storage-> consistency check and delete all.

Then you should schedule a house keeping job to run this consistency and delete old spool objects. Refer the below link

http://help.sap.com/saphelp_nw70/helpdata/en/fc/04ca3bb6f8c21de10000000a114084/content.htm

Thanks & regards

bala