Upgrade performance during PARCONV_UPG

[thomas_obermeier]

Just wanted to announce the delivery of R3up/SAPup versions on the service marketplace. The patch addresses the problem that only one of multiple submitted tp processes has to perform allmost all conversions.

<b>6.40: R3up (version 21.098)

7.00: SAPup (version 24.056)</b>

Any feedback is highly welcome.

Regards,

Thomas

[Former Member]

Hi Thomas,

I just discussed with the client in Begium and they had really great news !

From 70h down to 14 hours !!!!

Congratulations and thanks for this fix !

Stay the only question on the best implementation ...

Would it be ok to use the following ?

APYR3FIX SID(BRP) SAVF(PATCHES/SAPUP)

SAVLIB(GEN700AOPT) KRNLIB(SAPUP)

EXEPATH('/usr/sap/put/exe') GETSAVF(*NO)

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

[thomas_obermeier]

Hi,

Did not explicitly test the execution of APYR3FIX in the two releases on my own. Details for patching of the R3UP/SAPUP libraries can be found in <b>notes

661569 (6.40)

822296 (7.00)</b>

Your processing should be ok, but parameter EXEPATH is of no relevance as far as I remember.

HTH,

Thomas

[Former Member]

Hi Volker,

does QDBENCWT parameter need to be enabled to allow parallel tp processes ? A currently running PARCONV_UPG phase from 4.6C to ERP2005 does not seem to use parallel tp processes. SAPup is latest 24.05x.

OSS note 992299 about QDBENCWT does not clearly talk about PARCONV activities.

Thanks,

Juergen

Message was edited by: Juergen Ilg

Message was edited by: Juergen Ilg

[Former Member]

Hi Jürgen,

this has NOTHING to do with each other :-((

QDBENCWT describes performance optimizations since V5R3, that are interesting in a multi user environment => it would be useful to turn that on in general in SAP environments.

Parallel PARCON_UPG ...

There you need at least the following version:

SAPup version 7.00/2, build 24.056

as you are writing on 24.05x I don't know yet ... I tried this several times in the meantime and this always worked fine ...

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

[Former Member]

Thanks Volker,

it finished after 13,5 hrs. Quite long compared to other platforms but at least it finished successful.

Thanks for your input about QDBENCWT.

Juergen

[Former Member]

Hi Jürgen,

PARCON_UPG works totally different on iSeries, because for every "ALTER TABLE" the complete table needs to be copied around in order to reduce the overhead with different row sizes during runtime later.

Therefore, it is typical, that this phase takes longer on iSeries. The only question would be:

Did you see several TPs doing something or did all except 1 terminate after a few seconds - and I guess, they were working ... (even when slower than you expected)

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

[Former Member]

Hallo Volker,

SAPup is on 24.056 but only one TP process could be seen during entire PARCON_UPG phase. I specified 3 parallel tp´s .

Thanks again,

Juergen

[Former Member]

Hi Jürgen,

then I would open a ticket with BC-DB-DB4 ...

They fixed it especially with this patch. You will have to provide a few log files and then the root cause should be possible to be investigated ...

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

[thomas_obermeier]

Hi Jürgen,

Are you sure the required R3up version was active during prepare? You can easily tell by looking up R3upcheck.log. If phase JOB_RSDB4090 ran you had the required patch. This phase is supposed to update/fill the statistic tables which are required to do a reasonable splitting of the tp workload. If the statistic table DB4TABLE_STAT is empty, all tables will be converted by one tp.

Regards,

Thomas

[Former Member]

Hi Thomas,

that explains. We used SAPup7002_13-20001266.SAR to patch SAPup. However SAPupchk.log states :

...

1. This is SAPup version 7.00/2 patch level 24.038

So patching of SAPup failed.

Juergen

[Former Member]

Hi,

Did you apy the sapup fix as staded in the oss notes?

Otherwise you will still use the old version of sapup

UPDIFS HYBLIB(SAPup) IFSPATH('/usr/sap/put/bin') MODE(SELECT) APPLYLINK(NO) TYPE(*IFS)

UPDIFS HYBLIB(SAPup) IFSPATH('/usr/sap/put/tools') MODE(SELECT) APPLYLINK(NO) TYPE(*IFS)

Kind regrads,

Paul Hoogendoorn

[Former Member]

I'd like to throw in a question here on this subject. It seems very newbie-ish, but I am a newbie to 400. I am attempting a SolMan upgrade, and I am running into a issue where I also need to upgrade SAPUP for the upgrade. I'm pulling my hair out over this one. I am trying to use the UPDIFS command, but it doesn't look like it's available on my system.

When I try to run UPDIFS, I receive:

Command UPDIFS in library *LIBL not found.

I tried a wrkobj lookup, but it didn't show up anywhere. My 400 guy has never heard of this command before. Where does it come from? Can anyone help?

Thanks...

Randall

[thomas_obermeier]

Hi Randall,

UPDIFS should be located in your SAPUP library as all the other tools you need to apply a fix for SAPup. In case you were not aware: There is a dedicated section for how to handle patches in note 822296.

HTH,

Thomas