on 04-22-2009 5:35 AM
Dear Friends,
I got around 120 ABAP runtime error in PRD system regularly(Daily) for the period of 4.40 AM to 5.18 AM.
How can i solve following ABAP Runtime Error, Pls give me suggession.
SM21 - System Logs:
Client : 000
User : sapsys
Package : SDYN, SABP, SBAC
Prgm : SAPMSSY2
Problem Class : SAP Web AS Problem
Access table : TBTCO
Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20090422051802production_PRD_02 SAPSYS 000)
How to correct the Error
==================
"RESCHEDULE_PERIODIC_JOBS"
The exception must either be prevented, caught within proedure
"RESCHEDULE_PERIODIC_JOBS" "(FORM)", or its possible occurrence must be
declared in the
RAISING clause of the procedure.
Information on where terminated:
=======================
Termination occurred in the ABAP program "SAPMSSY2" - in
"RESCHEDULE_PERIODIC_JOBS".
The main program was "SAPMSSY2 ".
In the source code you have the termination point in line 4115
of the (Include) program "SAPMSSY2".
The program "SAPMSSY2" was started as a background job.
Job Name....... " "
Job Initiator.. " "
Job Number..... " "
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "RESCHEDULE_PERIODIC_JOBS" "(FORM)", but it was neither handled
locally nor declared
in the RAISING clause of its signature.
The procedure is in program "SAPMSSY2 "; its source code begins in line
3823 of the (Include program "SAPMSSY2 ".
Regards
kesav
Hi
1) Check the dev_w* trace of the work process corresponding to the entry in the system log, to get more information on "Transaction Canceled 00 671 "
2) DBIF_RSQL_SQL_ERROR- refers to database error in the RSQL module of the database interface,usually relating to timeouts. See Note 976203 - Interception of background jobs: Timeout
3) Contact ABAP team and see what they have to say on this, as mentioned in the dump:
"The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "RESCHEDULE_PERIODIC_JOBS" "(FORM)", but it was neither handled
locally nor declared in the RAISING clause of its signature. "
4) Moreover, the ABAP program SAPMSSY2 is used to switch operation modes assigned to instances, refer : http://help.sap.com/saphelp_nw70/helpdata/en/c4/3a5f1f505211d189550000e829fbbd/content.htm
5) The most common cause for an operation mode switch failing is inconsistencies in the total number of work processes or in the profiles.You must define the whole 24u2212hour range for operation modes to work. You cannot leave any time period unassigned, otherwise the switch will not be possible and can cause problems in the background processing system. check the operation mode from control panel refer: http://help.sap.com/saphelp_nw04/helpdata/en/c4/3a5f7a505211d189550000e829fbbd/content.htm
6) Explore the follwoing cases as well:
SAP note Note 208924 - Operation mode switch incorrect
SAP Note 1082783 - Work processes hang after operation mode switching
Ravi
Edited by: ravi raj on Apr 23, 2009 8:20 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Tables are Damaged so daily generated ABAP runtime errors. So Migrated SAP systems
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
R there any cancelled jobs in SM37 during that period 4.40 AM to 5.18 AM.
What there any activity happend in the system like applying patches or upgrading kernel.
Check out all the standard background jobs are scheduled in the sytem.
Regards
Uday
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
76 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.