cancel
Showing results for 
Search instead for 
Did you mean: 

DBIF_RSQL_INVALID_RSQL

Former Member
0 Kudos
278

Hi All,

We are getting below mentioned runtime error while executing some tcodes. Also we could find sm21 dump as Database error -901 at INS access to table ARFCSDATA> SQL system error. MSGID= Job=037811/DEV05/WP01. Earlier we had some issue with workprocess going onto private mode we resolved it by increasing parameter em/initial_size_MB. We are using kernel release 701 pacakage level 66. Please advice

Runtime Errors DBIF_RSQL_SQL_ERROR

Exception CX_SY_OPEN_SQL_DB

Date and Time 27.07.2010 10:23:18

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........: "SQL system error. MSGID= Job=037400/DEV05/WP01"

Internal call code.........: "[RSQL/INSR/ARFCSDATA ]"

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"

"SAPLARFC" or "LARFCU03"

"END_TRANSACTION_NONE_LOCAL_UPD"

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

"END_TRANSACTION_NONE_LOCAL_UPD" "(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 701

Application server... "SYSDEV"

Network address...... " "

Operating system..... "OS400"

Release.............. "6.1"

Hardware type........ "00060004BD15"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 1

Shortdump setting.... "full"

Database server... "SYSDEV"

Database type..... "DB400"

Database name..... "DEV"

Database user ID.. "R3DEVDATA"

Terminal.......... "sap-dsds"

Char.set.... "C"

SAP kernel....... 701

created (date)... "Oct 25 2009 21:54:57"

create on........ "AIX 2 5 00CB5A5B4C00 (IBM iSeries with OS400)"

Database version. "DB4_53"

Patch level. 66

Patch text.. " "

Database............. "V5R3, V5R4, V6R1"

SAP database version. 701

Operating system..... "OS400 3 5, OS400 4 5, OS400 1 6"

Memory consumption

Roll.... 16192

EM...... 12569544

Heap.... 0

Page.... 40960

MM Used. 5998912

MM Free. 2377984

User and Transaction

Client.............. 300

User................ "OCCADMIN"

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

Transaction......... "PFCG "

Transactions ID..... "4C4E7BD97AA300D4E1008000C0050208"

Program............. "SAPLARFC"

Screen.............. "SAPLPRGN_TREE 0321"

Screen line......... 5

Information on where terminated

Termination occurred in the ABAP program "SAPLARFC" - in

"END_TRANSACTION_NONE_LOCAL_UPD".

The main program was "SAPLPRGN_TREE ".

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

of the (Include) program "LARFCU03".

The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in

procedure "END_TRANSACTION_NONE_LOCAL_UPD" "(FORM)", but it was neither handled

locally nor declared

in the RAISING clause of its signature.

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

40 of the (Include program "LARFCU03 ".

Source Code Extract

Line SourceCde

359 * Wenn keine Outbound tRFC/qRFC mehr vorhanden.

360 IF sendstate[] IS INITIAL.

361 PERFORM database_commit.

362

363 PERFORM trfc_dequeue_all.

364

365 * ARFC_END_VB muss getriggert werden um die gesperrten BGRFCs

366 * nach der Verbuchung wieder frei zu schalten.

367 IF kanal = verbucher AND vb_called = space AND bgrfc_active <> space.

368 vb_called = 'X'.

369 CALL FUNCTION 'ARFC_END_VB' IN UPDATE TASK

370 EXPORTING

371 vbkey = vbkey.

372 ENDIF.

373

374 IF write_qin <> space.

375 READ TABLE qin_qname INDEX 1.

376 IF qin_qname-qstate <> qs_noexec.

377 CALL FUNCTION 'QIWK_SCHEDULER_ACTIVATE_GROUP'

378 TABLES

379 name_queue = qin_qname.

380 ENDIF.

381 write_qin = space.

382 REFRESH qin_qname.

383 ENDIF.

384 ENDIF.

385

386 * Wenn noch tRFC/qRFC vorhanden.

387 IF sendstate[] IS NOT INITIAL.

388 * Wenn tRFC/qRFC-Daten vorhanden sind diese in DB schreiben

>>> INSERT arfcsdata FROM TABLE senddata.

390 IF sy-dbcnt = 0.

391 MESSAGE a502(sy).

392 ENDIF.

393

394 INSERT arfcsstate FROM TABLE sendstate.

395 IF sy-dbcnt = 0.

396 MESSAGE a502(sy).

397 ENDIF.

398

399 * Referenz-TIDs für Receiver List

400 IF sqreftid[] IS NOT INITIAL.

401 INSERT qreftid FROM TABLE sqreftid.

402 IF sy-dbcnt = 0.

403 MESSAGE a502(sy).

404 ENDIF.

405 ENDIF.

406

407 * Queue-Daten abstellen

408 IF loc_queue[] IS NOT INITIAL.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Dear Vinodvijayankk

What you need to do is to check the joblog of the job 037400/DEV05/WP01 via DB01 or with WRKACTJOB SBS(R3_05) on the green screen. Find the message code SQL0901with the time stamp of your dump and then scroll back to the immediately preceding messages, which should give you more information about what has occurred. If the messages don't help you to solve the problem yourself, then I should open an SAP customer message.

Regards,

Sally Power

Development Support for SAP on IBM i

Former Member
0 Kudos

Dear Sally Power,

We executed the log from DB01 and found below message. Also opened an OSS message

5761SS1 V6R1M0 080215 Display Job Log SYSDEV 07/29/10 12:57:53 Page 3437

Job name . . . . . . . . . . : WP01 User . . . . . . : DEV05 Number . . . . . . . . . . . : 038081

Job description . . . . . . : R3_05 Library . . . . . : R3DEV400

MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST

From procedure . . . . . . : CLEANUP

Statement . . . . . . . . . : 26623

To module . . . . . . . . . : QSQINS

To procedure . . . . . . . : CLEANUP

Statement . . . . . . . . . : 26623

Message . . . . : SQL system error.

Cause . . . . . : An SQL system error has occurred. The current SQL

statement cannot be completed successfully. The error will not prevent

other SQL statements from being processed. Previous messages may indicate

that there is a problem with the SQL statement and SQL did not correctly

diagnose the error. The previous message identifier was ARFCS. Internal

error type -993926207 has occurred. If precompiling, processing will not

continue beyond this statement. Recovery . . . : See the previous

messages to determine if there is a problem with the SQL statement. To view

the messages, use the DSPJOBLOG command if running interactively, or the

WRKJOB command to view the output of a precompile. An application program

receiving this return code may attempt further SQL statements. Correct any

errors and try the request again.

MCH1807 Escape 40 07/29/10 10:43:21.747005 #dbixchn 0068BC QDBFEOD QSYS 069A

Message . . . . : Data space index ARFCSDATA ARFCSDATA cannot be used as

specified.

CPF9999 Escape 40 07/29/10 10:43:21.747096 QMHUNMSG *N QDBFEOD QSYS 069A

Message . . . . : Function check. MCH1807 unmonitored by QDBFEOD at

statement *N, instruction X'069A'.

Cause . . . . . : An escape exception message was sent to a program which

did not monitor for that message. The full name of the program to which the

unmonitored message was sent is QDBFEOD . At the time the message was sent

the program was stopped at higher level language statement number(s) *N. If more than one statement number is shown, the program was a bound program.

Optimization does not allow a single statement number to be determined. If

*N is shown as a value, it means the actual value was not available.

Recovery . . . : See the low level messages previously listed to locate

the cause of the function check. Correct any errors, and then try the

request again.

CPF3698 Information 00 07/29/10 10:43:21.748365 QSCPUTR QSYS 005E QMHAPD QSYS 0500

Message . . . . : Dump output directed to spooled file 8, job

038081/DEV05/WP01 created on system SYSDEV on 07/29/10 10:43:21.

Cause . . . . . : Dump output is being directed to a spooled file.

CPF5257 Escape 70 07/29/10 10:43:21.752358 QDBSIGEX QSYS 0539 QSQRUN3 QSYS *STMT

To module . . . . . . . . . : QSQINS

To procedure . . . . . . . : CLEANUP

Statement . . . . . . . . . : 25565

Message . . . . : Failure for device or member ARFCSDATA file ARFCSDATA in

library R3DEVDATA.

Cause . . . . . : An error occurred during a read or write operation. If

this is a display file, the display may not be usable. Recovery . . . :

See the previously listed messages, correct the errors, and try the request

again. If the problem continues, report the problem (ANZPRB command).

Best Regards,

Answers (0)