cancel
Showing results for 
Search instead for 
Did you mean: 

DBIF_RSQL_INVALID_REQUEST in SAPLSDOC Func Module DOCU_GET

Former Member
0 Kudos

SuSe 10 Oracle 10.2.0.2

shot dump DBIF_RSQL_INVALID_REQUEST when acessing in cluster table DOKTL

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Answer from SAP support:

Dear Customer,

according to information from our Linux experts SLES 10 is currently

in validation.

Plans was that SLES10 for ERP 2005 will be officially released with

SR2 which was planned for october. Do you already have an information,

that this is released ? Where from ?

So, if it would be possible, please, install the system at SLES 9.

Please, also refer to the SAP Note

#958253 SUSE LINUX Enterprise Server 10: Installation notes

hannes_kuehnemund
Active Contributor
0 Kudos

The <a href="http://service.sap.com/pam">Product Availability Matrix</a> may give you an overview which OS/DB/SAP combinations are already certified.

Up to now SAP kernel 6.40 - NW04 - is realeased for SLES10. SAP kernel 7.00 - NW04s - (which you are using) on top of SLES10 is not certified yet, but it is already in the validation, as the SAP support already stated.

Former Member
0 Kudos

Remove from /etc/hosts:

localhost 127.0.0.2

Thats all

Regards

Marcin

Former Member
0 Kudos

also DBIF_RSQL_INVALID_REQUEST shot dump when show contents BSEG

>>>> SELECT * FROM BSEG "client speci

550 APPENDING TABLE IBSEG

551 UP TO RSEUMOD-TBMAXSEL ROWS BYPASSI

552 WHERE BUKRS IN I1

553 AND BELNR IN I2

554 AND GJAHR IN I3

555 AND BUZEI IN I4.

Former Member
0 Kudos

Hello,

Sorry, I wasexpecting to see some other information on the trace files.

The only think I can recommend you is to open a message in SAP.

Former Member
0 Kudos

ST05 SQL trace:

12 DOKIL REOPEN 0 SELECT WHERE "ID" = 'DT' AND "OBJECT" = 'TX_SPAM_APPLICATION_DIALOG_1' AND "LANGU" = 'E'

453 DOKIL FETCH 1 1403

10 SNAPT REOPEN 0 SELECT WHERE LANGU = 'E' AND ERRID = 'INCL_' AND TTYPE = 'K' ORDER BY SEQNO

359 SNAPT FETCH 0 1403

4 SNAPT REOPEN 0 SELECT WHERE LANGU = 'E' AND ERRID = 'INCL_' AND TTYPE = 'K' ORDER BY SEQNO

78 SNAPT FETCH 0 1403

3 SNAPT REOPEN 0 SELECT WHERE LANGU = 'D' AND ERRID = 'INCL_' AND TTYPE = 'K' ORDER BY SEQNO

70 SNAPT FETCH 0 1403

365 SNAP REEXEC 1 0 INSERT VALUES ( 20061114 , 182358 , 'sapserber11_D70_00' , 'MATVEEV' , '000' , 2 , '000' , 'C' , 'FC025DBIF_RSQL_INVALID_REQUESTAP008SAPLSDOCAI008LSDOCU09AL003249CM039//bas/700_REL/s

Former Member
0 Kudos

Hello,

That error is too generic.

On the developer trace you can find more information.

Like the query that was being executed and the full text of the error.

With that information it is possible to provide some help, otherwise it is not possible, only guess.

Former Member
0 Kudos

This dump occurs during start of the following transactions:

SPAM, SMLT, RCPINST....., e.c.

Runtime Errors DBIF_RSQL_INVALID_REQUEST

Date and Time 14.11.2006 13:54:55

Short text

Invalid request.

What happened?

The current ABAP/4 program had to be terminated because the

ABAP/4 processor detected an internal system error.

Error analysis

An invalid request was made to the database interface

when accessing table "DOKTL ".

How to correct the error

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

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

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,

please use the following search criteria:

"SAPLSDOC" "DBIF_RSQL_INVALID_REQUEST"

If you cannot solve the problem yourself, please send the

following documents to SAP:

1. A hard copy print describing the problem.

To obtain this, select the "Print" function on the current screen.

2. A suitable hardcopy prinout of the system log.

To obtain this, call the system log with Transaction SM21

and select the "Print" function to print out the relevant

part.

3. If the programs are your own programs or modified SAP programs,

supply the source code.

To do this, you can either use the "PRINT" command in the editor or

print the programs using the report RSINCL00.

4. Details regarding the conditions under which the error occurred

or which actions and input led to the error.

System environment

SAP-Release 700

Application server... "sapserver11"

Network address...... "127.0.0.2"

Operating system..... "Linux"

Release.............. "2.6.16.21-0.8-defaul"

Hardware type........ "i686"

Character length.... 16 Bits

Pointer length....... 32 Bits

Work process number.. 0

Shortdump setting.... "full"

Database server... "sapserver11"

Database type..... "ORACLE"

Database name..... "D70"

Database user ID.. "SAPSR3"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Aug 29 2006 07:06:26"

create on........ "Linux GNU SLES-9 i686 cc3.3.3"

Database version. "OCI_102 (10.2.0.2.0) "

Patch level. 75

Patch text.. " "

Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."

SAP database version. 700

Operating system..... "Linux 2.6"

Memory consumption

Roll.... 8176

EM...... 2090448

Heap.... 0

Page.... 0

MM Used. 1087224

MM Free. 1001704

and Transaction

Client.............. 000

User................ "MATVEEV"

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

Transaction......... "SESSION_MANAGER "

Program............. "SAPLSDOC"

Screen.............. "SAPMSYST 0020"

Screen line......... 87

rmation on where terminated

Termination occurred in the ABAP program "SAPLSDOC" - in "DOCU_GET".

The main program was "SAPMSYST ".

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

of the (Include) program "LSDOCU09".

ce Code Extract

SourceCde

19 head-tdobject = 'DOKU'.

20 ENDCASE.

21 HEAD-TDNAME = DOKHL-OBJECT.

22 HEAD-TDID = DOKHL-ID.

23 HEAD-TDSPRAS = DOKHL-LANGU.

24 * HEAD-TDFORM = DOKHL-DOKFORM. "geä. hb 30/06/93

25 IF DOKHL-DOKFORM EQ 'HELP'. "geä. hb 30/06/93

26 MOVE 'S_DOCU_SHOW' TO HEAD-TDFORM. "geä. hb 30/06/93

27 ELSE. "geä. hb 30/06/93

28 HEAD-TDFORM = DOKHL-DOKFORM. "geä. hb 30/06/93

29 ENDIF. "geä. hb 30/06/93

30 * HEAD-TDSTYLE = DOKHL-DOKSTYLE. "geä. hb 30/06/93

31 IF DOKHL-DOKSTYLE EQ 'DOKU'. "geä. hb 30/06/93

32 MOVE 'S_DOCUS1' TO HEAD-TDSTYLE. "geä. hb 30/06/93

33 ELSE. "geä. hb 30/06/93

34 HEAD-TDSTYLE = DOKHL-DOKSTYLE. "geä. hb 30/06/93

35 ENDIF. "geä. hb 30/06/93

36 HEAD-TDVERSION = DOKHL-DOKVERSION.

37 HEAD-TDFUSER = DOKHL-DOKFUSER.

38 HEAD-TDFRELES = DOKHL-DOKFRELES.

39 HEAD-TDFDATE = DOKHL-DOKFDATE.

40 HEAD-TDFTIME = DOKHL-DOKFTIME.

41 HEAD-TDLUSER = DOKHL-DOKLUSER.

42 HEAD-TDLRELES = DOKHL-DOKLRELES.

43 HEAD-TDLDATE = DOKHL-DOKLDATE.

44 HEAD-TDLTIME = DOKHL-DOKLTIME.

45 HEAD-TDLINESIZE = '072'.

46

47 DOKSTATE = DOKHL-DOKSTATE.

48

>> SELECT *

50 FROM DOKTL

51 INTO TABLE IDOKTL

52 WHERE LANGU = LANGU

53 AND ID = ID

54 AND OBJECT = OBJECT

55 AND TYP = TYP

56 AND DOKVERSION = DOKIL-VERSION

57 ORDER BY PRIMARY KEY.

58

59 CLEAR IDOKTL.

60 READ TABLE IDOKTL INDEX 1.

61

62 IF IDOKTL-DOKTEXT(5) NE '{ tf'.

63 LOOP AT IDOKTL.

64 PERFORM LINE_APPEND.

65 ENDLOOP.

66 ELSE.

67 LOOP AT IDOKTL.

68 MOVE IDOKTL-DOKFORMAT TO ILINE-TDFORMAT.

Former Member
0 Kudos

Hi Dmitry,

That is the short dump.

For this specific error is not good.

You need to go to the developer traces ( dev_w* )

Do the following

1) start transaction SM21

2) search for the error in this transaction ( you have the day and time )

3) the 3rd column is telling you the WP where the error happened. For example ( the format is not very good )

Time Ty. Nr Cl. User Tcod MNo Text

10:02:16 DIA <b><u><i>00</i></u></b> 800 Fidel AB0 Run-time error ...

4) now, if you have not restarted SAP you can go to SM50, look for the WP with the same number and check the developer trace ( button "display file" )

This can be a very biggggg file. Please, do not paste it here.

Look on the file for the day and time you got the error:

Date and Time 14.11.2006 13:54:55

and there you can find the information I asked before.

Perhaps it is better you open a ticket for it.

Former Member
0 Kudos

In trace dev_w2

ABAP Program SAPLSDOC .

Source LSDOCU09 Line 249.

Error Code DBIF_RSQL_INVALID_REQUEST.

Module $Id: //bas/700_REL/src/krn/runt/absapsql.c#6 $ SAP.

Former Member
0 Kudos

Function HandleRsqlErrors Line 764.

Former Member
0 Kudos

During installation on SuSe10 occurred error when control.xml during checs swap. I've solve this edit control.xml and disable function this.performCheks = function {} also I've edit oraparam.ini file for add SuSe10 for susses check. Have not more errors.