Skip to Content
author's profile photo Former Member
Former Member

what does the downtime part really do in an upgrade?

hi experts

when there is a system upgrade i understand that all the modifications happen on the shadow instance. then the downtime part starts, what does it really do with the modified data of the shadow instance? what happens with the repository objects that are stored on the ~ tables? at which point the shadow is deinstalled?

appreciate if someone helps.

br

JK

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Aug 26, 2013 at 11:26 AM

    This means the ~ tables will be renamed back to their original names during the downtime?

    If I log on the shado instance which version I will see on the objects? the source or the destination?

    the kernel on the shadow instance is the same as on the source? the kernel switches to the new one in downtime. So how can the source kernel execute commands on the source tables? if i have a 640 system the shadow instance will have also the 640 kernel, but its objects will be on the 730 version. how can a r3trans possible work on this case? what is the value of table SVERS~ on the shadow?

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Tomas Black

      hi thomas

      yes i got that by reading lots of notes and guides the last weeks. we had an error in shadow with the source kernel and found out the new kernel was not copied. our last upgrade was with r3up tool way ago 😊

      thanks for the helpful support of you all

      JK

  • Posted on Aug 23, 2013 at 01:29 PM

    Hi Julius,

    The downtime phases are where the system switches over to actually using the target tables and target release kernel. the previous phases were setting these up but the system was still running on the source release. Downtime is needed to switch oer so the system is acutally running on target kernel and release.

    You can use downtime minimised and almost zero-downtime appraoches to reduce the amount of time the system is not available to users.

    http://scn.sap.com/docs/DOC-32544

    The shadow tables are both changed tables and new tab les being brought in with the target release, once the system switch and repositroy switch occurs, then these become the "real" tables that the system is using.

    Before starting downtime phase, it is always recommended to take full offline DB backup and EHPI upgrade directory backup. So, that if something goes wrong during downtime phase or after downtime phase, you can restore DB and EHPI/ Upgrade directory. And then later on you can again start upgrade right before the downtime phase.

    In case, you still want to reset Upgrade /EHPi upgrade then you have to drop shadow instance schema manually from the database.

    It is cleaned up as part of the post processing when the upgrade runs correctly.

    Hope this information helps.

    Best regards,

    Paul

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 25, 2013 at 07:02 PM

    Hello

    when there is a system upgrade i understand that all the modifications happen on the shadow instance. then the downtime part starts, what does it really do with the modified data of the shadow instance.

    The shadow system is created with the help of DBCLONE jobs and upgraded with the Technical components and Kernel of the target release based on the stack file. During the downtime the upgrade tool does a switch of the shadow system to the main system with the target release components and kernel. The repository switch is done at phase EU_SWITCH and kernel switch is done at KX_SWITCH. In simple words the shadow will take the role of the main system.

    what happens with the repository objects that are stored on the ~ tables?

    They will get upgraded with newer functionality.

    If you have any modifications then they will lost unless you perform the SPDD phase in the shadow system to retain your modifications.

    The upgrade will bring in newer database objects and transactions based on the new release to the database and there will be aliases created.

    The shadow system works on the new version of the objects with the help of these aliases.

    http://help.sap.com/saphelp_nw04/helpdata/en/35/26b4f0afab52b9e10000009b38f974/content.htm

    at which point the shadow is deinstalled?

    Once the downtime (switch) completes.

    There will be left overs at the file system level (logs and kernel files) but they are not useful anymore.

    Regards

    RB

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.