why does support package SAPKH60014 15 & 16 take so long (ECC 6.0)?

[MPGraziano]

I've been running these three items in a que for 2days. I don't see any errors in the morning, but maybe because I can't see the errors?

I thihk that 14 & 15 have completed and now running on 16

Has anyone implemented and had similar experience?

ECC 6.0 on Win 2003 SQL 2005 , 64bit OS , Unicode....

Thank you in advance

Maria

[markus_doehr2 · Accepted solution]

> I thihk that 14 & 15 have completed and now running on 16

> Has anyone implemented and had similar experience?

Open a second mode in client 000 and check the import logs. There you can see where the import is running.

Did you change the SPAM parameter to use a parallel import? If you have only one R3trans process then it will take pretty long to update those big packages.

Markus

[MPGraziano · Accepted solution]

The logs indicate that both 15 & 16 ran completely with err code 004 (shuld be fine)

however

in the import steps section there is an indication for table conversion with error code 012, however the next entry indicates that

'Feedback after export or import successfull'

rather confusing

btw,

how do you change the spam param?

[markus_doehr2 · Accepted solution]

> in the import steps section there is an indication for table conversion with error code 012, however the next entry indicates that

> 'Feedback after export or import successfull'

Some phases run a few times - dependencies between tables make that necessary. As long as the main returncode is fine the import is correctly done.

> how do you change the spam param?

SPAM

--> Extras - Settings

---> Parallel import (I'd set to the number of CPUs you have)

Markus

[MPGraziano · Accepted solution]

So can I set it while a patch is running? and will it take effect?

[markus_doehr2 · Accepted solution]

Transaction SPAM is locked during an import run - so you can't change that now - but you can change it when the import finished for the next support packages.

Markus