Error deleting a TemSe object file.

[santoshsap]

capture.jpgDear Team,

we are getting alerts in SM21 every minute , Error deleting a TemSe object file. \\SAPCS\sapmnt\ECP\SYS\global\100JOBLG\0001X10310600X76338, error 13 .

Could you please help me on this.

Regards,

santosh

[santoshsap]

Hello Team,

Thanks for your valuable answers ,

Envrionment : ECC 6.0 EHP 6

Windows 2012

DB: MS SQL 2012 R2

@ David: i have checked the permission , it has full authorization access to SID<ADM> to the DIR_GLOBAL directory,

@sriram : there are huge files generated , i dont see any logs which is readable format.

@CJC : if i use the method of MESSAGE command to output a message , it is a production envrionement we are approaching ABAP team on it,

i tried to execute the RSTS0024 command to delete the Orphaned job logs manually to clear some space for temporary solution.

Regards,

santosh

[kaus19d]

Hi santosh,

Is it possible to run RSPO0041 for older spool deletion & the check the SP12 TemSe

Thanks,

Kaushik

[kaus19d]

Hi,

Would suggest to check the job for Temse deletion. Do the Check-Consistency in SP12. Next to check permission as suggested by David as well as the exe files. Next to reschedule the standard SAP Temse jobs, or you can check if any job-variants are already set for this. Deletion of big Temse could require the involvement of dynamic parameter rdisp/max_wprun_time=0

Thanks,

Kaushik

[DavidLY]

Hello Santosh,

The error code of deletion error is 13.
According to SAP note 1510259, error 13 means permission issue, so you can look into the OS level and make sure that the user <SID>ADM has the proper authorization for DIR_GLOBAL directory.

Regards,

David

[Sriram2009]

Hi Samtosh.

Thanks for your information.

Could you check the status of the files in the following location \\SAPCS\sapmnt\ECP\SYS\global\100JOBLG\0001X10310600X76338, ?

Regards

SS

[former_member522291]

Hello Jami,

Which OS and kernel you are using now?

Could you try to see the note

1950387 - F6C: Error deleting a TemSe object file

Reason and Prerequisites

As of Kernel 7.21, trivial job log files are deleted at once by default, when the job ends. See also SAP Notes 1468596 and 1707974.
In Windows systems, deleting a trivial job log file can sometimes fail. This has no negative effects at all, but message F6C is always written to the system log.

The reason for the failure to delete the job log file is as follows: Some jobs start asynchronous processes that are still running when the job has ended. These processes have inherited a file handle for the job log file. In Windows, a file cannot be deleted if another process still has an open handle for this file.

Solution

As already mentioned, the problem described here has no negative effects at all. The kernel patches specified in this SAP Note suppress message F6C if the deletion of a trivial job log file fails when a job ends.

As an alternative solution, you can use the MESSAGE command to output a message in the program that ran in the batch job in question. The SAP system then no longer tries to delete the job log following the end of the job.

BR

CJC

[santoshsap]

Hello Sriram,

I tried all those methods , unable to fix the issue.

Regards,

santosh

[Sriram2009]

Hi Samtosh.

Kindly refer the SCN thread with same error message https://answers.sap.com/questions/8957441/problems-with-temse-object.html

Regards

SS