DBIF_RSQL_INVALID_REQUEST

[Former Member]

Hi Gurus,

In our SAP system we are getting DBIF_RSQL_INVALID_REQUEST dump error when the functional team is accessing some sales and material related transactions. I dont have any idea on that and i have seen the trace from the work directory which as of below

A ABAP Program SAPLSCD0 .

A Source LSCD0F03 Line 175.

A Error Code DBIF_RSQL_INVALID_REQUEST.

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

A Function HandleRsqlErrors Line 786.

A ** RABAX: level LEV_RX_STDERR completed.

A ** RABAX: level LEV_RX_RFC_ERROR entered.

A ** RABAX: level LEV_RX_RFC_ERROR completed.

A ** RABAX: level LEV_RX_RFC_CLOSE entered.

A ** RABAX: level LEV_RX_RFC_CLOSE completed.

A ** RABAX: level LEV_RX_IMC_ERROR entered.

A ** RABAX: level LEV_RX_IMC_ERROR completed.

A ** RABAX: level LEV_RX_DATASET_CLOSE entered.

A ** RABAX: level LEV_RX_DATASET_CLOSE completed.

A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.

A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.

A ** RABAX: level LEV_RX_ERROR_SAVE entered.

A ** RABAX: level LEV_RX_ERROR_SAVE completed.

A ** RABAX: level LEV_RX_ERROR_TPDA entered.

A ** RABAX: level LEV_RX_ERROR_TPDA completed.

A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.

A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.

A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.

A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.

A ** RABAX: level LEV_RX_END entered.

A ** RABAX: level LEV_RX_END completed.

A ** RABAX: end no http/smtp

A ** RABAX: end RX_GOTO_RABAX

A Invalid request..

Please suggest how to rectify the dump

Your suggestions will be highly appreciated

Will reward points

thanks,

KIRAN

[Former Member]

Hello Kiran,

Did you solve the problem?

I'm facing the exact same problem.

I have a system with kernel patch level 83.

Seems like the problem is related to clustered tables.

Anyone?

Regards,

Leif

[Former Member]

Hi,

Kiran, also please send the error log you find in ST22 for the particular error.

Regards,

Suhas

[Former Member]

Hi Suhas,

Iam sending the dump error.Plz have a look in to it

Runtime Errors DBIF_RSQL_INVALID_REQUEST

Short text

Invalid request.

What happened?

The current ABAP/4 program terminated due to

an internal error in the database interface.

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.

Error analysis

An invalid request was made to the SAP database interface in a statement

in which the table "KONV " was accessed.

How to correct the error

Start the work process involved and repeat the action that lead to the

error.

If the error position is in a program that you can change, you can try

to create preliminary solution: Reformulate the database command by

varying the properties such as individual record access instead of

input/output via internal tables, the structure of the selection

conditions (WHERE clause), nested SELECT loops instead of FOR ALL

ENTRIES and other such variations.

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

Check the entries in the developer trace of the work process involved

(transaction ST11).

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_INVALID_REQUEST" " "

"SAPLV61A" or "LV61AA11"

"KONV_EINLESEN"

System environment

SAP-Release 700

Application server... "os1gvzg"

Network address...... "10.10.30.24"

Operating system..... "Windows NT"

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

Hardware type........ "2x Intel 80686"

Character length.... 16 Bits

Pointer length....... 32 Bits

Work process number.. 1

Shortdump setting.... "full"

Database server... "OS1GVZG"

Database type..... "MSSQL"

Database name..... "RT1"

Database user ID.. "rt1"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Aug 29 2006 00:18:21"

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

Database version. "SQL_Server_8.00 "

Patch level. 75

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"

Memory consumption

Roll.... 8176

EM...... 8361792

Heap.... 0

Page.... 32768

MM Used. 3704704

MM Free. 474448

User and Transaction

Client.............. 100

User................ "MUBEENM"

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

Transaction......... "VA02 "

Program............. "SAPLV61A"

Screen.............. "SAPMV45A 0102"

Screen line......... 27

Information on where terminated

Termination occurred in the ABAP program "SAPLV61A" - in "KONV_EINLESEN".

The main program was "SAPMV45A ".

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

of the (Include) program "LV61AA11".

Source Code Extract

Line SourceCde

52 ix_tkomv_v = sy-tabix. "remember the index

53 if sy-subrc eq 0.

54 if generell_lesen ne 'X'.

55 exit.

56 endif.

57 * there are already fitting entries in TKOMV,

58 * but a 'general read' is requested

59 sort_tkomv = yes. "sort is necessary

60 endif.

61 endif.

62

63 generell_lesen = space.

64

65 * structured conditions (KDUPL set) like cumulation

66 refresh xkumko.

67

68 * determine the right index of TKOMV if necessary

69 if ix_tkomv_v is initial.

70 read table tkomv with key knumv = komk-knumv

71 binary search

72 transporting no fields.

73 ix_tkomv_v = sy-tabix. "index always not initial now

74 if sy-subrc eq 0.

75 * there are already fitting entries

76 sort_tkomv = yes. "sort is necessary

77 endif.

78 endif.

79

80 * get pricing result from database table

81 ENHANCEMENT-SECTION KONV_EINLESEN_02 SPOTS ES_SAPLV61A.

>>>>> select * into table hkomv

83 from konv

84 where knumv = komk-knumv

85 order by primary key.

86 END-ENHANCEMENT-SECTION.

87 * internal optimization: for the db system no sort of the result

88 * should be necessary here, because the KONV is a cluster table

89 * (records are already in the right order)

90

91 lines_of_hkomv = sy-dbcnt. "remember number of hits

92

93 * BAdI for supplementation of KONV data

94 if gr_konv_exit is initial and gv_konv_impl_exists ne '-'.

95 call function 'SXC_EXIT_CHECK_ACTIVE'

96 exporting

97 exit_name = 'SD_KONV_SELECT'

98 exceptions

99 not_active = 1

100 others = 2.

101 if sy-subrc ne 0.

thanks N regards,

KIRAN

[Former Member]

Hi,

current kernel patch level of your system - 75

upgrade kernel patch of your sap system.

regards,

kaushal

[Former Member]

Hi Kiran,

I agree with Antonio. Check your kernel patch level update with latest patch.

Regards,

Nagendra.

[antonio_voce]

Hi ,

try first to install the latest kernel patch !!!

Tell me the result.

Antonio