Process chain - ODS Activation error

Question

Hello All,
I have a process chain which has the following data load sequences:
Load data to ODS
Activate ODS
Load data to ODS2
Activate data ODS2
Load data to ODS3
Activate ODS3.
Used the Program to RSPC_SYNCHRONOUS_RUN to schedule the process chain in Background.
When the process chain is executed in background it loads the data to ODS1 and Activation process is not happening. It registers short dump like shown below at the end. But when i execute the same process chain in RSPC, Schedule option with Start variant set to immediate, it is activating the ODS Data and completes the process chain Succesfully.
Help me to solve this problem.
ABAP Short dump information:
Invalid interruption of a database selection.
t happened?
Error in ABAP application program.
The current ABAP program "GP4BRKGANFKJY5K2A3ACVGAPTN4" had to be terminated
  because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
Unable to perform database selection fully.
record.
t can you do?
If the error occurs in debugging mode, you should first run the process
without debugging activated.
If the error persists outside debugging, you must check the application
program more closely.
No error requiring recovery has occurred.
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
  termination messages, especially those beyond their normal deletiondate.
is especially useful if you want to keep a particular message
Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
     neither
    caught nor passed along using a RAISING clause, in the procedure "ACTIVATE_ODS"
     "(FORM)"
    Since the caller of the procedure could not have expected this exception
     to occur, the running program was terminated.
    The reason for the exception is:
    One of the database selections included a database commit.
    The selection was then supposed to continue. Before a
    database commit, however, all outstanding database selections must be
    concluded.
    Possible causes in the application program:
    Within a loop (SELECT/LOOP/EXEC SQL), one of the following
    statements is used:
    - MESSAGE (apart from MESSAGE S...)
    - COMMIT WORK
    - ROLLBACK WORK
    - CALL SCREEN
    - CALL DIALOG
    - CALL TRANSACTION
    - SUBMIT
    - BREAK-POINT
    - WAIT
    In debugging mode, a program sometimes triggers
    a "COMMIT WORK" during the database selection. As a result
    this termination may also occur in debugging mode with a correct
    program.
A "COMMIT WORK" during debugging may be due to the following reasons:
1. A program or screen was regenerated
    and updated in the database.
2. Each user needs a private process in debugging mode, but
    the number of available processes is restricted. If this
    limit is exceeded, each debugging step then requires a
    "COMMIT WORK".
The error occurred in a statement that accesses the table "/BIC/AZXOQMATR40 ".
Thanks in Advance.
Points will be assigned.
Regards
M.A

Answer 1

Hi,
If it is a daily process chain u define it on a periodic basis in the variant and it'll run successfully.
I guess the DUMP may be due to less processes at the time u run...It is gving the same in the dump also..
So when u run the chain immediate in the BKGD the ODS will be automatically getting the required processes dailog and bkgd to run according to ur settings and it was successful..
U try to execute the chain using FM: RSPC_API_CHAIN_START and give the tecnical name of the chain under I_CHAIN filed and conitinue...It'll scedule the chain in the BKGD only and if it is a periodic one the chain will be automatically ready for the next run also...
rgds,