Skip to Content
0
Former Member
Jul 04, 2012 at 11:14 AM

abap dump EXTRACT_FWRITE_FAILED, while executing f.08

57 Views

Hi,

I am facing one problem related to abap dump EXTRACT_FWRITE_FAILED, when we executing f.08 and mm60 then this dump appear in both foreground and background; both transaction f.08 and mm60 are some little bit heavy report. Mainly this dump comes when disk space problem in usr directory.

But in my case everything is OK. Anyone which face this type of problem?

-Dump-

Runtime Errors EXTRACT_FWRITE_FAILED

Date and Time 03.07.2012 11:08:51

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|Short text |

| Error when writing the extracts into the temporary file. |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|What happened? |

| Runtime error |

| |

| The current ABAP program "RFSSLD00" had to be terminated because one |

| of the statements could not be executed at runtime. |

| |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|What can you do? |

| 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 |

| The extracts could not be written into the temporary file |

| "G:\usr\sap\PRD\DVEBMGS00\data\E00008N6.DAT" (file size |

| : 0 byte). |

| |

| Error number: 22 |

| Error text: "Invalid argument" |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|How to correct the error |

| If the error cause indicates that the available memory space is not |

| sufficient for the extract, you should ensure that there is enough space |

| in the file system containing the directory "G:\usr\sap\PRD\DVEBMGS00\data" |

| (the extract file is |

| stored in this directory) or use the profile parameter DIR_EXTRACT to |

| select a different directory. |

| |

| |

| 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. |

| |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|System environment |

| SAP-Release 700