Com.sap.inst.split.str.StrExtSplitTask processEmptyPackages

Question

Hi,
we are getting this error while starting export.
INFO: 2009-02-10 07:22:19
Package 'SAPUSER1' will be stored in 'SAPUSER1.EXT/STR' files.
INFO: 2009-02-10 07:22:19
File '/oracle/MSG/sapdata2/coredmp/ABAP/DATA/SAP0000.EXT' was renamed to 'SAP0000.EXT.old'.
ERROR: 2009-02-10 07:22:19 com.sap.inst.split.str.StrExtSplitTask processEmptyPackages
java.io.IOException: A system call received a parameter that is not valid.
     at sun.nio.ch.FileChannelImpl.map0(Native Method)
     at sun.nio.ch.FileChannelImpl.map(FileChannelImpl.java:737)
     at sun.nio.ch.FileChannelImpl.transferFromFileChannel(FileChannelImpl.java:542)
     at sun.nio.ch.FileChannelImpl.transferFrom(FileChannelImpl.java:605)
     at com.sap.inst.lib.io.FileUtils.copyFile(FileUtils.java:447)
     at com.sap.inst.split.str.StrExtSplitTask.processEmptyPackages(StrExtSplitTask.java:459)
     at com.sap.inst.split.str.StrExtSplitTask.doRun(StrExtSplitTask.java:142)
     at com.sap.inst.split.str.StrSplitTask.run(StrSplitTask.java:194)
     at com.sap.inst.split.PackageSplitter.startAppJob(PackageSplitter.java:348)
     at com.sap.inst.lib.app.CommandLineApp.doMain(CommandLineApp.java:111)
     at com.sap.inst.split.PackageSplitter.main(PackageSplitter.java:390)

Answer 1

Note 1333874 works! We are doing a Unicode migration. During the export we used a "CIO" mounted filesystem as target for the "export files" which lead to the following error in the file:
../sapinst_instdir/NW04S/LM/COPY/ORA/EXP/CENTRAL/AS-ABAP/EXP/str_splitter.log
ERROR: 2010-11-18 12:37:15 com.sap.inst.split.str.StrExtSplitTask processEmptyPackages
Exception during processing of 'SAPVIEW' package.
java.io.IOException: A system call received a parameter that is not valid.
        at sun.nio.ch.FileChannelImpl.map0(Native Method)
        at sun.nio.ch.FileChannelImpl.map(FileChannelImpl.java:737)
Changed to none CIO mounted filesystems... Problem solved!
Edited by: M. Kuijper on Nov 18, 2010 10:21 PM