SPOOL_TEMSE_ERROR SE16N_BATCH Background

Hi All!

I tried run the report SE16N_BATCH twice. In both cases happened the short dump :

Information on where terminated

    Termination occurred in the ABAP program "SAPLKKBL" - in "END-OF-PAGE".

    The main program was "SE16N_BATCH ".

    In the source code you have the termination point in line 262

    of the (Include) program "LKKBLF00".

    The program "SAPLKKBL" was started as a background job.

    Job Name....... "XXXXXX"

    Job Initiator.. "XXXXXX"

    Job Number..... 07550600

Source Code Extract

Line  SourceCde

  232         perform uline_write using gt_stack-s_lprint-width.

  233       else.

  234         perform uline_write using g_print_dialog_popup_mxlsz.

  235       endif.

  236       gflg_uline = 'X'.  "no uline at DATA_OUT_SIMPLE5 Y6BK079490

  237     endif.

  238     endif.

The piece of log in work process:

A  ** RABAX: end no http/smtp

A  ** RABAX: end RX_BTCHLOG RX_VBLOG

A  Error in TemSe system..

A

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

S  {root-id=5367068C61FF41D0E1008000AC16045A}_{conn-id=00000000000000000000000000000000}_0

M Mon May  5 10:51:58 2014

M  kernel runs with dp version 138(ext=120) (@(#) DPLIB-INT-VERSION-138)

M  length of sys_adm_ext is 376 bytes

M  *** ERROR => SiSelEPSet: pollset_ctl: cmd=2  errno=13 [sixxsel.cpp  3089]

M  *** ERROR => SiSelEPSet: pollset_ctl: cmd=1  errno=13 [sixxsel.cpp  3089]

M  ThStart: taskhandler started

M  ThStart: prv_action of W41 = 0x4

M  ThInit: initializing BTC work process W41

Can anyone help me please?

Regards

Marcos

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    May 07, 2014 at 01:23 AM

    Hello,

    SPOOL_TEMSE_ERROR dumps are related to the inconsistencies in the
    TemSe objects.

    Do a consistency check through transaction SP12 then goto TemSe
    Database -> Consistency check firstly.

    Then delete the reported inconsistencies.

    To avoid this in the future, clean up temse/spool as per the
    SAP note 48400.

    Always run RSPO1041 (spool cleanup)
    followed by RSPO1043 (temse cleanup).

    Also review SAP note 98065, to see how the check RSP01043 does
    the Spool consistency checking after release 4.0A. This may
    prevent this error from happening in the future.

    Regards,

    David

    Add comment
    10|10000 characters needed characters exceeded

    • David Liu Marcos Antonio Magalhães Junior

      Hello,

      Seems like you have reached the hard-coded 2GB limit for a temse object while running your job.

      You may need to update the kernel as specified in note 1890546, and the other is to follow the
      recommendations of note 857075.

      Regards,

      David

Skip to Content