Категория              Дефицит ресурсов
ДинамОшибка            MEMORY_NO_MORE_PAGING
Дата и время           23.04.2014 12:56:40

Краткий текст
     SAP paging overflow when storing data in the ABAP/4 memory.
Что произошло?
     The current program requested storage space from the SAP paging area,
     but this request could not be fulfilled.
     of this area in the SAP system profile.
Что Вы можете сделать?
     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.
Анализ ошибки
    The ABAP/4 runtime system and the ABAP/4 compiler use a common
    interface to store different types of data in different parts of
    the SAP paging area. This data includes the
    ABAP/4 memory (EXPORT TO MEMORY), the SUBMIT REPORT parameters,
    CALL DIALOG and CALL TRANSACTION USING, as well as internally defined
    macros (specified with DEFINE).
    To store further data in the SAP paging area, you attempted to
    allocate a new SAP paging block, but no more blocks were
    available.
    When the SAP paging overflow occurred, the ABAP/4 memory contained
    entries for 214 of different IDs.
    Please note:
    To facilitate error handling, the ABAP/4 memory was
    deleted.
Указания по устранению ошибки
    The amount of storage space (in bytes) filled at termination time was:
    Roll area...................... 1712480
    Extended memory (EM)........... 276526272
    Assigned memory (HEAP)......... 0
    Short area..................... " "
    Paging area.................... 24576
    Maximum address space.......... 4294967295
    By calling Transaction SM04 and choosing 'Goto' -> 'Block list',
    you can display an overview of the current roll and paging memory
    levels resulting from active users and their transactions. Try to
    decide from this whether another program requires a lot of memory
    space (perhaps too much).
    The system log contains more detailed information about the
    termination. Check for any unwanted recursion.
    Determine whether the error also occurs with small volumes of
    data. Check the profile (parameter "rdisp/PG_MAXFS", see
    Installation Guidelines).
    Is the disk or the file system that contains the paging file
    full to the extent that it cannot be increased, although it has
    not yet reached the size defined in the profile? Is the
    operating system configured to accommodate files of such a
    size?
The ABAP processor stores different types of data in the SAP
paging area. These include:
   (1) Data clusters (EXPORT ... TO MEMORY ...)
   (2) Parameters for calling programs (SUBMIT REPORT ...),
       Dialog modules (CALL DIALOG ...) and transactions
       (CALL TRANSACTION USING ...)
   (3) Internally defined program macros (DEFINE ...)

  Accordingly, you should check the relevant statements in a program
  that results in an overflow of the SAP paging area.
  It is critical when many internal tables, possibly with
  different IDs, are written to memory (EXPORT).
  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:
   "MEMORY_NO_MORE_PAGING" " "
   "SAPDBPSJ" or "DBPSJPUT"
   "PUT_RSTHIE"
  If you cannot solve the problem yourself and want to send an error
  notification to SAP, include the following information:
  1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
  (Unconverted)".
  2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
  after the short dump. Then choose "System->List->Save->Local File
  (Unconverted)".
  3. If the problem occurs in a problem of your own or a modified SAP
  program: The source code of the program
    In the editor, choose "Utilities->More
  Utilities->Upload/Download->Download".
  4. Details about the conditions under which the error occurred or which
  actions and input led to the error.