RV60SBAT DBIF_RSQL_INVALID_RSQL - ST22 dump using VF06

Hello
We are trying in test system to run a test in VF06 selecting approx
13000 DMR. When we try to run the program, we recieve a dump . Is there a limitation for number of selected DMR, and if so what is the max amount?
Kind regards

Check these threads
[Error DBIF_RSQL_INVALID_RSQL in R/3|Error DBIF_RSQL_INVALID_RSQL in R/3]
[Reg Blocked Export Documents Runtime Error |Re: Reg Blocked Export Documents Runtime Error]
thanks
G. Lakshmipathi

Similar Messages

ST22 Dumps in ECC pushed to Slution Manager

Hi,
We have a ECC6.0 and Solution Manager in our system.
I wanted to configure that if a ST22 Dump occurs in ECC 6.0, the ST22 dump should be pused to the Solution Manager and i should be able to view it through the Solution Manager.
Please let me know whether it is possible or anyone has done it

Dear andreas,
You will not be able to see ST22 dumps in solution Manager. You can see dumps in Solution Manager Diagonstics.. for that you need to configure SMD agents on satelite system and SMD on solution Manager...
also if you just want to get alerts .. you can configure.. CCMS RZ20 and use solution manager as central system..
search in help.sap.com for more info..
Let me know if you require any furher info..
Regards,
akhilesh

How can I read st22 dump in ABAP

hello,
i would like to know if st22 dump info could be read via FMs or Classes. I found a class CL_DUMP_INFO_MANAGER, btu well could not find documentation on it usage. Will be glad if someone can tell me how to retrieve St22 info.
- Harish

Hi,
Try the fun module
RS_ST22_GET_DUMPS
to get the dump results.
other related fun modules are:
RS_ST22_GET_DUMPS_CATEGORIES
RS_ST22_GET_DUMP_CATEGORY
RS_ST22_GET_DUMP_CATEGORY_TEXT
reward if useful
regards,
Anji

ST22 Dump - Need to find associated proxy XML

Hi,
I need to find the inbound proxy call (xml message), which has caused the ST22 dump. Can any of you tell me whether the transaction id or any other values from ST22 can be used to track the message unique?
Thanks,

HI Joe,
for any proxy call either inbound or outbound, you will find all the processed the messages in the SXMB_MONI transaction.
the messages which are processed successfully has the status and processed successfully but if there is any problem during the processing of message because of program dump then this message remains in the green flagged status. hence try to find out the green flagged status and check the error log for the same. you will find out the exact error message which is appearing in ST22.
you can also try to check the queue using smq2 transaction , if there is any dump while processing the message the followeing messages are got stuck as long as you are not deleting the first messages. from there also you can see the erroneous XML data.

Error while taking dump using datapump

getting following error -
Export: Release 10.2.0.1.0 - Production on Friday, 15 September, 2006 10:31:41
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Starting "XX"."SYS_EXPORT_SCHEMA_02": XX/********@XXX directory=dpdump dumpfile=XXX150906.dmp logfile=XXX150906.log
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.GET_TABLE_DATA_OBJECTS while calling DBMS_METADATA.FETCH_XML_CLOB []
ORA-31642: the following SQL statement fails:
BEGIN "DMSYS"."DBMS_DM_MODEL_EXP".SCHEMA_CALLOUT(:1,0,0,'10.02.00.01.00'); END;
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_METADATA", line 907
ORA-06550: line 1, column 7:
PLS-00201: identifier 'DMSYS.DBMS_DM_MODEL_EXP' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 6235
----- PL/SQL Call Stack -----
object line object
handle number name
2A68E610 14916 package body SYS.KUPW$WORKER
2A68E610 6300 package body SYS.KUPW$WORKER
2A68E610 9120 package body SYS.KUPW$WORKER
2A68E610 1880 package body SYS.KUPW$WORKER
2A68E610 6861 package body SYS.KUPW$WORKER
2A68E610 1262 package body SYS.KUPW$WORKER
255541A8 2 anonymous block
Job "XX"."SYS_EXPORT_SCHEMA_02" stopped due to fatal error at 10:33:12
Action required is contact customer support. And on metalink found a link that states it a bug in 10g release 1 that was suppose to be fixed in 10g release 1 version 4.
some of the default schemas were purposely dropped from the database. The only default schema available now are -
DBSNMP, DIP, OUTLN, PUBLIC, SCOTT, SYS, SYSMAN, SYSTEM, TSMSYS.
DIP, OUTLN, TSMSYS were created again.
Could this be a cause of problem??
Thanks in adv.

Hi,
Below is the DDL taken from different database. Will this be enough ? One more thing please, what shall be the password should it be DMSYS.....since this will not be used by me but system.
CREATE USER "DMSYS" PROFILE "DEFAULT" IDENTIFIED BY "*******" PASSWORD EXPIRE DEFAULT TABLESPACE "SYSAUX" TEMPORARY TABLESPACE "TEMP" QUOTA 204800 K ON "SYSAUX" ACCOUNT LOCK
GRANT ALTER SESSION TO "DMSYS"
GRANT ALTER SYSTEM TO "DMSYS"
GRANT CREATE JOB TO "DMSYS"
GRANT CREATE LIBRARY TO "DMSYS"
GRANT CREATE PROCEDURE TO "DMSYS"
GRANT CREATE PUBLIC SYNONYM TO "DMSYS"
GRANT CREATE SEQUENCE TO "DMSYS"
GRANT CREATE SESSION TO "DMSYS"
GRANT CREATE SYNONYM TO "DMSYS"
GRANT CREATE TABLE TO "DMSYS"
GRANT CREATE TRIGGER TO "DMSYS"
GRANT CREATE TYPE TO "DMSYS"
GRANT CREATE VIEW TO "DMSYS"
GRANT DROP PUBLIC SYNONYM TO "DMSYS"
GRANT QUERY REWRITE TO "DMSYS"
GRANT SELECT ON "SYS"."DBA_JOBS_RUNNING" TO "DMSYS"
GRANT SELECT ON "SYS"."DBA_REGISTRY" TO "DMSYS"
GRANT SELECT ON "SYS"."DBA_SYS_PRIVS" TO "DMSYS"
GRANT SELECT ON "SYS"."DBA_TAB_PRIVS" TO "DMSYS"
GRANT SELECT ON "SYS"."DBA_TEMP_FILES" TO "DMSYS"
GRANT EXECUTE ON "SYS"."DBMS_LOCK" TO "DMSYS"
GRANT EXECUTE ON "SYS"."DBMS_REGISTRY" TO "DMSYS"
GRANT EXECUTE ON "SYS"."DBMS_SYSTEM" TO "DMSYS"
GRANT EXECUTE ON "SYS"."DBMS_SYS_ERROR" TO "DMSYS"
GRANT DELETE ON "SYS"."EXPDEPACT$" TO "DMSYS"
GRANT INSERT ON "SYS"."EXPDEPACT$" TO "DMSYS"
GRANT SELECT ON "SYS"."EXPDEPACT$" TO "DMSYS"
GRANT UPDATE ON "SYS"."EXPDEPACT$" TO "DMSYS"
GRANT SELECT ON "SYS"."V_$PARAMETER" TO "DMSYS"
GRANT SELECT ON "SYS"."V_$SESSION" TO "DMSYS"
The other database has the DMSYS and the status is EXPIRED & LOCKED but I'm still able to take the dump using datapump??

COMPUTE_BCD_OVERFLOW ST22 dump

Dear All,
When I run the ECC_PRD_BITX_D_FDM_INVOICE, which is a standard SAP(program FDM_INVOICE_MEMORY).
I get COMPUTE_BCD_OVERFLOW ST22 dump.
This short dump occured due to CX_SY_ARITHMETIC_OVERFLOW i.e. Target field size was not able to store the value of source field at the folowing code location while assigning value to l_days_of_delay.
   90       ENDIF.
   91
   92 *     set actual discount and delay in payment
>>>>>       l_days_of_delay = sy-datlo
   94                       - <open_item>-zfbdt
   95                       - <open_item>-zbd1t.
Are there SAP Notes that can solve this problem?
My system details
S/w Component : SAP_APPL
Release : 604
Highest Support : SAPKH60405
sapnote_0000620532, sapnote_0001239612 , sapnote_0001323002 do not work in my system
Regards,
Jack Silverz

hi jack,
just check these avalilabe notes for your dump.
620532
1323002
1239612
hope this will help u.
thanks

Collect Thread Dump using Script and direct to separate log file

Dear Legends,
I request you to provide me some useful guide lines to collect Thread Dump using script in linux and redirect the output to a separate log file, not the STDOUT file. If it is redirecting to STDOUT then how to extract only the thread stack to a separate log file.
i used
ps -ef | grep java
kill -3 <pid> >> ss1_td.log
but it is not providing the thread stack to the log file.
Anykind of help would be appreciated much.
Regards,
Karthik

Hi Ram,
Really a great and useful script for me at the right time. It solved my requirement and i made some changes to my requirement and the script it working fine to collect the thread dump and even i have checked the thread dump with SAMURAI works fine.
Helpful site also refer sites like these which contains more valuable things for weblogic. We will meet in the forums again.
Note: also please update several links available in the site like UNIX scripts, WLST, Python etc.
Regards,
Karthik

Error while taking GC heap Dump using Microsoft PerfView

Hello,
When I try to take heap dump for an application process using Microsoft
PerfView , error observed
and the error log given below. Can you please let me know the root cause for his issue ?
Steps followed
From the PerfView UI, choose “Take Heap Snapshot,” located on the Memory menu.
And choose the process to capture
Click the “Dump GC Heap” button or simply double click on the process name.
Error Log
Completed: Dumping GC Heap to C:\Install\TM\PerfView\TestProcess.gcDump (Elapsed Time: 1.156 sec)
Error: HeapDump failed with exit code 1
Directory TestProcess.gcdump does not exist
Started: Dumping GC Heap to C:\Install\TM\PerfView\TestProcess.1.gcDump
Collecting a GC Heap SnapShot for process 1704
[Taking heap snapshot of process '1704' ID 1704 to TestProcess.1.gcdump. This can take 10s of seconds to minutes.]
During the dump the process will be frozen. If the dump is aborted, the process being dumped will need to be killed.
Starting dump at 8/08/2014 3:55:15 PM
Starting Heap dump on Process 1704 running architecture AMD64.
set _NT_SYMBOL_PATH=SRV*C:\Users\UserId\AppData\Local\Temp\3\symbols*http://msdl.microsoft.com/download/symbols
Exec: "C:\Users\UserId\AppData\Roaming\PerfView\VER.2014-08-08.13.49.17.346\AMD64\HeapDump.exe" /MaxDumpCountK=250 "1704" "TestProcess.1.gcdump"
Looking for C:\Users\UserId\AppData\Roaming\PerfView\VER.2014-08-08.13.49.17.346\Microsoft.Diagnostics.FastSerialization.dll
Dumping process 1704 with id 1704.
Process Has DotNet: False Has JScript: False Has ClrDll: False
HeapDump Error: Could not dump either a .NET or JavaScript Heap. See log file for details
Completed: Dumping GC Heap to C:\Install\TM\PerfView\TestProcess.1.gcDump (Elapsed Time: 1.172 sec)
Error: HeapDump failed with exit code 1
Directory TestProcess.1.gcdump does not exist

Hi,
Below is the DDL taken from different database. Will this be enough ? One more thing please, what shall be the password should it be DMSYS.....since this will not be used by me but system.
CREATE USER "DMSYS" PROFILE "DEFAULT" IDENTIFIED BY "*******" PASSWORD EXPIRE DEFAULT TABLESPACE "SYSAUX" TEMPORARY TABLESPACE "TEMP" QUOTA 204800 K ON "SYSAUX" ACCOUNT LOCK
GRANT ALTER SESSION TO "DMSYS"
GRANT ALTER SYSTEM TO "DMSYS"
GRANT CREATE JOB TO "DMSYS"
GRANT CREATE LIBRARY TO "DMSYS"
GRANT CREATE PROCEDURE TO "DMSYS"
GRANT CREATE PUBLIC SYNONYM TO "DMSYS"
GRANT CREATE SEQUENCE TO "DMSYS"
GRANT CREATE SESSION TO "DMSYS"
GRANT CREATE SYNONYM TO "DMSYS"
GRANT CREATE TABLE TO "DMSYS"
GRANT CREATE TRIGGER TO "DMSYS"
GRANT CREATE TYPE TO "DMSYS"
GRANT CREATE VIEW TO "DMSYS"
GRANT DROP PUBLIC SYNONYM TO "DMSYS"
GRANT QUERY REWRITE TO "DMSYS"
GRANT SELECT ON "SYS"."DBA_JOBS_RUNNING" TO "DMSYS"
GRANT SELECT ON "SYS"."DBA_REGISTRY" TO "DMSYS"
GRANT SELECT ON "SYS"."DBA_SYS_PRIVS" TO "DMSYS"
GRANT SELECT ON "SYS"."DBA_TAB_PRIVS" TO "DMSYS"
GRANT SELECT ON "SYS"."DBA_TEMP_FILES" TO "DMSYS"
GRANT EXECUTE ON "SYS"."DBMS_LOCK" TO "DMSYS"
GRANT EXECUTE ON "SYS"."DBMS_REGISTRY" TO "DMSYS"
GRANT EXECUTE ON "SYS"."DBMS_SYSTEM" TO "DMSYS"
GRANT EXECUTE ON "SYS"."DBMS_SYS_ERROR" TO "DMSYS"
GRANT DELETE ON "SYS"."EXPDEPACT$" TO "DMSYS"
GRANT INSERT ON "SYS"."EXPDEPACT$" TO "DMSYS"
GRANT SELECT ON "SYS"."EXPDEPACT$" TO "DMSYS"
GRANT UPDATE ON "SYS"."EXPDEPACT$" TO "DMSYS"
GRANT SELECT ON "SYS"."V_$PARAMETER" TO "DMSYS"
GRANT SELECT ON "SYS"."V_$SESSION" TO "DMSYS"
The other database has the DMSYS and the status is EXPIRED & LOCKED but I'm still able to take the dump using datapump??

St22 Dump in Mail

Dear All,
I want to configure the St22 dump in mail , With criteria if Mail is more than 150 in a day it should send a mail.Please Let me know the steps need to be done.
RK

Hello Rableen,
in RZ20 there are several MTEs, where dumps are catched, for example, ABAP dumps are displayed under:
RZ20 --> SAP CCMS Monitor Templates
               --> Entire System
                    --> <SID> --> Application Server
                         --> <instance> --> R3Abap
and here you have these MTEs
You can configure threshold values in the properties of MTE "Shortdumps Frequency" and assign an autoreaction method.
But this MTE is only for ABAP dumps. Other type of dumps you can find as described in KBA:
1942651 - RZ20 does not display shortdumps
but there is no such monitor in RZ20, which cathes all dumps from ST22 in one MTE.
Regards,
Alwina

Dump using Dynamic WHERE condition (EXISTS + subquery)

Hi experts,
I want to use dynamic WHERE here, but I got a problem when using EXISTS + subuery.
Here is my code snippet:
And the actual SQL sentence should be like this:
When I execute this program, an exception CX_SY_DYNAMIC_OSQL_SEMANTICS is raised and the program dumps.
Dump Information:
Short text
   A dynamically specified column name is unknown.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SEMANTICS', was
     not caught in
    procedure "FRM_GET_ALL_PROD_ORDERS" "(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:
    An Open SQL clause was specified dynamically. The contained field name
    "EXISTS" does not exist in any of the database tables from the FROM clause.
I'm confused because the plain text of my WHERE condition looks good. Could you tell me why I encountered this problem?
Many thanks,
Shelwin

Hi Shelwin !
Testing your code i dont have dump, using this:
REPORT z_test MESSAGE-ID z_test_msgs.
DATA: lt_where_tab1 TYPE STANDARD TABLE OF edpline WITH HEADER LINE,
      lt_where_tab2 TYPE STANDARD TABLE OF edpline WITH HEADER LINE,
      gt_detail     TYPE STANDARD TABLE OF caufv WITH HEADER LINE.
CONCATENATE 'EXISTS (SELECT J_1~STAT FROM JEST AS J_1 INNER JOIN TJ02T AS T_1'
            'ON J_1~STAT EQ T_1~ISTAT'
            'WHERE J_1~OBJNR EQ CAUFV~OBJNR'
            'AND J_1~INACT EQ '' '''
            'AND T_1~SPRAS EQ ''E'''
            'AND T_1~TXT04 EQ ''CRTD'')'
            INTO lt_where_tab1.
CONCATENATE 'NOT EXISTS (SELECT J_2~STAT FROM JEST AS J_2 INNER JOIN TJ02T AS T_2'
            'ON J_2~STAT EQ T_2~ISTAT'
            'WHERE J_2~OBJNR EQ CAUFV~OBJNR'
            'AND J_2~INACT EQ '' '''
            'AND T_2~SPRAS EQ ''E'''
            'AND T_1~TXT04 IN (''TECO'' , ''DLFL'', ''DLV'', ''CLSD''))'
            INTO lt_where_tab2.
SELECT aufnr ftrms gltrs
FROM caufv
INTO CORRESPONDING FIELDS OF TABLE gt_detail
WHERE (lt_where_tab1)
   AND (lt_where_tab2).
BREAK-POINT.
Regards,
Edited for error on image.

Trigger ST22 Dumps as EMAIL

Hi Everyone,
I want all my ST22 Dumps to be automatically triggered to a particular User mail id (Busines Workplace). so that, if any new Dump comes in a Production system i will come to know that while checking mail and provide solution immediately.How this can be done from Basis side
Thanks& Regards,
Siva

Hai,
Check the below link.....
http://help.sap.com/saphelp_nw70/helpdata/en/2c/abb2e7ff6311d194c000a0c93033f7/frameset.htm
Regards,
Yoganand.V

Cannot complete dump using db1_dump185

We have an older BerkeleyDB database file of 22810624 bytes. When we dump using:
./db1_dump185 -p dbfile
it ends with the following error
db1_dump185: seq: Cannot allocate memory
We were using DB_File perl module to read/write the database but either it became corrupted or reached some size limit and now we can't access all the data.
Can anyone help with suggesting as to how to retrieve all the information in the database?

We have an older BerkeleyDB database file of 22810624 bytes. When we dump using:
./db1_dump185 -p dbfile
it ends with the following error
db1_dump185: seq: Cannot allocate memory
We were using DB_File perl module to read/write the database but either it became corrupted or reached some size limit and now we can't access all the data.
Can anyone help with suggesting as to how to retrieve all the information in the database?

'DBIF_RSQL_INVALID_RSQL' short dump

Hello All,
I have a dynamic where_clause in a select query. ie its created at runtime. I get a short dump 'DBIF_RSQL_INVALID_RSQL' at the select statement. The reason shown in ST22 is:
Possible errors:
o The maximum size of an SQL statement has been exceeded.
o The statement contains too many input variables.
o The space needed for the input data exceeds the available memory.
Could you please suggest a solution to the problem, since the data to be fetched is large I would not want to use select-endselect loop as that would make it slower.
Thanks in advance,
Anju

Hi Anju,
Check the link
[ Perfect link|
DBIF_RSQL_INVALID_RSQL;
Regards,
Sandeep

SAP ST22 dump SAPSQL_ARRAY_INSERT_DUPREC

Hi All,
We are getting dump SAPSQL_ARRAY_INSERT_DUPREC in testing system. SAP basis: 701 and Oracle 10.2.0.2
We are getting this dump from yesterday only and the details of the dump are as mentioned below:
============================================================================================
Short text
    The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSBAL_DB_INTERNAL" had to be terminated because it
     has
    come across a statement that unfortunately cannot be executed.
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 "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(FUNCTION)", 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:
    If you use an ABAP/4 Open SQL array insert to insert a record in
    the database and that record already exists with the same key,
    this results in a termination.
    (With an ABAP/4 Open SQL single record insert in the same error
    situation, processing does not terminate, but SY-SUBRC is set to 4.)
Information on where terminated
    Termination occurred in the ABAP program "SAPLSBAL_DB_INTERNAL" - in
     "BAL_DB_INTERNAL_NO_UPDATE_TASK".
    The main program was "SWNCCOLL ".
    In the source code you have the termination point in line 64
    of the (Include) program "LSBAL_DB_INTERNALU02".
    The program "SAPLSBAL_DB_INTERNAL" was started as a background job.
    Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
    Job Initiator.. "BASIS"
    Job Number..... 08893100
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(FUNCTION)", but it was neither
     handled locally nor declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLSBAL_DB_INTERNAL "; its source code begins
     line
    1 of the (Include program "LSBAL_DB_INTERNALU02 ".
System environment
    SAP-Release 701
    Application server... "appl543"
    Network address...... "122.99.01.88"
    Operating system..... "AIX"
    Release.............. "5.3"
    Hardware type........ "099DER88BN90000"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 27
    Shortdump setting.... "full"
    Database server... "appl543"
    Database type..... "ORACLE"
    Database name..... "Q22"
    Database user ID.. "SAPSR3"
=====================================================================================================
Also some jobs are cancelled and they are forming the above dump. the detials are:
SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 00:43:31
SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 02:43:31
SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 03:43:31
SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 04:43:31
SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 05:43:31
SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 06:43:31
**The cancelled job SAP_COLLECTOR_FOR_NONE_R3_STAT generating the above dump at ST22.**
Please suggest us a solution. Thanks in advance!!!
Regards
Veera
Edited by: Veerab on Dec 17, 2010 11:33 AM

>     1 of the (Include program "LSBAL_DB_INTERNALU02 ".
Try the following:
open http://service.sap.com/notes
Search for "LSBAL_DB_INTERNALU02"
Markus

ST22 Dumps: Shared Objects

Hi SDN,
in our SRM System, SRM Server 5.5, WAS700 ABAP, we get ST22 Short Dumps concerning "shared objects".
This is the Dump Short Analysis:
Runtime Errors         SYSTEM_NO_SHM_MEMORY
Date and Time          19.08.2008 12:20:50
Short text
     No more memory for 2516576 bytes in the shared objects memory.
What happened?
     The shared objects memory is full or an area management specified
     memory limit has be reached.
In heard, that "shared objects" is part of the new WAS 620, 640, 2004s, 700 ... releases
What are exactly these shared objects. And how can we avoid the dumps?
We have an instance profile parameter set:
abap/shared_objects_size_MB                 100
Apparently this is not enough... Are there any recommendations?
thanx, matthias

Take a look at [Note 972757 - Occurence of the SYSTEM_NO_SHM_MEMORY runtime error|https://service.sap.com/sap/support/notes/972757] for further information. You should investigate what is using the shared objects memory, it may be an error in a application. The note will help to determine this.
Regards,
Nelis

RV60SBAT DBIF_RSQL_INVALID_RSQL - ST22 dump using VF06

Similar Messages

Maybe you are looking for