Symptom

An R3trans export terminates with the message

"ETW030 Cannot write to datafile any more (fwrite() at position ...)."

or

"ETW030 Cannot write to datafile any more (fclose() at position ...)."

Reason and Prerequisites

The following causes are possible:

      1. The file system is full (you can check this with UNIX command df or bdf).

      2. The user has reached his/her personal disk space quota (if a quota has been defined; you can check this with UNIX command quota -v).

      3. The directory is mounted via NFS, and network problems caused an NSF timeout.

      4. The permissions were changed during the export (check with ls -l).

      5. The file has reached the maximum size for files.  Things get tight above a file size of 2GB (check with ls -l).

      6. For operating system HP-UX:

            a) Releases up to 3.1I support HP-UX 10.20 as well as HP-UX 10.01. Therefore, it is not possible to process files > 2GB.

            b) For releases as of 4.0A either an old R3trans is used or the large file system is not activated on the hard disk.

            c) For releases as of 4.6B or HP-UX-64bit the large file system is not activated.

      7. For operating system Linuxintel

            a) For kernel release 6.20, files > 2GB are possible as of the R3trans version of 04/20/04.

            b) For kernel release 4.6D, files > 2GB are possible as of the R3trans version of 04/20/04.

            c) For kernel releases < 4.6D and kernel release 6.10, there is no solution.

      8. "Large file support" is only possible for various operating systems as of a specific version. Refer to Note 330992 for information about this.

      9. The drive lost its drive position for the direct write on a tape. Up to now this problem occured only when IBM drives were used.

      10. UNIX: A user-specific limit is defined für the maximum file size.

Solution

1,2: Add space, delete unnecessary files.

3: Repeat the export.

4: Correct the permissions and repeat the export.

5: Execute the transport in several smaller parts. As of Release

   4.5A a solution is available which is described in Note 86535.

6.a: See no. 5)

6.b: Download the current R3trans patch from sapservX:

    * 4.0A/B:  ~ftp/general/R3server/patches/rel40B/...

    * 4.5A: Apply the 4.5B kernel which is downward compatible (see Note 149682) and then the R3trans patch for 4.5B.

    * 4.5B: ~ftp/general/R3server/patches/rel45B/...

    * 4.6A: Apply the 4.6B kernel which is downward compatible.

           Also activate the large file system on the hard disk via

"fsadm -o largefile <directory>"

6.c: Activate the large file system on the hard disk via

fsadm -o largefile <directory>

7. For kernel release 6.20, files > 2GB are possible as of the R3trans
   version of 04/20/04.
   For kernel release 4.6D, files > 2GB are possible as of the R3trans
   version of 04/20/04. This version is not available at present.
   For kernel releases < 4.6D and kernel release 6.10, there is no
   solution.

8. Check the operating system version and if necessary upgrade the
   operating system.
For Reliant in particular: As of Reliant 5.44, files of > 2 GB are supported. The following prerequisites must be met:

          o Reliant Version >= 5.44

          o Use the COM kernel

          o Configure the operating system: in /etc/conf/cf.d/stune
               HFSZLIM             0x7FFFFFFFFFFFFFFF
               SFSZLIM            0x7FFFFFFFFFFFFFFF
            must be set.

          o The corresponding user is not allowed to to display any file(size) limits for " ulimit -a" and "limit".

9. Change the data selection in such a way that shorter pauses occur
   when writing or a different tape drive is used.

10. In UNIX you can define the maximum file size for every operating
   system user. Often "ulimit -a" in line File (size) informs you about
   this limit. Increase the limit, if required, and contact your sales
   partner in case of questions. Sometimes a limit may explicitly be
   set by a used scheduler (e.g. "ulimit 4194303" for 2 GB). Therefore
   also check the job files, if you use an external scheduler such as
   cron.