Quantcast
Channel: SCN : All Content - Security
Viewing all articles
Browse latest Browse all 2858

Some hints for a smooth transition reg. SU25|upgrade to >=7.31

$
0
0

To avoid dataloss, unexpected results, some actions have to be performed as preparation already before starting the upgrade.

 

Before the Upgrade:

 

  • First repair any inconsistent data still in the old release: Use report SU24_AUTO_REPAIR with all available options (documentation can be found in SAP note 1539556).
  • Initialize timestamps with report SU25_INITIALIZE_TSTMP (SAP note 1599128)
  • Create a backup transport of SU24 data after each step (you can use SU25, step 3 for that creation of the transport) and export it
  • Create a backup transport of your roles and export it

 

 

Now after the Upgrade:

 

Apply all notes listed in note 440231. This note is kept actual with the latest notes.

 

Run SU25 2a-2c, alternatively you can use also the expert mode combining 2a and 2b by starting SU24->button 'Default Values Comparison'. As of 7.40 this expert mode is included in the SU25 action-list after step 2b.

 

If everything is fine, create a final transport in step 3 of SU25 and transport the new proposals through your system landscape.

Then transport your already adapted roles as well.

 

 

Update June 19th, 2013:

If you have missed the first step of  'Before the Upgrade' (SU24_AUTO_REPAIR ->Repair Modification flags), note #1850378 provides a correction which corrects at least the SU24-entries with incorrect modification flags. Missing modification flags cannot be repaired anymore at this moment, as the old SU22-content before Upgrade is required to repair the missing ones.



Viewing all articles
Browse latest Browse all 2858

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>