Export Import Client take a long time

[Former Member]

HI, Gurus

I export client PRD to QAS by T-Code: SCC8 , background is finish spend time 15 Hours and then <br>

import at target client by STMS take a long time, now is over 20 hourse but status is running. <br>

database on QAS is growth 30%

I saw log <br>

/usr/sap/trans/log/PRDET00021.PRD <br>

at 10 last row <br>

4 ETW000 0 entries from RFIDPTPRVAL exported (900*). <br>

4 ETW679 end export of "R3TRTABURFIDPTPRVAL". <br>

3 ETW678Xstart export of "R3TRTABURFRR" ...

3WETW206 scrap char 0x0000 found in RFRR.โu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20AC

<br>1AETP000 R3trans received signal 11 from operating system. <br>

2EETP200 Export with errors, request will not be imported <br>

1 ETP150 MAIN EXPORT <br>

1 ETP110 end date and time : "20100127161434" <br>

1 ETP111 exit code : "13" <br>

1 ETP199 ###################################### <br>

how i can do ?.

stop transport , resolve and new export ?

or wait for finish transport.

PRD system is ECC 6.0 database size 243 GB ( 2 Client 800 is Pre-Production and 900 is Production) <br>

OS: Solaris RAM 64GB<br><br>

QAS ECC 6.0 OS: Solaris RAM: 16 G <br><br>

Thank for advise.

[former_member186775 · Accepted solution]

Hi

Please let it go on...yes it will take time...15hrs is not much time....

In our company ..I have observed it took more than 30 hrs...

also it depends on size of the client and the data.

regards,

Manjula .U

[Former Member · Accepted solution]

HI, Manjula

Now, Status on STMS import is still running over 40 hours

database size same 20 hours befor,

archive log is same befor, create 2-3 file per hours

Thank ,

[paul_power · Accepted solution]

Hi,

do you still see the entry:

usr/sap/trans/log/PRDET00021.PRD

at 10 last row

4 ETW000 0 entries from RFIDPTPRVAL exported (900*).

4 ETW679 end export of "R3TRTABURFIDPTPRVAL".

3 ETW678Xstart export of "R3TRTABURFRR" ...

3WETW206 scrap char 0x0000 found in RFRR.โu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20ACโu20ACu20AC

1AETP000 R3trans received signal 11 from operating system.

2EETP200 Export with errors, request will not be imported

1 ETP150 MAIN EXPORT

1 ETP110 end date and time : "20100127161434"

1 ETP111 exit code : "13"

1 ETP199 ######################################

The signal 11 could indicate memoryproblems which are most likely to

appear when importing cluster or transparent table

A possible solution might be to delete the entries in the target client

before the import or otherwise to exclude the clustertable from the

client export and to transport it separately. Check note #68896 for more

information on these topics.

Table RFRR is a work table. Its content will be filled by the two

reports RFDRRGEN and RFKRRGEN (batch jobs) periodically. So you can

exclude the table from the transport. Please do it by using

report RSCCEXPT (see note #70290 - see attachment).

After this you can start your export of the client.

If all is done, start the reports RFDRRGEN and RFKRRGEN to create the

table RFRR.

Note 718511 is also applicable here, you could clean up the scrap characters and then retry the export.

Kind regards,

Paul