- Logfiles: how to find them, how to check them.
- How can I tell SUM if I have changed the DDIC password?
- What is a Vendor Key ?
- How can I identify all objects that have activation error?
- Accept non-severe errors option: What is the meaning and what can be the consequences of selecting it?
- How to handle modifications by SPDD and SPAU during the Update/Upgrade?
- How to reset an update from SUM SP13 onwards and new UI
- How to reset an update when you are in Preprocessing roadmap with SUM using SL Controller
- How to reset an update when you are in Execution roadmap
- I have already passed the DOWNCONF_DTTRANS_BCK phase, is it possible to reset an upgrade if I forgot to backup the upgrade directory?
- I have to replace my SUM version during an upgrade. What are the necessary steps?
- I have just reset my update and now I want to use an older SUM version to run a new update
- How to stop and start the instance during update manually
- How can I troubleshoot instance start-stop situations during update
- How can I identify and install the correct kernel for an application server instance during update?
- How can I start/stop the shadow instance manually during update?
- How can I implement SAP notes during an update? Can I use SNOTE transaction?
- Can I call SAup processes manually when other is running?
- How can I check on which release and SP level a transport request was released?
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.
- Stop the Software Update Manager by choosing Update Stop Update from the main menu of the GUI.
- Choose -> ABAP -> Start With Options from the menu.
- 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)
- Restart the Software Update Manager.
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.
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).
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:
Further details can be found in the SAP KBA 1993236 - Implementing SAP note corrections during Upgrade Downtime
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:
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.