on 03-26-2009 9:47 AM
Dear Experts,
We are getting following short dump while execute a customer-developed program, but same program run succesfully in development system,
Dump listed Possible error causes as ;
Possible error causes:
o The maximum size of an SQL statement was exceeded.
o The statement contains too many input variables.
o The input data requires more space than is available.
o ...
What should we do ?
Regards
--
Runtime Errors DBIF_RSQL_INVALID_RSQL
Exception CX_SY_OPEN_SQL_DB
Date and Time 26.03.2009 10:25:38
Short text
Error in module RSQL of the database interface.
What happened?
Error in the ABAP Application Program
The current ABAP program "ZFI_CUST_AGEING_V3" had to be terminated because it
has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
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 exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
in
procedure "GET_OPEN_ITEMS" "(FORM)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
The SQL statement generated from the SAP Open SQL statement violates a
restriction imposed by the underlying database system of the ABAP
system.
Possible error causes:
o The maximum size of an SQL statement was exceeded.
o The statement contains too many input variables.
o The input data requires more space than is available.
o ...
You can generally find details in the system log (SM21) and in the
developer trace of the relevant work process (ST11).
In the case of an error, current restrictions are frequently displayed
in the developer trace.
How to correct the error
The SAP Open SQL statement concerned must be divided into several
smaller units.
If the problem occurred due to the use of an excessively large table
in an IN itab construct, you can use FOR ALL ENTRIES instead.
When you use this addition, the statement is split into smaller units
according to the restrictions of the database system used.
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_RSQL" "CX_SY_OPEN_SQL_DB"
"ZFI_CUST_AGEING_V3" or "ZFI_CASF01_V3"
"GET_OPEN_ITEMS"
The exception must either be prevented, caught within proedure
"GET_OPEN_ITEMS" "(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 700
Application server... "sapapp1"
Network address......
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "8x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "SAPDB"
Database type..... "MSSQL"
Database name..... "KEC"
Database user ID.. "kec"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Mar 3 2008 00:06:14"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 150
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, Windows
NT 6.0"
Memory consumption
Roll.... 16192
EM...... 16759360
Heap.... 0
Page.... 73728
MM Used. 1346384
MM Free. 2840832
User and Transaction
Client.............. 100
User................ "ADMIN"
Language key........ "T"
Transaction......... "SE38 "
Program............. "ZFI_CUST_AGEING_V3"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "ZFI_CUST_AGEING_V3" - in
"GET_OPEN_ITEMS".
The main program was "ZFI_CUST_AGEING_V3 ".
In the source code you have the termination point in line 24
of the (Include) program "ZFI_CASF01_V3".
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "GET_OPEN_ITEMS" "(FORM)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "ZFI_CUST_AGEING_V3 "; its source code begins in
line
12 of the (Include program "ZFI_CASF01_V3 ".
Hi
Check the variant settings for the program causing the error as well.
Regards
Chen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you very much for your recommendations, i forwarded case to Abap Developer,
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Atakan,
It seems to be a memeory issue,your program is consuming a lot of memory,
I would suggest you ask your developer to tune this report and then test it again
it is running fine in development as the dev server doesnt have the production data
Rohit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Consult with Abaper, there is some problem in custom program in Production, that's why is it giving dump. You can check the program via SE38 that is there any syntax error or somehting like that but better option is consult with ABAPER
Regards,
Subhash
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.