on 06-10-2009 10:50 AM
Dear Friends,
I got following errors regularly. when i run t.code RSBTCDEL and RSSNAPDL. what can i do? then Regularly morning i got same morethan 120 Error. User is SAPSYS 000 Client. How can avoid this type of ABAP Runtime Error.
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Date and Time 10.06.2009 15:04:23
Short text
SQL error in the database when accessing a table.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
.
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
How to correct the error
Database error text........: "[601] Could not continue scan with NOLOCK due to
data movement."
Internal call code.........: "[RSQL/FTCH/TBTCO ]"
Please check the entries in the system log (Transaction SM21).
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
"SAPLBTCH" or "LBTCHF19"
"EXECUTE_BP_JOB_SELECT"
If you cannot solve the problem yourself and want to send an error notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System u2192 List u2192 Save u2192 Local File u2192 (Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21. Restrict the time interval to 10 minutes before and five minutes after the short dump. Then choose "System->List->Save->Local File-(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP program: The source code of the program In the editor, choose "Utilities->More Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which actions and input led to the error. The exception must either be prevented, caught within proedure
"EXECUTE_BP_JOB_SELECT" "(FORM)", or its possible occurrence must be declared
in the RAISING clause of the procedure. To prevent the exception, note the following:
Client.............. 400
User................ "BASIS"
Language key........ "E"
Transaction......... "SE38 "
Transactions ID..... "D7A155DEA42EF1EEB52A000423BF7C3A"
Program............. "SAPLBTCH" ( Run a Sap Standard Report RSBTCDEL)
Screen.............. "SAPMSSY0 1000"
Regards
keshav
Read,
Note 976203 - Interception of background jobs: Timeout
That might help
Regards
Juan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Juan,
My System is
ECC 6.0
Database : MS SQL Server 2005
OS - Windows 2003 server
SAP Patches level is Basis - SAPKB70016
ABAP - SAPKA70016
Kernel patch level - 185
when i has update the kernel patches after only i got this error morethan 120 like early morning 4.40 AM to 5.18 AM regularly. what can i do?
Regards
keshav
Tables are damaged So Migrated SAP system
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please check this Note .
This Note Is applicable for Database MSSQL
Note 965530 - 601 Errors in SQL Server.
Note 1250016 - Could not continue scan with NOLOCK due to data movement
Thanks
Rishi Abrol
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Normally time out error comes due to large data fetching.
For RSBTCDEL (delets old background jobs) and RSSNAPDL (deletes old ABAP dumps) change the selectin criteria of the reports.
Run above reports daily in non business working hours and put the different only 1 day
cheers
Sudhakar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.