cancel
Showing results for 
Search instead for 
Did you mean: 

SAP BW 7.5 SPS04 Upgrade via sum sp17 pl10 error during the Execution phase MAIN_SWITCH/UVERS_UP_B!

Former Member
0 Kudos

I am currently running the BW 7.5 SPS upgrade in the execution phase, during the start of the downtime I am getting an error message that Severe error(s) occurred in phase MAIN_SWITCH/UVERS_UP_B!

  • according to phases.log file, it looks like there are incorrect status information for some components in the table upgrade versioning table “UVERS”:

  • Looks like the status has not been set correctly by the upgrade process during the upgrade of the components!?I had also attached the screen of the phase logs highlighted the error.

    When I had verified the entries to the table UVERS its was showing the current status as "T" How should we proceed further in fixing the issue.

  • Could you help me further ,how should we proceed I had attached the SUM error logs.


    Last error code set: Found 9 Invalid upgrade statistics.

    CURRENTPHASE MAIN_SWITCH/UVERS_UP_B
    ...started at 20161013074548
    ..finished at 20161013074548 with status ABORTED.
    # Error message set: 'Found 9 Invalid upgrade stati'
    ...begin dialog at 20161013074551
    ...end dialog at 20161013075417
    ..answered at 20161013075417.
    -> decided to cancel phase execution.
    # Finished execution of 29/93 phases with rc=3.
    # ==========================================================================

    Current unit is 'EXECUTE', next unit is 'EXECUTE'.
    -> decided to continue with unit EXECUTE.
    # Executing module 'MAIN_SWITCH'.

    # BEGIN MAIN MODULE Downtime I: Switch tables and Kernel

    Starting phase execution with maxpar = 6, scheduled: 64x'-'

    CURRENTPHASE MAIN_SWITCH/UVERS_UP_B
    ...started at 20161013083048
    ..finished at 20161013083049 with status ABORTED.
    # Error message set: 'Found 9 Invalid upgrade stati'
    ...begin dialog at 20161013083053
    ...end dialog at 20161013091609
    ..answered at 20161013091609.
    -> decided to cancel phase execution.
    # Finished execution of 0/64 phases with rc=3.
    # ==========================================================================

    Current unit is 'EXECUTE', next unit is 'EXECUTE'.
    -> decided to continue with unit EXECUTE.
    # Executing module 'MAIN_SWITCH'.

    # BEGIN MAIN MODULE Downtime I: Switch tables and Kernel

    # Starting phase execution with maxpar = 6, scheduled: 64x'-'

    CURRENTPHASE MAIN_SWITCH/UVERS_UP_B
    ...started at 20161013091807
    ..finished at 20161013091808 with status ABORTED.
    # Error message set: 'Found 9 Invalid upgrade stati'
    ...begin dialog at 20161013091812
    ...end dialog at 20161013092128
    ..answered at 20161013092128.
    -> decided to cancel phase execution.
    # Finished execution of 0/64 phases with rc=3.
    # ==========================================================================

    Current unit is 'EXECUTE', next unit is 'EXECUTE'.
    -> decided to continue with unit EXECUTE.
    # Executing module 'MAIN_SWITCH'.

    # BEGIN MAIN MODULE Downtime I: Switch tables and Kernel

    # Starting phase execution with maxpar = 6, scheduled: 64x'-'

    CURRENTPHASE MAIN_SWITCH/UVERS_UP_B
    ...started at 20161013092136
    ..finished at 20161013092136 with status ABORTED.
    # Error message set: 'Found 9 Invalid upgrade stati'
    ...begin dialog at 20161013092141

    Regards,
    Ranganath Sripathy

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hello Roland,

Thank you for your update, the BW system was created as a copy from the production which was on NW 7.0 and later I had upgraded it to NW 7.5 SPS03 and now I had tried to perform the SPS04 Upgrade to the same system, but this where we are experiencing the issue currently our project is stopped since we had planned to update the Sandbox to SAP HANA system and then start with the SPS04 upgrade.Currently the production system is running on SAP HANA DB.

Regards,

Ranganath Sripathy

RolandKramer
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

As you might already saw in your response of the Incidents the UVERS value "T" is not correct, rather then "P".

Resetting an Upgrade must be done properly before running the technical Process again

Note 1790486- SAP_ABA is in an undefined state that is not safe to be upgraded

Was the System created by a systemcopy or migration first?

Best Regards Roland

Former Member
0 Kudos

Hello Mark,

Thanks,I have already done it and since I am using the latest version of the SUM SPS10 ,its giving us lot of issues especially related to the tables and so on I already opened the message with SAP and they have requested to reset the upgrade since they have found some inconsistencies with it as per their suggestion I dropped an table object REPOSRC~0 which already exist during the old upgrade.

After which I had some sql errors coming up on the system, whenever I execute any reports on the SAP as per the suggestion from SAP I restored the DB and the error with the report generation stopped but the error continued with the upgrade, but now SAP says its inconsistent now and the reset is the only option and to go forward and also they suggested to use the Latest release of the SUM SPS18.

Regards,

Ranganath Sripathy

former_member93896
Active Contributor
0 Kudos

Ranganath

Please create an incident report so SAP support can analyze the issue (see http://support.sap.com/incident).

Regards,
Marc
Product Management SAP EDW (BW/HANA)