on 12-18-2008 6:25 AM
Hi Experts,,,
Issue i am facing here is all the Background jobs are getting canceled (not only E2Ejobs). There is no logs created. When i check the trace of the work processes, i getting the following errors
ERROR => BtcAuthSet: dy_signi-call failed, rc: 1 [btcjcntl.c 1002]
Thu Dec 18 11:16:45 2008
ERROR => ThCallHooks: event handler rsts_before_commit for event BEFORE_COMMIT failed [thxxtool3.c 260]
ComRolHook(BEFORE_COMMIT, free_all) failed
db_con_commit received an error return code in before-commit action
***LOG R38=> ThICommit3, db_commit98 ( 001024) [thxxhead.c 12982]
Thu Dec 18 11:16:46 2008
WARNING => PfStatWrite: missing STAT_END for opcode STAT_COMMIT [pfxxstat.c 4103]
Thu Dec 18 11:17:44 2008
ERROR => BtcAuthSet: dy_signi-call failed, rc: 1 [btcjcntl.c 1002]
Thu Dec 18 11:17:45 2008
ERROR => ThCallHooks: event handler rsts_before_commit for event BEFORE_COMMIT failed [thxxtool3.c 260]
ComRolHook(BEFORE_COMMIT, free_all) failed
db_con_commit received an error return code in before-commit action
LOG R38=> ThICommit3, db_commit98 ( 001024) [thxxhead.c 12982]
In SM21 i am able to see the log messages as
TemSe input/output to unopened file
TemSe input/output to unopened file
Error at DB commit, return code 001024
Run-time error "DBIF_DSQL2_DEFAULT_CR_ERROR" occurred
Kindly advice
Edited by: Naveen kumar Palanichamy on Dec 18, 2008 8:48 AM
Hi,
Check this note 1274928. The note is in DE.
I have translated it for you
Symptom
During the execution of background RFC (bgRFC) units joined ABAP runtime error SYSTEM_ILLEGAL_STATEMENT or DBIF_DSQL2_DEFAULT_CR_ERROR on.
More terms
bgRFC, SYSTEM_ILLEGAL_STATEMENT, DBIF_DSQL2_DEFAULT_CR_ERROR
Reason
During the processing of bgRFC units (language element <func> FUNCTION CALL BACK GROUND IN UNIT), a transactional KCC, which prevents the execution unit in the application ABAP language elements used to commit or rollback lead. Among these language elements include synchronous and asynchronous RFCs (CALL FUNCTION <func> DESTINATION), WAIT, WORK COMMIT, ROLLBACK WORK and the call of the function 'DB_COMMIT'. During the call of the ABAP language elements on the ABAP runtime error SYSTEM_ILLEGAL_STATEMENT result, the execution of an implicit Commit functions via CALL 'DB_COMMIT' for ABAP runtime error DBIF_DSQL2_DEFAULT_CR_ERROR.
Solution
Either dekativieren the transactional consistency check in the generation-bgRFC of units or change the application so that no actions are carried out to a commit or rollback lead. This is the use of the language element MESSAGE logging of errors allowed.
This will solve you Problem.
Feel free to revert back.
--Ragu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ragu,
Thanks for the translation,
Error is with all background jobs (not only for E2E jobs), to the level i have explored i feel it can be because of the inconsistency in TemSe objects.
If i execute the report to check the consistency of TemSe objects in background, that job is also getting cancelled. In dialog it results in TIME_OUT error.
now i increasd the value of rdisp/max_wprun_time parameter to execute in dialog.
Is there any other way to remove the inconsistent of TemSe objects. Can i delete the JOBLG files directly from OS level, is it a recommended practice?
Pls advice
regards
Naveen
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.