Runtime Error ( EXPORT_NO_SHARED_MEMORY ) while creating order in CRM

Question

Hi All,
i am getting runtime error while creating order in CRMD_ORDER. details of error is provided below
Runtime Errors         EXPORT_NO_SHARED_MEMORY
Exception              CX_SY_EXPORT_NO_SHARED_MEMORY
Date and Time          29.01.2009 02:07:58
Short text
     Der EXPORT-Datencluster ist zu groß für das SHARED MEMORY.
What happened?
     The current program had to be terminated because
     a capacity limit has been reached.
What can you do?
     Please make a note of the actions and input which caused the error.
     To resolve the problem, contact your
     SAP system administrator.
     Select the "Print" function to obtain a hardcopy of the
     current termination message.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_EXPORT_NO_SHARED_MEMORY', was
      not caught in
     procedure "CRM_EVENT_PUBLISH_OW" "(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:
This is probably due to a very large dataset, for which there are
insufficient resources in your installation.
Das SHARED MEMORY kann Objekte nur bis zu einer bestimmten Maximalgröße
speichern (1) und hat selbst eine beschränkte Größe (2).
In diesem Fall wurde die Größe 2 überschritten.
to correct the error
Mit den Profilparametern rsdb/esm/buffersize_kb und
rsdb/esm/large_object_size kann man diese Größen verändern.
Informationen über diese Parameter erhalten Sie mit der
Transaktion RZ11.
Beachten Sie jedoch, dass aus Performancegründen ein einzelnes
Objekt nicht den größten Teil des Puffers belegen darf, so dass die
maximal zulässige Objektgröße erheblich unter der Gesamtgröße des
Puffers liegt.
The exception must either be prevented, caught within proedure
"CRM_EVENT_PUBLISH_OW" "(FUNCTION)", or its possible occurrence must be
declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:

Answer 1

Hello Sudhir,
Have you set the user parameter CRM_EVENT_TRACE as one of your personal
user settings? If this is the case, remove this parameter and the dump will no longer occur. The parameter is intended for test purposes only, for a report which evaluates
which events are published and which function modules are called as a
result of these events. However, depending on system settings, the
allocated memory may be too low and lead to the short dump.
(CRM_EVENT_TRACE is the report which can execute in SE38.)
Regards, Gerhard