Error while performing system export

[Former Member]

Hi all,

While doing a system export, i am getting errors listed below,

ECC 5, Oracle 9, Windows 2003

In the SAPAPPL0.log,
(WTF) ERROR: write to data file "H:\ECC5_Export/DATA/SAPAPPL0.001" failed
             current table was "ABAPHTML"
(WTF) ERROR: OS error message: Invalid argument
(DB) INFO: disconnected from DB

In SAPAPPL1.log
(WTF) ERROR: write to data file "H:\ECC5_Export/DATA/SAPAPPL1.001" failed
             current table was "AQGDB"
(WTF) ERROR: OS error message: Invalid argument
(CDF) ERROR: file "H:\ECC5_Export/DATA/SAPAPPL1.001" has wrong length 10137600 (expected 10134528)
(DB) INFO: disconnected from DB

In SAPAPPL2.log
(WTF) ERROR: write to data file "H:\ECC5_Export/DATA/SAPAPPL2.001" failed
             current table was "IACMIME"
(WTF) ERROR: OS error message: Invalid argument
(CDF) ERROR: file "H:\ECC5_Export/DATA/SAPAPPL2.001" has wrong length 194334720 (expected 194332672)
(DB) INFO: disconnected from DB

This is the error in R3ldctlExport.log

DbSl Trace: Error 24508 in stmt_fetch()

DbSl Trace: ORA-24508 occurred when executing SQL statement (parse error offset=0)

ERROR: ExeRead for get_loc_table_inf failed
ORA-24508: Message 24508 not found;  product=RDBMS; facility=ORA

Error generating DDLINF.TPL
(UPT) Info: Preparing tables and tablespace entries.
(UPT) Info: Distributing tables and tablespace entries.
(WLL) Info:  finished writing location lists

Tried searching for it on sdn, unable to find a solution.

Regards,

Vishnu

[Former Member]

Hi

Have you fullfill all those pre-requisities,

Please check teh same and rerun export.

Regards,

Deepanshu

[former_member189546]

Hello,

It appears that sone of the export-files (SAPAPPL0.001)

got corrupted when you ran the export.

This could be due to the fact that you had to restart the export

process. If you do not reset all export-files including the TOC-files

completely, the TOC-file will not be overwritten.

The result can be a mismatch of the entries in the TOC-file and the

real file length of the new(!) export-dumpfiles.

file "H:\ECC5_Export/DATA/SAPAPPL1.001" has wrong length 10137600

Please, try to restart from the begining the export database checking

this point.

regards,

John Feely

[Former Member]

John,

Thanks for your input, I have restarted the export. Let me check if I get the error again.

Regards,

Vishnu

[Former Member]

Hi John,

I am getting the same error again. I have cleared all the files from the previous export.

You had said,

This could be due to the fact that you had to restart the export
process. If you do not reset all export-files including the TOC-files
completely, the TOC-file will not be overwritten.
The result can be a mismatch of the entries in the TOC-file and the
real file length of the new(!) export-dumpfiles.

Could you explain what resetting of export files means, or provide me with any useful link?

Regards,

Vishnu

[Former Member]

Hi,

Any Suggestions to the problem I am facing?

Regards,

Vishnu

[Former Member]

Hi,

Have you tried updating R3tools (R3trans, R3load, R3check etc) with latest one...

Regards.

Rajesh Narkhede

[Former Member]

Hi Rajesh,

Let me try it and I will update you.

Thanks,

Vishnu

[Former Member]

Hi Rajesh,

After trying to export again, I was able to correct some of the problems,

however in the SAPSSEXC.log, I find the below error, this is where the export

is terminating,

(WTF) ERROR: write to data file "H:\ECC5_Export/DATA/SAPSSEXC.001" failed
             current table was "DOKCLU"
(WTF) ERROR: OS error message: Invalid argument
(CDF) ERROR: file "H:\ECC5_Export/DATA/SAPSSEXC.001" has wrong length 593375232 (expected 593372160)
(DB) INFO: disconnected from DB

I found a note 945255, but wasn't helpful.

Any Suggestions,

Regards,

Vishnu

[Former Member]

Hi,

Are you doing Unicode Conversion ?

If this is the case you may have to read Unicode Conversion Guide before System Export

Refer the below note :

[SAP Note 551344 - Unicode Conversion Documentation|https://service.sap.com/sap/support/notes/551344]

If this is not the case, I'm afraid, you may need to restart the export from scratch...

(Obviously, with latest R3tools....)

Regards.

Rajesh Narkhede

[Former Member]

Hi Rajesh,

I am not trying to do a Unicode conversion, for my ECC 5.0 is already unicode, with data code page 4103.

I started export with the latest R3tools, but with the same result.

Regards,

Vishnu

[markus_doehr2]

Is H: a local drive? Or is it network mapped?

Markus

[Former Member]

Hi Marcus,

Thank you for responding,

H: is not a local drive, but a network mapped drive.

Strangely, after trying to run the installation a few times, by continuing with the

step run old installation, I was able to export all the tables that were previously

throwing an error. The .TSK files show the tables export as OK. The export was a success.

This is my first time doing a system copy, so I am really not sure

where the problem was.

Regards,

Vishnu

[markus_doehr2]

> H: is not a local drive, but a network mapped drive.

Then I'd say you had network problems/collisions/lost packets

> Strangely, after trying to run the installation a few times, by continuing with the

> step run old installation, I was able to export all the tables that were previously

> throwing an error. The .TSK files show the tables export as OK. The export was a success.

This would point even more to the network problem. I suggest you try to export locally again.

The export should be about 1/10 of the database size (roughly).

Markus

[Former Member]

Hi Markus,

Apologies for misspelling your name in my last post.

Thanks for the information you shared.

Regards,

Vishnu.

[Former Member]

Hi,

Check this thread.

Good Luck,

-Varadhu...

[Former Member]

Hi Varadhu,

Thanks, for your input, I had looked at the link before.

I have selected the correct codepage.

Regards,

Vishnu