EHP4 Installation hanging at CONFLICT_CHECK

[Former Member]

Hi<BR>

<BR>

We are currently facing another issue with the EHP4 installation.<BR>

<BR>

The installation has been the stage CONFLICT_CHECK for over 2 hours, there are no logs produced, no activities on the GUI.<BR>

The entire installation seems to be frozen.

<BR>

<BR>

We have updated EHPI package and the latest SPAM/SAINT.<BR>

<BR>

Operating System : AIX 5.3<BR>

Database : Oracle 10.2.0.4<BR>

<BR>

Any help is greatly appreciated.<BR>

<BR>

LOGS<BR>

<BR>

ritussdb:d88adm 14> tail -20 ULOG10_3<BR>

d88adm 20100810194800 : /EHP4/EHPI/abap/exe/tp pf=/EHP4/EHPI/abap/bin/PCMDIMP.TPP addtobuffer SAPK-60405INISOIL buffer=PCMDIMP.BUF u126 (pid=618982)<BR>

d88adm 20100810194800 : /EHP4/EHPI/abap/exe/tp pf=/EHP4/EHPI/abap/bin/PCMDIMP.TPP setsyncmark SAPK-60405INISOIL buffer=PCMDIMP.BUF (pid=618984)<BR>

d88adm 20100810194801 : /EHP4/EHPI/abap/exe/tp pf=/EHP4/EHPI/abap/bin/PCMDIMP.TPP addtobuffer SAPK-60407INISH buffer=PCMDIMP.BUF u126 (pid=618986)<BR>

d88adm 20100810194802 : /EHP4/EHPI/abap/exe/tp pf=/EHP4/EHPI/abap/bin/PCMDIMP.TPP setsyncmark SAPK-60407INISH buffer=PCMDIMP.BUF (pid=618988)<BR>

d88adm 20100810194803 : /EHP4/EHPI/abap/exe/tp pf=/EHP4/EHPI/abap/bin/PCMDIMP.TPP addtobuffer SAPK-60405INECCDIMP buffer=PCMDIMP.BUF u126 (pid=618990)<BR>

d88adm 20100810194803 : /EHP4/EHPI/abap/exe/tp pf=/EHP4/EHPI/abap/bin/PCMDIMP.TPP setsyncmark SAPK-60405INECCDIMP buffer=PCMDIMP.BUF (pid=618992)<BR>

d88adm 20100810194804 : /EHP4/EHPI/abap/exe/tp pf=/EHP4/EHPI/abap/bin/PCMDIMP.TPP addtobuffer SAPK-60405ININSURANC buffer=PCMDIMP.BUF u126 (pid=618994)<BR>

d88adm 20100810194805 : /EHP4/EHPI/abap/exe/tp pf=/EHP4/EHPI/abap/bin/PCMDIMP.TPP setsyncmark SAPK-60405ININSURANC buffer=PCMDIMP.BUF (pid=438448)<BR>

d88adm 20100810194806 : /EHP4/EHPI/abap/exe/tp pf=/EHP4/EHPI/abap/bin/PCMDIMP.TPP addtobuffer SAPK-60405INISM buffer=PCMDIMP.BUF u126 (pid=618996)<BR>

d88adm 20100810194806 : /EHP4/EHPI/abap/exe/tp pf=/EHP4/EHPI/abap/bin/PCMDIMP.TPP setsyncmark SAPK-60405INISM buffer=PCMDIMP.BUF (pid=438450)<BR>

d88adm 20100810194807 : /EHP4/EHPI/abap/exe/tp pf=/EHP4/EHPI/abap/bin/PCMDIMP.TPP addtobuffer SAPK-60405INISPSCA buffer=PCMDIMP.BUF u126 (pid=618998)<BR>

d88adm 20100810194807 : /EHP4/EHPI/abap/exe/tp pf=/EHP4/EHPI/abap/bin/PCMDIMP.TPP setsyncmark SAPK-60405INISPSCA buffer=PCMDIMP.BUF (pid=688318)<BR>

d88adm 20100810194809 : /EHP4/EHPI/abap/exe/tp pf=/EHP4/EHPI/abap/bin/PCMDIMP.TPP addtobuffer SAPK-60405INISUT buffer=PCMDIMP.BUF u126 (pid=619000)<BR>

d88adm 20100810194809 : /EHP4/EHPI/abap/exe/tp pf=/EHP4/EHPI/abap/bin/PCMDIMP.TPP setsyncmark SAPK-60405INISUT buffer=PCMDIMP.BUF (pid=619002)<BR>

d88adm 20100810194810 : /EHP4/EHPI/abap/exe/tp pf=/EHP4/EHPI/abap/bin/PCMDIMP.TPP addtobuffer SAPK-60405INISCWM buffer=PCMDIMP.BUF u126 (pid=619004)<BR>

d88adm 20100810194810 : /EHP4/EHPI/abap/exe/tp pf=/EHP4/EHPI/abap/bin/PCMDIMP.TPP setsyncmark SAPK-60405INISCWM buffer=PCMDIMP.BUF (pid=688320)<BR>

d88adm 20100810194812 : /EHP4/EHPI/abap/exe/tp pf=/EHP4/EHPI/abap/bin/PCMDIMP.TPP cmd all D88 (pid=688322)<BR>

1. Phase JOB_RDDIT020:<BR>

2. Phase IS_SYNC_20:<BR>

3. Phase CONFLICT_CHECK:<BR>

<BR>

<BR>

ritussdb:d88adm 16> tail -10 SAPehpichk.log<BR>

<BR>

CURRENTPHASE PREP_EXTENSION/IS_SYNC_20<BR>

...started at 20100810195737<BR>

1. Using phase log file 'ISSYNC20.LOG'.<BR>

..times self: 0.010000/0.010000 usr/sys, children 0.000000/0.000000 usr/sys.<BR>

..finished at 20100810195737 with status SUCCEEDED.<BR>

<BR>

CURRENTPHASE PREP_EXTENSION/CONFLICT_CHECK<BR>

...started at 20100810195737<BR>

1. Using phase log file 'CONFLCHK.LOG'.<BR>

<BR>

<BR>

ritussdb:d88adm 17> tail -10 CONFLCHK.LOG<BR>

3 ETQ399 "SAPKE60408","226","CSP","SAP_HR","604","SP 08 for SAP_HR 604","01"<BR>

3 ETQ399 "SAPK-60408INEAHR","227","CSP","EA-HR","604","SP 08 for EA-HR 604","01"<BR>

3 ETQ399 "SAPKE60409","228","CSP","SAP_HR","604","SP 09 for SAP_HR 604","01"<BR>

3 ETQ399 "SAPK-60409INEAHR","229","CSP","EA-HR","604","SP 09 for EA-HR 604","01"<BR>

3 ETQ399 "SAPKE60410","230","CSP","SAP_HR","604","SP 10 for SAP_HR 604","01"<BR>

3 ETQ399 "SAPK-60410INEAHR","231","CSP","EA-HR","604","SP 10 for EA-HR 604","01"<BR>

3 ETQ399 "SAPKE60411","232","CSP","SAP_HR","604","SP 11 for SAP_HR 604","01"<BR>

3 ETQ399 "SAPK-60411INEAHR","233","CSP","EA-HR","604","SP 11 for EA-HR 604","01"<BR>

3 ETQ399 "SAPKE60412","234","CSP","SAP_HR","604","SP 12 for SAP_HR 604","01"<BR>

3 ETQ399 "SAPK-60412INEAHR","235","CSP","EA-HR","604","SP 12 for EA-HR 604","01"<BR>

Edited by: Roche SAP Support IBM on Aug 10, 2010 3:18 PM

[Former Member]

<BR>

Yes, there were no updates to the installation directory at all during this period.<BR>

<BR>

We raised a message with SAP requesting for their assistance. However, during the conversation with them, the installation came out of the phase and went on. My only guess is that we just need to be more patient with the installation at this point. <BR>

<BR>

One key reason we were so anxious in this phase was we had a previous phase which had encountered an error due to a corrupted media package, the installation ran in circles instead of error out. This error had caused us 24 hours in our project timeline. <BR>.

<BR> In any case, thanks for the advise.

Edited by: Roche SAP Support IBM on Aug 12, 2010 3:15 AM

[Former Member]

Hello Roche,

Could you tell me roughly how long you had to wait? I have exactly the same issue here, if you tell me then I know wat I'm looking at..

Thanks

Update: Roughly 1,5 hours later without any sign of activity the process continues over here.

Edited by: Martin Loohuizen on Aug 13, 2010 1:34 PM

[Former Member]

Hi <BR>

<BR>

Sorry for the late reply<BR>

<BR>

We waited for about 2.5 hours, on a AIX box with 1 physical CPU and 12 GB of memory.<BR>

[Former Member]

Thanks! Guess this is normal with this step.

[Former Member]

Hi,

I have waited for 3 hours and no sign of activities.

Machine is T5120 64cores 32GB RAM.

Has anybody waited more than 3 hours? Or anybody get faster runtime by restartting the phase?

Thank you.

[Former Member]

Hi,

Wow, after waiting desperately for 4 hours, that CONFLICT_CHECK step is finally passed.

SAP should logs more activities during that step, to make us know what is going on.

Thank you

[Former Member]

Hi all,

CONFLICT_CHECK step phase takes long time in  EHP5 upgrade also, this phase really tests our patience, did any one implemented any best practices to improve this phase or did any one received any recommendations from SAP to improve this phase?

If you have any tips to improve this phase please share.

Thanks in advance.

Sree

[former_member208623]

Hi,

update statistics of table OCSCMPLOBJ may help, as this table is initial filled during the upgrade and accessed within phase CONFLICT_CHECK.

Regards, Christoph

[Former Member]

Just for curiosity - conflict check could take more than 10 hours:

:

1 ETQ201 Entering upgrade-phase "PREP_EXTENSION/CONFLICT_CHECK" ("20160629135640")

1 ETQ202 Upgrade phase "CONFLICT_CHECK" completed successfully ("20160630004919")

:

No sign of activity in logs what so ever.

Just like in other long running SUM tasks - either monitor on DB level, or watch processes on OS:

If ora<sid> (for Oracle DB) is consuming a lot of CPU power, it's in progress (use top or glance commands on UX).

The speed is more dependent on the DB health than on the power of HW.

[paul_power]

Dear Roche,

Check what the contents of the latest file updated in <ehpi dir>/tmp is this will be what the ehpi is currently doing.

If their still is no update under <ehpi dir>/log or <ehpi dir>/tmp I would recommend to stop the current phase. Close the ehpi gui, restart the server to clear any shared memory and then restart the ehpi and repeat the phase. Check if it still hangs.

Regards,

Paul