SAP Client Copy taking loooonger than usual.

[reza_memari]

We do our client copies regularly to clone our Production environment to our QA Environment.

The export from Production was done successfully. The import into QA is running for 48 hours now (Usually it takes less than 24 hours).

TRBAT & TRJOB Tables are empty, The import monitor shows transport is running with return code 8888.

When monitoring the Database, we can see some activities carried out by R3trans.

Recently we have upgraded our OS from AIX 5.3.11 to 6.1.7, and our DB from DB2 9.1.10 to 9.5.9.

Do we need a kernel upgrade? Current Kernel level  291.

How do we stop the current import? or should we wait till it concludes?

Regrds.

[reza_memari · Accepted solution]

Thank you Guys for all the help.

Just for the records, we have resolved the issue. After almost 80 hours of import process, the import failed with following errors:

SQL error -101 accessing  : SQL0101N  The statement is too long or too complex.

After analysing the import logs, we also came across the following error:

4 ETW000 twrtab reached memory limit;

The above two errors were related to memory allocation and utilization by R3trans. The solution was to change "tcs" option for R3trans to half the memory limits identified by second error above.

In addition, we also had to adjust DB parameters: STMTHEAP & PCKCACHESZ.

The import ran after the above changes was a successful one.

Thanks again.

[Former Member]

Hi Reza,

Check any error are getting in transport log directory or at work directory.

And check the log also in SM21,archive files are generating are not at D/B level.

U can stop at any point of time and then again u can start the client copy it may not affect any problem's  in the system.

Regards,

Anil

[Former Member]

Try transcation SCC3 (copy logs) there should be a cancel button for running copies. I am not 100 percent sure if that works for client transports too.

Cheers Michael

[HuseyinBilgen]

Hi Reza,

How did you started the import? With which command?