Question:
Hi Basis Girls/Guys,
this posting is coming from the Business Warehouse forum; as I think you could be from some help, I decided to shadow move it to your forum.
Could somebody try to explain a little bit those concepts to JuergenL ?
Thanks in advance,
Ch
_________________
_
There are only 10 types of people in the world :
those who understand binary and those who don't.
Answer:
Hello Juergen,
a tablespace becomes critical if the max. free space (DB2->freespace statistics) is smaler than the largest next extent size of tables in that tablespace. I'm not sure if I wrote it clearly or not.
But you can check the log of your short dump and you can find out the reason.
The % of used space in a tablesapce is only an information and you get warning from sapdba -check if this value is > 90%, but it dosnt mean that your tablespace is critical. This % value for warning can be changed in DB17.
I hope I could help, Vica
Answer:
Well, follwing the post of vica, nothing should happen (all tablespaces are uncritical...)
But I got a short dump everytime...
Here's the text of it:
ABAP runtime errors DBIF_RSQL_INVALID_RSQL
Occurred on 10.04.2003 at 13:41:16
------------------------------------------------------------------------------------------
>> Short dump has not been completely stored. It is too big.
------------------------------------------------------------------------------------------
RSQL error 13 when accessing table "FPLA ".
--------------
What happened?
--------------
The current ABAP/4 program "RMCVNEAV2 " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
----------------
What can you do?
----------------
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
--------------
Error analysis
--------------
The SQL statement generated from SAP Open SQL violates a
restriction imposed by the database system used in R/3.
-
For details, refer to either the system log or the developer trace.
Possible reasons for error:
o Maximum size of an SQL statement exceeded.
o The statement contains too many input variables.
o The input data requires more space than is available.
o ...
You can usually find details in the system log (SM21) and in
the developer trace of the relevant work process (ST11).
In the event of an error, the developer trace often gives the
current restrictions.
------------------------
How to correct the error
------------------------
The SAP Open SQL statement concerned must be divided into several
smaller units.
If the problem occurred because an excessively large table was used
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 occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
----------------------------------------------------------------
"DBIF_RSQL_INVALID_RSQL"
"RMCVNEAV2 " or "RMCVNEAV2 "
"READ_PACKAGE_OF_DOCUMENTS"
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.............. "46C"
Application server....... "*******"
Network address.......... "xxx.xxx.xxx.xxx"
Operating system......... "HP-UX"
Release.................. "B.11.00"
Hardware type............ "9000/800"
Database server.......... "*******"
Database type............ "ORACLE"
Database name............ "CW1"
Database owner........... "SAPR3"
Character set............ "en_US.iso88591"
SAP kernel............... "46D"
Created on............... "Nov 4 2001 20:33:01"
Created in............... "HP-UX B.11.00 U 9000/800"
Database version......... "OCI_805_64 "
Patch level.............. "880"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.0.5.*.*, ORACLE 8.0.6.*.*"
SAP database version..... "46D"
Operating system......... "HP-UX B.10, HP-UX B.11, , System build information:,
-------------------------------------, LCHN : 431080"
--------------------
User, transaction...
--------------------
Client.............. 010
User................ "WILIMBACH"
Language key........ "E"
Transaction......... "OLI7BW "
Program............. "RMCVNEAV2 "
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
-----------------------------------------
Information on where termination occurred
-----------------------------------------
The termination occurred in the ABAP/4 program "RMCVNEAV2 " in
"READ_PACKAGE_OF_DOCUMENTS".
The main program was "RMCVNEAV2 ".
The termination occurred in line 339
of the source code of program "RMCVNEAV2 " (when calling the editor 3390).
-------------------
Source code extract
-------------------
003090 SELECT * INTO TABLE gt_vbpan
003100 FROM vbpa
003110 WHERE vbeln IN l_vbeln
003120 ORDER BY PRIMARY KEY.
003130
003140 * read VBEP
003150 SELECT * INTO TABLE gt_vbepn
003160 FROM vbep
003170 WHERE vbeln IN l_vbeln
003180 ORDER BY PRIMARY KEY.
003190
003200 * read VBFA
003210 SELECT * INTO TABLE gt_vbfan
003220 FROM vbfa
003230 WHERE vbelv IN l_vbeln
003240 ORDER BY PRIMARY KEY.
003250
003260 * read KONV
003270 IF cnt_knumv > 0.
003280 SELECT * INTO TABLE gt_konvn
003290 FROM konv
003300 WHERE knumv IN l_knumv
003310 ORDER BY PRIMARY KEY.
003320 ENDIF.
003330
003340 * read FPLA / FPLT
003350 IF cnt_fplnr > 0.
003360 SELECT * INTO TABLE gt_fplan
003370 FROM fpla
003380 WHERE fplnr IN l_fplnr
-----> ORDER BY PRIMARY KEY.
003400 SELECT * INTO TABLE gt_fpltn
003410 FROM fplt
003420 WHERE fplnr IN l_fplnr
003430 ORDER BY PRIMARY KEY.
003440 ENDIF.
003450
003460 ENDFORM. "read_block_of_documents
003470
003480 *&--------------------------------------------------------------------*
003490 *& Form process_package
003500 *&--------------------------------------------------------------------*
003510 * text
003520 *---------------------------------------------------------------------*
003530 FORM process_package.
003540
003550 IF cnt_package > 0.
003560 CALL FUNCTION 'MCV_SALES_DOCUMENT_UPDATE'
003570 EXPORTING
003580 i_flg_options = flg_options
(This is not the end of the short dump...)
_________________
Juergen Limbach
Answer:
I had the same dump few days ago in my system.
The problem is that the SQL sentence is too long.
SELECT * INTO TABLE gt_fplan
003370 FROM fpla
003380 WHERE fplnr IN l_fplnr
-----> ORDER BY PRIMARY KEY.
The sentence passed to the databse is translated into sql native. There are too many parameters in l_fplnr and the translated sentence is too long.
I don't know if it is clear but you have two options :
Change the abap code ( as it is an standard report i woudn't recomend it unless you have SAP instructions to do it.
Select less options for fplnr.
This dump is not related to the tablespace free space.
Maybe if you look at OSS you will find anmy note with this problem
Answer:
Hi Juergen,
nothing to do with y problem but
anyway I believe that your SAP Kernel is too old .... 880
Regards
Boss
Answer:
Hi, adela.
Thanks, will try this...
_________________
Juergen Limbach
Answer:
First of all the error in my Business Warehouse was caused by to less tablespace, we enhanced it and now it works.
The error within R/3 is caused by an error in RMCVNEAV2, the SQL-Statement is to long for ORACLE...
Hi, regarding oss note 565035, we have to change the coding.
There's a correction guide in the marketplace...
FORM READ_PACKAGE_OF_DOCUMENTS
SELECT * INTO TABLE gt_konvn
FROM konv
WHERE knumv IN l_knumv
ORDER BY PRIMARY KEY.
ENDIF.
* read FPLA / FPLT
IF cnt_fplnr > 0.
*************************
******Delete-Block********
*************************
* SELECT * INTO TABLE gt_fplan
* FROM fpla
* WHERE fplnr IN l_fplnr
* ORDER BY PRIMARY KEY.
* SELECT * INTO TABLE gt_fpltn
* FROM fplt
* WHERE fplnr IN l_fplnr
* ORDER BY PRIMARY KEY.
*************************
*******Insert-Block********
*************************
SELECT * FROM fpla INTO TABLE gt_fplan
FOR ALL ENTRIES IN l_fplnr
WHERE fplnr = l_fplnr-low.
SORT gt_fplan.
SELECT * FROM fplt INTO TABLE gt_fpltn
FOR ALL ENTRIES IN l_fplnr
WHERE fplnr = l_fplnr-low.
SORT gt_fpltn.
Another possibilty is do install support package SAPKH46C39 (we are on 36 I think)
Regards. Jürgen
_________________
Juergen Limbach
Answer:
I had a similar problem a year ago. I found out that I was looking for problems on the BW side, but tablepsace problem was on the R/3 side.
Snowy
_________________
SapFans Moderator
NetWeaver ‘04–SAP Web AS for ORACLE certified
Search: /forums/search.php
SAP Notes: http://service.sap.com/notes
SAP Help: http://help.sap.com
Basic Rules: /forums/viewtopic.php?t=222759
Answer:
Hello Juergen,
a tablespace becomes critical if the max. free space (DB2->freespace statistics) is smaler than the largest next extent size of tables in that tablespace. I'm not sure if I wrote it clearly or not.
But you can check the log of your short dump and you can find out the reason.
The % of used space in a tablesapce is only an information and you get warning from sapdba -check if this value is > 90%, but it dosnt mean that your tablespace is critical. This % value for warning can be changed in DB17.
I hope I could help, Vica
you are right except that its the contiguous max free space
_________________
The heart has its reasons which reason knows not of
PASCAL
Answer:
hi ,
my opnion is defarent then other i think may be your kernal is old or your data is currpted just go to se11 and try to view same table if u get shotdump please post message back .
svhanspal