Upgrade to BW 7.31 SP08 - Error in phase "Execution"

[former_member286544]

Hi experts,

i posted this Question already in Netweaver BW Space:

We want to upgrade our BW-System from 7.00 to 7.31 (we are also using the SEM-AddOn, so we have to upgrade this addon from 600 to 736). During the phase "Execution" in SUM, the error occurred: "Batchjob Enhupgphase aborted". It is not possible to continue the Upgrade, so the whole project is currently interrupted.

In the run ( in XPRASUPG ) occured another error, but we were able to solve this one. Considering note 644610 we created a special RFC-Connection to client 100 and restarted the SUM with option "Accept Non severe errors".

In the attached document can be found some screenshots.

Is there any idea, to solve this issue?

Best regards

Daniel Oppermann

log.txt.zip

[Former Member · Accepted solution]

Hello All

he mentioned Log Writer failed, The issue is after the system was restarted the DIR_PUT directory got set to default /usr/sap/put. You need to change this entry to point to the abap directory under SUM

example /usr/sap/XXX/SUM/abap

Then restart SUM and the SAP and all should work

[former_member286544 · Accepted solution]

Hi James,

thank you, for your correct answer. Issue is solved.

best regards

Daniel

[RolandKramer · Accepted solution]

Hell James,

I documented this also here - SAP First Guidance - Using the DMO Option to Mi... | SCN - Page 20

Best Regards Roland

SAP BW? - three things to know ...

[Former Member]

Hello Daniel,

Have you raised it with SAP ? It could be anything from a bug to the fact that you accepted non-severe errors in XPRA_AIMMRG phase (though chances of that are really less but there is different solution that accepting non-severe errors if you got the error which I am thinking you got).

Re-run this phase and then when you get the error just check at OS level for the all files with the time stamp near to error time and publish them here.

Regards,

Ruchit

[Reagan]

Hello

Check this discussion:

http://scn.sap.com/message/7416850

Regards

RB

[Former Member]

Hi,

Please check the below note.

Note 1608181 - Error in phase MAIN_POSTP/RUN_ENHUPGPHASE

Thanks

Rishi abrol

[former_member286544]

Hi Rishi,

thanks for reply.

Note 1608181 is not the solution, the report is already repaired in SP08, i checked the ABAP-Coding.

regards

Daniel

[former_member188883]

Hi Daniel,

Could you check database logs for the error message you getting. It looks like some issue with database log writer.

Either the log partition is full or something.

Hope this helps.

Regards,

Deepak Kori

[Former Member]

Hi ,

Can you try to enable trace in the shadow instance and check the background work process trace for that particular process.

or enable trace in st05 and see where is it failing.

Because from the logs it not much error.

Thanks

Rishi abrol

[Former Member]

Hi,

can you also try to run transaction SPAU and see its not throwing any error (dont change any thing) as this phase is trying to run SPAU and Starting of Prepare enhancements for SPAU in batch.

Thanks

Rishi Abrol

[Former Member]

and which could be related to this

Implement note 1720495 before you start transaction SPAU

Make sure to implement SAP note 1720495 immediately after a Support Package import, an enhancement package installation, or an upgrade and before making any adjustments in transaction SPAU.

Otherwise you can observe after an EHP installation or a Support package import notes with status 'SAP note <no.> obsolete; de-implementation necessary' in transaction SPAU, when adjusting the note, and in the Snote. If you proceed in transaction SPAU and adjust this kind of notes, the de-implementation of the note can destroy the code of the support package and can make the system inconsistent.

The SAP note 1720495 corrects the status of the notes and avoids wrong deimplementation of obsolete notes.

as mentioned in Note 1790828 - Central Note - Software Update Manager 1.0 SP08 [lmt_004]

Thanks

Rishi abrol

[former_member286544]

Hi,

thanks for your hints!

@Deepak Kori: we checked the database logs, but found no errors.

@Rishi abrol: The shadow instance does not exist anymore. We tried to implement Note 1720495, but this note is already delivered with SP 08. And SP08 is our target release.

Best regards

Daniel

[Former Member]

Hi Daniel,

As per your Systems SM37 and SM21 logs it shows error " Log writer aborted with RC 1: Message no TG154".

And you have already replied that SAP Note 1608181 is already implemented in the system. If there are no other error logs found or getting generated if you repeat the phase then please check the space and directories at OS level. Is there any possibility of directories/files being moved/deleted or space full or authorization issue on SUM directory?

If everything is good at OS level then please check/provide the relevant phase log also.

Thanks,

MP Singh