Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

DBIF_RSQL_SQL_ERROR

Hi,

In our production system form the past couple of days we are getting bunch of ABAP dumps of kind DBIF_RSQL_SQL_ERROR Exception CX_SY_OPEN_SQL_DB. From ST22 :

Runtime Errors DBIF_RSQL_SQL_ERROR

Exception CX_SY_OPEN_SQL_DB

Date and Time 27.04.2009 00:15:52

-


-


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........: "SQL0968C The file system is full. SQLSTATE=57011"

Internal call code.........: "[RSQL/FTCH//BI0/AFIGL_O0240 ]"

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"

"CL_RSODSO_ACTIVATE_REQUESTS===CP" or "CL_RSODSO_ACTIVATE_REQUESTS===CM00D"

"ACTIVATE_DATA_FROM_QUEUE"

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

"ACTIVATE_DATA_FROM_QUEUE" "(METHOD)", 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... "xxxapp7"

Network address...... "192.168.4.38"

Operating system..... "SunOS"

Release.............. "5.10"

Hardware type........ "sun4v"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 18

Shortdump setting.... "full"

Database server... "ndflbwp"

Database type..... "DB6"

Database name..... "BWP"

Database user ID.. "SAPBWP"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Feb 3 2008 21:08:24"

create on........ "SunOS 5.9 Generic_117171-13 sun4u"

Database version. "DB6_81 "

Patch level. 146

Patch text.. " "

Database............. "DB6 08.02., DB6 09."

SAP database version. 700

Operating system..... "SunOS 5.9, SunOS 5.10"

Memory consumption

Roll.... 2715056

EM...... 0

Heap.... 15305200

Page.... 24576

MM Used. 12282376

MM Free. 5687520

-


-


User and Transaction

Client.............. 700

User................ "xxxxxx"

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

Transaction......... " "

Transactions ID..... "49F4A670A6415620E1000000C0A80426"

Program............. "CL_RSODSO_ACTIVATE_REQUESTS===CP"

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

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

-


-


Information on where terminated

Termination occurred in the ABAP program "CL_RSODSO_ACTIVATE_REQUESTS===CP" -

in "ACTIVATE_DATA_FROM_QUEUE".

The main program was "RSODSACT1 ".

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

of the (Include) program "CL_RSODSO_ACTIVATE_REQUESTS===CM00D".

The program "CL_RSODSO_ACTIVATE_REQUESTS===CP" was started as a background job.

Job Name....... "BI_ODSABIACTIVATION"

Job Initiator.. "PWC_RAKESH"

Job Number..... 00052100

The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in

procedure "ACTIVATE_DATA_FROM_QUEUE" "(METHOD)", but it was neither handled

locally nor declared

in the RAISING clause of its signature.

The procedure is in program "CL_RSODSO_ACTIVATE_REQUESTS===CP "; its source

code begins in line

1 of the (Include program "CL_RSODSO_ACTIVATE_REQUESTS===CM00D ".

Regards,

Sachin

-


Not what you were looking for? View more on this topic or Ask a question