DISP+WORK used SUM profile and not instance profile

[Former Member]

Hello All;

I am dpplying EHP3 on crm system production, I am just finish with Check Phase,

The disp+work has stop on this installation. I see in the trac log file

The disp+work used SUM profile file and not system profile file.

Trace from disp+Work looking like that

trc file: "dev_disp", trc level: 1, release: "741"
---------------------------------------------------
sysno      02
sid        PJ1
systemid   562 (PC with Windows NT)
relno      7410
patchlevel 0
patchno    26
intno      20020600
make       multithreaded, Unicode, 64 bit, optimized
profile    F:\Reeje\SUM\abap\PJ1\SYS\profile\PJ1_DVEBMGS02_dkrdssap342
pid        13952

BUt that should look like this

and not on trc file: "dev_disp", trc level: 1, release: "720"

---------------------------------------------------
sysno      01
sid        PJ1
systemid   562 (PC with Windows NT)
relno      7200
patchlevel 0
patchno    300
intno      20020600
make       multithreaded, Unicode, 64 bit, optimized
profile    \\SAPPJ1\sapmnt\PJ1\SYS\profile\PJ1_D01_dkrdssap342
pid        5780

Any idea why this happing?

Thanks for any help.

Reza

[Reagan · Accepted solution]

Hello Reza

The one used by the SUM tool is for the shadow system and the other one is the main system.

You can see the difference in the system numbers.

In what phase are you now in the EHP installation ?

Regards

RB

[Former Member · Accepted solution]

Hello Reagan,

I am just finish with Check Phase. But I can see the disp+Work is stopet:

And on developer trace I have :

---------------------------------------------------

trc file: "dev_disp", trc level: 1, release: "741"

---------------------------------------------------

sysno      02

sid        PJ1

systemid   562 (PC with Windows NT)

relno      7410

patchlevel 0

patchno    26

intno      20020600

make multithreaded, Unicode, 64 bit, optimized

profile    F:\Reeje\SUM\abap\PJ1\SYS\profile\PJ1_DVEBMGS02_dkrdssap342

pid        5320

　

Mon Jul 07 13:30:24 2014

kernel runs with dp version 203000(ext=117000) (@(#) DPLIB-INT-VERSION-203000-UC)

length of sys_adm_ext is 500 bytes

.

.

.

.

Any idea why disp+work used shadow profile file?

Should I reset upgrade?

Thanks

[Reagan · Accepted solution]

Hello Reza

I can see that the PJ1 with the system number 02 is using kernel 741 and you are presently doing an EHP3 update for the CRM system.

EHP3 for CRM is based on Netweaver 7.4 release and it appears to me that there was an (failed) EHP3 installation performed on this system and the reset was not done correctly.

Is this the case ?

If not then what is the system number of the PJ1 instance ?

Based on the profile path of F:\Reeje\SUM\abap\PJ1\SYS\profile\PJ1_DVEBMGS02_dkrdssap342 it looks to be a directory used for the upgrade.

I would check the dev_w0 trace file to know the reason why the system failed to start.

Regards

RB

[Former Member · Accepted solution]

Hello Reagan,

THE pj1 SYSTEM HAS SYSTEM NR.01. And right it should be problem with not correctly reset of EHP3.

If I reset this upgrade can the problem be solved?

This is production system.

Thanks

Reza

[Former Member · Accepted solution]

Hello Reagan,

Please correct me on it,

We are now on check phase in SUM, and in this phase the shodow instance is createt and the

dkrdssap342 2 is the shadow instance that was createt by sum.

The main instance is dkrdssap342 1 and that working.

So I think I got confused from one of my college in the case.

[Reagan · Accepted solution]

Reset the upgrade and delete the upgrade directory complete and start the upgrade with a newly extracted SUM and see if that helps.

[Former Member · Accepted solution]

I will do that,

Thanks again

[Reagan · Accepted solution]

Hello Reza

There is no shadow system during the check phase.

The shadow system will be created after the lock development phase.

Also what is the error you have on the SUM console ?

Regards

RB

[Former Member · Accepted solution]

Hello Reagan,

To dag I was finish with check phase  in SUM without any error, But in  SAPMMC we could see a new instance 02.

That is shadow instance. The  was create during upgrad.

But as you told this shadow instance should nte be create after check phase.

I will try to reset the upgrade and start over with a new SUM.

Thanks

Reza

[Reagan · Accepted solution]

Hello Reza

If the upgrade tool doesn't show any errors then do NOT reset the upgrade.

During an upgrade you need to depend on the SUM tool for error messages and not based on the SAP MMC console. If the upgrade tool doesn't throw any error for the upgrade then do not reset the upgrade.

Continue with the next phase.

The upgrade tool copies kernel and profiles for the shadow system creation. If there is no issue (like shadow system startup) then do not reset the upgrade.

I was under the impression that a previous upgrade was not reset and you started a new upgrade.

Regards

RB

[Former Member · Accepted solution]

Hell Reagan,

Thanks for reply,

The confusion is we have this dkrdssap342 02 on SAPMMC that is gray.

So I am not sure about this?!!

But there is no error om SUM.

[Reagan · Accepted solution]

Hello Reza

I am not sure at which stage the tool creates an entry in the SAP MMC but the shadow will be started only after the DBCLONE jobs are completed successfully. So if you are not facing any issues or errors on the SUM tool then do no interrupt the upgrade.

Regards

RB

[Former Member · Accepted solution]

Thanks for advice.

Thanks

Reza