Reg : Run a report RSBTCDEL - Error

[Former Member]

Dear Friends,

When i Run T.Code USMM / SDCCN / and reports RSBTCDEL (Delete Old Background Jobs) that time i got ABAP Runtime error.

Find attached with ABAP Dump report also. My Patch level is Kernel 185 / basis SAPKB70016

/ ABAP - SAPKA70016, ECC 6.0 / MS SQL Server 2005 / windows 2003 server

System Log - SM21 Result :

Database error 601 at FET access to table TBTCO

> [601] Could not continue scan with NOLOCK due to data movement.

Run-time error "DBIF_RSQL_SQL_ERROR" occurred

> Short dump "090611 105105 producti on_PRD_02 " generated

Operating system call recv failed (error no. 10054)

Connection to user 6104 (BASIS ), terminal 19 (SAP-ADMIN ) lost.

Regards

keshav

[Former Member]

Tables are damaged so got this error.

so I mograted system.

[Former Member]

Hi,

Its looks to me some old background jobs are still running,

i could see that "Could not continue scan with NOLOCK due to data movement" in your posted logs.

so try to stop the old jobs first and check whether your database is having any corrupted blocks.

-Srini

[Former Member]

I can't solve it pls give me solution

[JPReyes]

This is the same dump you reporter in this thread

Why are you opening a new one?

regards

Juan

[JPReyes]

Can you post the shortdump?

Regards

Juan

[Former Member]

Hi juan,

Runtime Errors DBIF_RSQL_SQL_ERROR

Exception CX_SY_OPEN_SQL_DB

Date and Time 11.06.2009 10:51:05

-

---

-

---

|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->List->Save->Local File

(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:

-

---

-

---

System environment

SAP-Release 700

Application server... "production"

Network address...... "192.168.1.36"

Operating system..... "Windows NT"

Release.............. "5.2"

Hardware type........ "4x Intel 801586"

Character length.... 16 Bits

Pointer length....... 32 Bits

Work process number.. 3

Shortdump setting.... "full"

Database server... "PRODUCTION"

Database type..... "MSSQL"

Database name..... "PRD"

Database user ID.. "prd"

Terminal................. "JINTSAP103"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Nov 21 2008 01:03:37"

create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"

Database version. "SQL_Server_8.00 "

Patch level. 185

Patch text.. " "

Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"

SAP database version. 700

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

NT 6.0"

Memory consumption

Roll.... 8176

EM...... 9407016

Heap.... 0

Page.... 73728

MM Used. 1512032

MM Free. 576896

-

---

-

---

User and Transaction

Client.............. 400

User................ "BASIS"

Language key........ "E"

Transaction......... "SE38 "

Transactions ID..... "984756DEB0A1F1F8B52A000423BF7C3A"

Program............. "SAPLBTCH"

Screen.............. "SAPMSSY0 1000"

Screen line......... 6

-

---

-

---

Information on where terminated

Termination occurred in the ABAP program "SAPLBTCH" - in

"EXECUTE_BP_JOB_SELECT".

The main program was "RSBTCDEL ".

In the source code you have the termination point in line 429

of the (Include) program "LBTCHF19".

The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in

procedure "EXECUTE_BP_JOB_SELECT" "(FORM)", but it was neither handled locally

nor declared

in the RAISING clause of its signature.

The procedure is in program "SAPLBTCH "; its source code begins in line

403 of the (Include program "LBTCHF19 ".

-

---