Skip to end of metadata
Go to start of metadata
 

 Contents

 

How can I tell SUM if I have changed the DDIC password?

This is described in the SUM guide Chapter Changing the DDIC Password 

In the PROFREAD phase, you enter the DDIC password. It is not usually necessary to change the password of the user DDIC later.
After the installation of the shadow system, the password of user DDIC in client 000 is the same as on the original system.
However, if you want to change the password after the PROFREAD phase, you have to change it in the system as well as in the Software Update Manager parameter.
The passwords in the original system and in the shadow system have to be identical with the passwords known by the Software Update Manager.
The procedure below describes how you can change the parameter in the Software Update Manager.

  1. Stop the Software Update Manager by choosing Update Stop Update from the main menu of the GUI.
  2. Choose -> ABAP -> Start With Options from the menu.
  3. To make the new password of user DDIC known to the Software Update Manager, enter the command:
    set DDICpwd (original system)
    set shdDDICpwd (shadow system)
  4. Restart the Software Update Manager.

Back to top

Do I need to uninstall additional application server instances before update?

Uninstalling additional application server instances is only requested in exceptional cases. The SUM guide SP13 describes these specific cases:

Release upgrade only and for heterogeneous systems, that is, which have different operating systems on the primary and additional application server instances, you have to uninstall the additional application server instances before you start the upgrade procedure. 

Release upgrade only and if you are upgrading from a source release based on SAP NetWeaver 2004 and you have additional application server instances, back them up in case a system restore is required and then uninstall them.
To uninstall the additional application server instances, proceed as described in the installation guide for your source release. If you want to use the profiles of the additional application server instances to adapt the profiles of the target system, save them before you uninstall the additional application server instances.

Back to top

Can I apply higher SP to only some of the components on my NetWeaver system?

Software Update Manager allows you to update the whole system to a higher support package stack using a stack xml file generated in SAP Solution Manager's Maintenance optimizer system - MOPZ. You can also update one or more software components to a higher patch(not support package) level using transaction SPAM for ABAP stack and  'Manually prepared directory' option for JAVA stack (See SAP note 1641062 for more information).

Back to top

How can I implement SAP notes during an update? Can I use SNOTE transaction?

During SUM execution the implementation of SAP Notes with transaction SNote is disabled so as not to corrupt the system state.

To make the implementation of changes to SAP objects easier, SNote has been enabled during the following update phases:

  • XPRAS_AIMMRG
  • XPRAS_UPG
  • XPRAS_AIMMRG_CUST
  • XPRAS_UPG_CUST 

Further details can be found in the SAP KBA  1993236 - Implementing SAP note corrections during Upgrade Downtime

Back to top


Why creates SUM another instance under  /usr/sap/<SID>  directory during update downtime in dual-stack updates?

In dual-stack updates  (e.g Solution manager) SUM JAVA and ABAP updates are running parallel.
During downtime SUM uses the original instance number for JAVA part update and the instance number of the shadow instance for the ABAP part update.
During downtime phases one can see two instances under /usr/sap/<SID> directory:

/usr/sap/SID/DEVBMGS<orig inst.nr>
/usr/sap/SID/DEVBMGS<shadow inst.nr> 

The instance role of the second instance is "Standard instance". You can read more about the earlier running shadow instance here.

 

Back to top

Can I call SAup processes manually when other is running?

You should take care that you do not have a previous SAPup running before starting another one manually, you can see more information in 2250487 SAP KBA.

 

Back to top


  • No labels