Termination occurred in the ABAP program "SAPLV12A"

[former_member212731]

Hello, we have an ABAP Runtime error in transaction FTXP on IDES ECC 6.0.

So far we have done

- SGEN

- Reorganizing table T007A

- Reorganizing tablespace PSAPSR3

- Reorganizing index T007A~0

Runtime error still exists, any ideas what more to check or try?

Error log (ST22) is enclosed below.

*****************************************************************************************************************************************************************************************************

Runtime Errors         TIME_OUT

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|Short text                                                                                        |

|    Time limit exceeded.                                                                          |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|What happened?                                                                                    |

|    The program "SAPLV12A" has exceeded the maximum permitted runtime without                     |

|    interruption and has therefore been terminated.                                               |

|                                                                                                  |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|What can you do?                                                                                  |

|    Note down which actions and inputs caused the error.                                          |

|                                                                                                  |

|                                                                                                  |

|    To process the problem further, contact you SAP system                                        |

|    administrator.                                                                                |

|                                                                                                  |

|    Using Transaction ST22 for ABAP Dump Analysis, you can look                                   |

|    at and manage termination messages, and you can also                                          |

|    keep them for a long time.                                                                    |

----------------------------------------------------------------------------------------------------

|Source Code Extract                                                                               |

----------------------------------------------------------------------------------------------------

|Line |SourceCde                                                                                   |

----------------------------------------------------------------------------------------------------

|   64|            i_dikom    = lv_table                                                           |

|   65|            i_field    = lv_field                                                           |

|   66|          IMPORTING                                                                         |

|   67|            e_append   = lv_append                                                          |

|   68|            e_switchid = lv_switch.                                                         |

|   69|        IF lv_switch IS NOT INITIAL.                                                        |

|   70|*         message i770(vk).                                                                 |

|   71|          PERFORM protokoll USING msgtp_info arbgb_vk '770'                                 |

|   72|                                  lv_table  lv_field                                        |

|   73|                                  lv_append lv_switch no.                                   |

|   74|*         no exception possible: notify the generator                                       |

|   75|          sfw_write_error = yes.                                                            |

|   76|                                                                                            |

|   77|*         message w773(vk).                                                                 |

|   78|          PERFORM protokoll USING msgtp_warnung arbgb_vk '773'                              |

|   79|                                  rw_reportname no no no no.                                |

|   80|          EXIT.                                                                             |

|   81|        ENDIF.                                                                              |

|   82|      ENDIF.                                                                                |

|   83|    ENDIF.                                                                                  |

|   84|    PERFORM protokoll USING msgtp_fehler arbgb_vk '806'                                     |

|   85|                            rw_reportname no no no no.                                      |

|   86|  ENDIF.                                                                                    |

|   87|                                                                                            |

|   88|* write report (even though there are syntax errors)                                        |

|   89|  IF rw_trdir-subc = subc_include.                                                          |

|   90|*   specify program type explicitly (executable is default)                                 |

|   91|    INSERT REPORT rw_reportname FROM rw_coding UNICODE ENABLING 'X'                         |

|   92|      PROGRAM TYPE rw_trdir-subc.                                                           |

|   93|  ELSE.                                                                                     |

|>>>>>|    INSERT REPORT rw_reportname FROM rw_coding UNICODE ENABLING 'X'.                        |

|   95|  ENDIF.                                                                                    |

|   96|  IF sy-subrc = 0.                                                                          |

|   97|    PERFORM protokoll USING msgtp_info arbgb_vk '851'                                       |

|   98|                            rw_reportname no no no no.                                      |

|   99|  ELSE.                                                                                     |

|  100|    PERFORM protokoll USING msgtp_fehler arbgb_vk '850'                                     |

|  101|                            rw_reportname no no no no.                                      |

|  102|  ENDIF.                                                                                    |

|  103|                                                                                            |

|  104|* write TRDIR                                                                               |

|  105|  PERFORM trdir_upd USING rw_reportname                                                     |

|  106|                          rw_trdir.                                                         |

|  107|                                                                                            |

|  108|* write documentation                                                                       |

|  109|  PERFORM docu_upd TABLES rw_docu                                                           |

|  110|                   USING  rw_langu                                                          |

|  111|                         'RE'                                                               |

|  112|                          rw_reportname.                                                    |

|  113|* write textpool                                                                            |

----------------------------------------------------------------------------------------------------

Please just include the relevant portions of the dump. Message was edited by: Rob Burbank

[former_member223981 · Accepted solution]

I dont know what is causing the long runtime.

However, to avoid the dump, you may want to consider extending the rdisp/max_wprun_time parameter. This is explained in SAP note 25528.

[former_member212731]

Thanks for the comments!

There were two problems

1) maximun runtime exceeded

-> runtime error in transaction FTXP

2) Buffer -> Tables -> Generic Key row in column Swaps was in red

--> in transaction ST02

Some parameters were updated in \usr\sap\[SAPSID]\SYS\profile\[SAPSID]_DVEBMGS02_[SAPServer] file

a) abap/buffersize = 800000

b) zcsa/table_buffer_area = 120000000

c) zcsa/db_max_buftab = 20000

d) rdisp/max_wprun_time=3600

As entering rdisp/max_wprun_time=3600 seemed to resolve the problem for runtime error (Termination occurred in the ABAP program "SAPLV12A"). Transaction FTXP execution lasted some 30min for first time and after that only normal couple of seconds. SGEN was done to client but maybe something was not compiled or generated totally after all.

Updating parameters a-c described above resolved the ST02 buffer problem.

Thanks for the support!

kuki

[yuri_ziryukin]

Hello Kuki,

basically SGEN was not so much relevant here. In your case the actual source code of certain report had to be generated and written to the database. 30 minutes were quite long. Either you had many condition types which caused generation of many access reports, or the issue was in the locking of REPOSRC table the longer time...

Regards,

  Yuri

[yuri_ziryukin]

Hello,

the dump does not look suspicious in terms of large internal tables or something like that. The program most probably hangs trying to insert the generated source code of the condition access report into the database. I would check for possible locks/deadlocks in DB administration transactions (e.g. DBACOCKPIT).

Regards,

  Yuri