Skip to Content
author's profile photo Former Member
Former Member

EXTRACT_FWRITE_FAILED

SAP 4.7 6.20 OS: Windows Server 2003 Oracle 10g

I'm a new Basis professional, and also new at this forum, so sorry for any mistakes...

Almost once a week I have some short dumps with this message : EXTRACT_FWRITE_FAILED.

I also have this information :

You have 10 Gb free on this device.

Error message :

The extracts could not be written to the temporary file

"U:\usr\sap\PRD\D00\data\E000NL5I.DAT" (file size

0).

Error number: 28

Error text: "No space left on device"

There is a company in France who solves the problem, but we never know what they did in order to solve it.

They just say that the area was full...

After some days of verification, I discovered that sometimes we have big files at his directory :

"U:\usr\sap\PRD\D00\work\" , and I believe that this is what is causing the problem.

Inside this work folder I have a very big file : dev_w0.old 1,7 Gbs generated today at 5:05am.

I think that this is a log or trace file generated by work process 00.

How could I discover the process/user which is generating such a big file ? What's the best technical way to do so ?

I also have inside this very same folder a lot of other files with extensions : .read .conv .

Some of them were generated in 2008 and 2009.

What is this work folder used for ? I'm trying to understand what kind of processes created them, and also if I could delete some of them...

Thanks in advance,

Eduardo

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Sep 09, 2010 at 05:32 PM

    Hi,

    Under work dir, the work process traces are generated. The dev_w0.old you mentioned is the old trace file for work process w0, you may have a check the work process status in SM50. The .old traces are the ones before the laste system reboot. For example, you have 10 work processes in SM50 for the current instance, then under work dir, you will see the crurrent traces, dev_w0,...,dev_w9, and also, the old traces before last system reboot, dev_w0.old,...,dev_w9.old.

    It is ok to remove .old as the constains the actions or activities of the work processes before the last system reboot.

    Regards,

    Snow

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Sep 09, 2010 at 08:21 PM

    Is there an automatic sap routine in order to delete these .old files related to the work process traces ?

    And about the .read and .conv files ?

    Can I delete them ? I'm kind of afraid of stopping something in SAP system because of that...

    Eduardo

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Sep 10, 2010 at 07:09 PM

    Hello,

    By reading some notes, I learned that the .conv and .read files are generated by transaction LSMW. They are usually generated during the implantation of SAP in order to charge some tables, and they will not be removed unless I delete them manually. So I moved the files generated in 2008 and 2009 to another server just in case someone complains about something. Next month I will delete them forever. So this problem is solved.

    About the .old files, the system passed through a reboot, so this was the cause of the big dev_w0.old file. Our trace level is 1 (only errors).

    The only doubt I have now is to know if the .old files related to the work processes will be deleted automatically by sap system or if someone is supposed to delete them manually.

    I tried to find something about that, in Google and sap notes, but I didn't find this answer.

    Do you have this information ?

    Eduardo

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      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?

      -

      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 |

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.