ABAP MS Access connection program not running in SM37

Question

hie gurus ,i really need your help. i have created a program to extract data from an Ms Access database at certain intervals.
the program runs well if you execute from the ABAP workbench. How ever if i schedule it as a back ground
process its not finishing processing , it remains active through out. i can process it via debugger JDBG in SM37
but on its on it remains active status. the OLE objects i am using are as follows(they):
DATA: conn      TYPE ole2_object,
      rsdb      TYPE ole2_object,
      sql        TYPE c LENGTH 2000.
CREATE OBJECT conn 'ADODB.Connection'.
  CREATE OBJECT rsdb 'ADODB.Recordset'.
CONCATENATE 'Provider=Microsoft.Jet.OLEDB.4.0;'   'Data Source=D:\Documents\ Wm.mdb;'
  INTO sql.
CALL METHOD OF rsdb 'OPEN'
    EXPORTING #1 = sql
    #2 = conn
    #3 = '1'.
DO.
    CALL METHOD OF rsdb 'getstring' = sql
    EXPORTING #1 = '2' "Do not modify!
    #2 = 1    "Do not modify!
    #3 = '|'  "Do not modify!
    #4 = '|'. "Do not modify!
    IF sy-subrc EQ 0.
      REFRESH it_temp.
      SPLIT sql AT '|' INTO TABLE it_temp.
      LOOP AT it_temp INTO wa_temp.
        CASE sy-tabix.
          WHEN 1.
            wa_prd-field1 = wa_temp-value.
          WHEN 2.
            wa_prd-field2 = wa_temp-value.
          WHEN 3.
            wa_prd-field3 = wa_temp-value.
          WHEN 4.
            wa_prd-field4 = wa_temp-value.
          when others.
        ENDCASE.
      ENDLOOP.
      APPEND wa_prd TO it_prd.
      CLEAR wa_prd.
    ELSE.
      EXIT.
    ENDIF.
  ENDDO.
FREE OBJECT conn.
FREE OBJECT rsdb.
thanks in advance.

Answer 1

Dear bhaskar:
Thanks for your reply. We have considered balancing the system to the other node or reboot the system to free resources, in order to re-create the shared memory, but in the past, the balancing process (move resources from one node to the other) has caused problems. Since this is a critical system, stopping (or balancing) is not an option right now, and updating the kernel requires an ABAP stack reboot plus the kernel change : any changes in system configuration requires a longer approval/planning process than a reboot.
Moreover, the OS collecting system and its display in OS06/ST06 has worked fine until now.
Does anyone knows if a reboot has solved this kind of problem in a similar situation?
Thanks in advance
José Enrique