DBIF_RSQL_SQL_ERROR - During Login Into the system

[Former Member]

Hi,

We have installed WebAS 640 (Unicode) on ISeries with BW 3.5. '

The latest Kernel and patches have also been applied. No data has been loaded in this system yet and it is freah installation. Though not regularly but at times whenever a user tries to log into the system , the system generated a short dump. This also occurs when we try to refresh a screen or at any time . the dump error is :

"

Runtime Error DBIF_RSQL_SQL_ERROR

Except. CX_SY_OPEN_SQL_DB

Date and Time 2006-11-13 22:06:39

Information on where terminated

The termination occurred in the ABAP program "SAPLSDOC" in "DOCU_READ".

The main program was "RSPARAGENJOB ".

The termination occurred in line 82 of the source code of the (Include)

program "LSDOCU01"

of the source code of program "LSDOCU01" (when calling the editor 820).

Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in

the

procedure "DOCU_READ" "(FUNCTION)" but was not handled locally, not declared in

the

RAISING clause of the procedure.

The procedure is in the program "SAPLSDOC ". Its source code starts in line 5

of the (Include) program "LSDOC$01 ".

Has any one else also come across this errror and what is the rectification for it.

Thanks

Sachin Rustagi

[benito_lupercio]

HI Sachin,

I get the same dump that you described in this message, Did you get the solution to this dump?

Regards,

Benito

[Former Member]

Hi,

this is the latest entry , immediately after getting the short dump

Message ID . . . . . . : CPF5009

Date sent . . . . . . : 13.11.06 Time sent . . . . . . : 22:14:30

Message . . . . : Duplicate record key in member ALCLASTOOL.

Cause . . . . . : The output or update operation to member number 1 record

number 0 format ALCLASTOOL, for member ALCLASTOOL file ALCLASTOOL in library

R3Q27DATA, failed. Member number 1 record number 3015 format ALCLASTOOL has

the same record key as member number 1 record number 0 format ALCLASTOOL.

If the record number is zero, the duplicate record key occurred on an output

operation.

Recovery . . . : Change either record key so that the keys are unique.

Then try your request again.

Regards

Sachin

[Former Member]

Hi,

... in the correct WP as well ? Did you check the WP number ?

Regards

Volker

[Former Member]

Hi,

The job log is as follows

DOKCLUIG in R3Q2742060 type *SQLPKG not found.

Duplicate record key in member ALGRPCUSGE.

Duplicate key on access path.

Then as suggested, I did F1

Message ID . . . . . . : CPF5034

Date sent . . . . . . : 13.11.06 Time sent . . . . . . : 22:14:30

Message . . . . : Duplicate key on access path.

Cause . . . . . : An output or update operation on record number 0 record

format FORMAT0001 member number 1 failed because of a duplicate key in a

unique keyed member that is based on member ALCLASTOOL file ALCLASTOOL in

library R3Q27DATA, or in a based-on member of ALCLASTOOL. The failure could

also have been caused by an output or update operation done to another file

by a trigger program associated with file ALCLASTOOL in library R3Q27DATA.

Recovery . . . : See previously listed message CPF5009 to identify the file

and record with the duplicate key and change the key value so that it is

unique. Note that the file could be a file operated on by a trigger program.

Then try your request again.

Regards

Sachin

[Former Member]

Hi,

even when you cannot believe:

Duplicate keys are "typically" normal.

The question would be:

What is the error message in "more or less" the same second in the joblog? I would imagine to see other stuff ...

Try to logon again now and "hunt" for this entry in the joblog ...

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

[Former Member]

Hi,

Yes you are right. The details shows:

How to correct the error

Database error text........: "DOKCLUIG in R3Q2742060 type * MSGID=

Job=351455/Q2727/WP00"

Internal call code.........: "[RSQL/FTCH/DOKTL ]"

Please check the entries in the system log (Transaction SM21).

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

-

---

"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC

"SAPLSDOC" or "LSDOCU01"

"DOCU_READ"

-

---

Do you also remember the solution to this issue ?

Thanks

Sachin Rustagi

[Former Member]

Hi,

what does the following show you ?

wrkjob 351455/Q2727/WP00

option 10 and then hunting for the error ... if possible with the MSGID (F1)

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

[Former Member]

Hi Sachin,

in the past I had the same problem once. You should have a look at the ABAP part of the short dump and should let us know it. I do have in mind, that it is an SQL to the docu-table DOKLU (?). Then you should have a look in the corresponding Work process for the SQL message. I would expect, that you see SQL0901 or 501 there ...

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de