Catalog publication fails with SYSTEM_ON_COMMIT_INTERRUPTED (dump)

[Former Member]

Hello all

I'm facing a new problem here. We get short dumps SYSTEM_ON_COMMIT_INTERRUPTED when trying to publish our master catalog. We're still on CCM 2.0 with SP03.

Main program = /CCM/PE_START_REG_PUBLICATION

Program = /CCM/CL_CHAR_VALUATION_MANAGERCP

In SAVE_HISTORY

The program exits / the dump happens in line 37:

   7         lt_history_del     TYPE t_history_db.
   8
   9 * only necessary if history was activated
  10   CHECK gv_history_active = abap_true.
  11
  12 * handle the history table
  13   LOOP AT gt_history_buf REFERENCE INTO lr_history_buf.
  14
  15     LOOP AT lr_history_buf->rec REFERENCE INTO lr_history_obj_buf.
  16
  17       CASE lr_history_obj_buf->rec_op.
  18
  19         WHEN /ccm/cl_data_access_constants=>co_operation_create.
  20           lr_history_obj_buf->rec-timestamp = iv_timestamp_commit.
  21           APPEND lr_history_obj_buf->rec TO lt_history_ins[].
  22
  23         WHEN /ccm/cl_data_access_constants=>co_operation_update.
  24           APPEND lr_history_obj_buf->rec TO lt_history_upd[].
  25
  26         WHEN /ccm/cl_data_access_constants=>co_operation_delete.
  27           APPEND lr_history_obj_buf->rec TO lt_history_del[].
  28
  29       ENDCASE.
  30
  31     ENDLOOP.
  32
  33   ENDLOOP.
  34
  35 * write records on database
  36   IF lt_history_ins[] IS NOT INITIAL.
  37     INSERT /ccm/d_value_h FROM TABLE lt_history_ins[].
  38   ENDIF.
  39
  40   IF lt_history_upd[] IS NOT INITIAL.
  41     UPDATE /ccm/d_value_h FROM TABLE lt_history_upd[].
  42   ENDIF.
  43
  44   IF lt_history_del[] IS NOT INITIAL.
  45     DELETE /ccm/d_value_h FROM TABLE lt_history_del[].
  46   ENDIF.
  47
  48 ENDMETHOD.

Does anyone have an idea what happened here and what could be done to fix this?!?

With the beginning of this year we added some characteristics to our catalog schema. We transfer content from ERP system via XI using catalogue_update_notification_in. This starts a process / background job in CCM (AUTH_UPDATE) which also fails exactly the same way.

For several years this worked well.

Many thanks in advance

Renaud

[krzysztof_murkowski2]

Hi,

check if you have many entries in the history table /CCM/D_VALUE_H.

In such case you can try to reorganise them with program /CCM/DELETE_HISTORY_BG.

regards,

Kris

--

my ABAP examples

[http://www.kerum.pl/infodepot/]