Central Note Software Update Manager

2197897 – Central Note – Software Update Manager 1.0

Symptom

Errors in the update process; preparations for the update; additional information to the update guides

Other Terms

Enhancement package installation, Software Update Manager, SUM, EHP, update, upgrade, Support Package Stack application, SPS update, additional technical usage, maintenance

Reason and Prerequisites

This SAP Note applies to Software Update Manager 1.0 SP16.  The Software Update Manager (SUM) is the tool for various system maintenance procedures such as:

  • Release upgrades (major release change)
  • System updates (EHP installation)
  • Support Packages (SPs) / Support Package Stacks applications
  • Java patches applications
  • Corrections of installed software information
  • Conversion of SAP systems to SAP S/4HANA

 In addition it offers the following options and features:

  • DMO: Database Migration Option (system update combined with database migration to SAP HANA)
  • ZDO: Zero Downtime Option (upgrades without a technical downtime and with a minimized business downtime)
  • nZDM: near-Zero Downtime Maintenance (includes features to minimize Business Downtime)
  • Benchmarking Tool
  • Table Comparison
  • Customer Releases

You can find more about SAP System Maintenance on the SAP Community Network at: http://scn.sap.com/docs/DOC-28354. The SCN document also includes a reference to an introduction into the SUM tool.

A graphical representation of the update and upgrade paths, which are currently supported by SUM, is attached to this SAP Note.

Solution

This is the central SAP Note for Software Update Manager 1.0 SP16.

CAUTION:

This SAP Note is updated regularly!

Therefore, read it again immediately before starting the tool.

Contents

Part A: Update SAP Notes and Keywords

Part B: SUM Version, Maintenance Strategy and Documentation

Part C: General Problems / Information

           I/…….Important General Information

           II/ …. Corrections to the Guide

           III/ ….Preparing the Update

           IV/….. Problems During the Update Phases

           V/ ….. Problems After the Update

Part D: Chronological Summary

Part A: Update SAP Notes and Keywords

Keyword for the “Confirm Target” roadmap step: 1729322

For more information about the update of your specific application, see the following SAP Notes:

SAP NetWeaver 7.5…………………………………2197259

SAP NetWeaver 7.4…………………………………1751237

SAP Solution Manager 7.1…………………………..1781833

SAP NetWeaver 7.3 EHP1…………………………….1609441

SAP NetWeaver 7.3…………………………………1390477

EHP1 for SAP NetWeaver 7.1…………………………1162299

ERP on HANA 1.0 – Release Information Note…………..1730095

CRM on HANA 1.0 – Release Information Note…………..1730098

SCM on HANA 1.0 – Release Information Note…………..1730175

SAP ERP 6.0 EHP8 – Release Information Note………… 2171334

SAP CRM 7.0 EHP4 – Release Information Note………… 2171335

SAP SCM 7.0 EHP4 – Release Information Note………… 2171392

SAP SRM 7.0 EHP4 – Release Information Note………… 2171391

SAP ERP 6.0 EHP 7 – Release Information Note…………1737650

SAP CRM 7.0 EHP 3 – Release Information Note…………1737725

SAP SCM 7.0 EHP 3 – Release Information Note…………1737723

SAP SRM 7.0 EHP 3 – Release Information Note…………1818517

SAP ERP 6.0 EHP 6:………………………………..1496212

SAP CRM 7.0 EHP 2:………………………………..1497032

SAP SCM 7.0 EHP 2:………………………………..1497083

SAP SRM 7.0 EHP 2:………………………………..1582094

In addition, you need the SAP Note for your database or operating system:

Operating system……………………………….Note number

_________________________________________________________________

IBM i …………………………………………..2233497

Database ……………………………………..SAP Note number

_________________________________________________________________

SAP MaxDB ……………………………………….2199034

IBM DB2 for Linux, UNIX and Windows ………………..2198641

IBM DB2 for z/OS …………………………………2200154

MS SQL Server ……………………………………2200892

Oracle ………………………………………….2197895

SAP ASE………………………………………….2197923

SAP HANA DB………………………………………2198407

IBM DB2 for i ……………………………………2233497

_________________________________________________________________

Part B: SUM Version, Maintenance Strategy and Documentation

SUM Version

This SAP Note applies to Software Update Manager 1.0 SP16.

Before you start the update, check if there is a newer tool version available. SAP recommends that you download the latest tool version as only this version contains the latest corrections and is updated regularly.

The Software Update Manager is available for download on the SAP Help Portal : http://help.sap.com/sltoolset -> System Maintenance.

Maintenance Strategy

The Software Update Manager 1.0 SP16 is currently in patch on request mode. That is, the Software Update Manager 1.0 SP16 is not recommended for use because it is not the latest version anymore. However, it can be downloaded on request, and patches are available on request as well.

The maintenance strategy for the Software Update Manager and the other tools delivered with SL Toolset 1.0 SP16 is described in the document attached to the SL Toolset 1.0 SPS16 Release Note 2164046.

Documentation

Before you start using the SUM tool, make sure that you have the latest version of the corresponding document, which is available on the SAP Help Portal : http://help.sap.com/sltoolset -> System Maintenance.

———————————————————————-

Part C: General Problems / Information

I/ Important General Information

  1. a) General

———————-< I030847 JULY/12/16 >—————————–

Verifying signed content in the stack.xml file

The Software Update Manager checks the authenticity of the software archives contained in the stack.xml, that is, it checks if the vendor is SAP. To check all archive types, yоu have to provide a Certificate Revocation List (CRL) file in the stack directory. During the Configuration roadmap step the components are scanned and verified, and any discrepancies are reported accordingly in the VERIFY-SIGNED-CONTENT.LOG.

———————–< I030847 UPDATE: MAY/17/2016 >—————————-

Updating systems running different OS on the primary AS and SCS instances

Switch-based release upgrade only: If your system is heterogenous, meaning that the primary application server instance and the SCS instance are running on different operating systems, you have to update the SAP Host Agent to the latest available version, and the SAP kernel to 7.20 patch level 68 and higher. You have to do this to both instances before the upgrade process. Also, later on during the procedure ensure that there is no SAP Host Agent present in your upgrade stack. You have to do these actions to prevent issues during the downtime of the upgrade.

——————-< Update D045929 MAR/03/2016 >——————–

Customer transport requests without stack.xml supported as of PL 02

If you want to import your customer transport requests only without performing a standard update procedure during an update or upgrade, you can the select the option that no stack configuration file is available.

This option is supported as of SUM SP 16 with patch level 02. If you use a lower SUM version, provide a stack.xml in any case to import your customer transport requests until further notice.

———————–< D023890 FEB/08/16 >————————–

Upgrade path SAP NW 6.40 to SAP NW 7.0, NW 7.01, and NW 7.02

Note that the Software Update Manager does not support the upgrade path from SAP NetWeaver 6.40 (and products on top) to SAP NetWeaver 7.0, 7.01, and 7.02.

  • Java: If you carry out a Java upgrade, you can request a SUM tool release via ticket on component BC-UPG-TLS-TLJ and with reference to this SAP Note.
  • ABAP: If you carry out an ABAP upgrade, you must use the fitting version of the SAPup tool.

———————–< D031330 FEB/05/16 >————————–

Conversion to S/4HANA, on-premise edition

If you carry out a conversion to S/4HANA, on-premise edition, using SUM SP16, consider also SAP Note 2269869.

———————–< D031330 FEB/05/16 >————————–

SAP NetWeaver versions: Release Restrictions and Limitations

Before the update, you must familiarize with the following important SAP Notes:

SAP NetWeaver 7.5:

  • 2197259 – Add. info about the update/upgrade to SAP NetWeaver 7.5
  • 2206460 – Release restrictions for SAP NetWeaver 7.5

SAP NetWeaver 7.4:

  • Note 1730102 – Release Restrictions for SAP NetWeaver 7.4
  • Note 1751237 – Add. info about the update/upgrade to SAP NetWeaver 7.4 (including service releases)

Note: Be aware that upgrade/update to SAP NetWeaver 7.4 is not supported for dual-stack NetWeaver systems. The only exception to this rule is SAP NetWeaver Process Integration on a traditional database system, which still requires a dual-stack implementation. For more information about the discontinuation of dual-stack deployments, see SAP Community Network at: http://scn.sap.com/docs/DOC-33703.

SAP NetWeaver 7.3 EHP1

  • Note 1522700 – Release Restrictions for SAP EHP1 for SAP NetWeaver 7.3

SAP NetWeaver 7.0 EHP3

  • Note 1557825 – Release Restrictions for EHP3 for SAP NetWeaver 7.0
  • Note 1637366 – Installation of SAP EHP3 for SAP NetWeaver 7.0
  • Note 1637629 – No Process Integration in SAP EHP3 FOR SAP NETWEAVER 7.0

SAP NetWeaver 7.3

  • Release Restrictions for SAP NetWeaver 7.3 – Note 1407532
  • SAP Business Suite PI Adapters for SAP NetWeaver PI 7.3 – Note 1570738

———————–< D023536 APR/01/15 >————————–

SAP Simple Finance add-on 2.0: Consider SAP Note 2150542

If you want to install, upgrade or update the SAP Simple Finance add-on 2.0 for SAP Business Suite powered by SAP HANA, pay attention to SAP Note 2150542 first.

—————< Update D023890 MAR/19/2015 >————————

——————–< I036200 DEC/13/2013 >—————————–

Solution Manager only: SPS update of ABAP or Java stack independently is supported

By default, you update the ABAP and Java part of the SAP Solution Manager in one step using the Software Update Manager (SUM). If you want to independently update the ABAP or Java stack of a dual-stack Solution Manager system to the latest SPS, use SUM for updating the Java stack and transaction SPAM/SAINT for updating the ABAP stack. SUM supports this scenario for the Java stack but requires a special command on startup.

Detailed information is available in the Release Information Notes for SP Stacks of SAP Solution Manager, which are listed in SAP Note 1595736.

———————–< I36200 JUL/26/2013 >————————–

Update of shared Wily AutoProbe connectors not supported

Performing updates in a system that uses a Wily AutoProbe connector shared with other systems is not supported. For example, if you have multiple systems on the same host, all systems use the same AutoProbe connectors, and you upgrade one of the systems, starting production operation of the remaining systems might fail.

———————–< D029945 16/JUN/15 >————————–

Selection of higher support packages in BIND_PATCH no longer possible for certain components

The option in phase BIND_PATCH to select higher Support Packages to those that have already been included in the stack.xml File, is no longer possible for all central components, that is, for SAP_BASIS, SAP_ABA, SAP_APPL, SAP_HR and SAP_BW. The reason is that this option may require a new kernel version, but the decision about a new kernel version has to be made before the BIND_PATCH phase

Update: As of SUM 1.0 SP13 patch level 02 and higher, it is possible again to select higher support packages for SAP_HR.

———————< D031178 MAY/17/2013 >————————–

SAP Business Suite Powered by SAP HANA: Release Restrictions and Limitations

Before the update, you must familiarize with the following important SAP Notes:

  • Note 1774566: SAP Business Suite Powered by SAP HANA – Restrictions
  • Note 1830894: Availability of SAP NetWeaver 7.4 on IBM i

Be aware that upgrade/update to SAP Business Suite 7 Innovation 2013 and higher is not supported for dual-stack SAP Business Suite systems. For more information, see SAP Note 1816819.

———————< D038245 MAR/25/2013 >————————–

SUM requires SAP kernel 7.20 or higher for target release

The Software Update Manager requires target release kernel 7.20 or higher for all platforms.

We recommend to always check before starting the update or upgrade whether there is a newer version of the SAP kernel available on SAP Service Marketplace and download it to the download directory.

Lower target release kernel versions are no no longer supported and may lead to an error during the update or upgrade.

———————–< D035496 APR/18/12 >————————–

Applying Support Package 02 to Solution Manager 7.1

When applying Support Package stack 02 to SolMan 7.1 with the Software Update Manager, an error occurs for component BI_CONT.

If you want to import Support Package queues that contain this Support Package stack, you either use the Support Package Manager (SPAM) or you include at least Support Package stack 05 as well.

———————–< I053650 DEC/19/11 >————————–

Java, ABAP+Java: Check for sapstartsrv Patch Level on the Source System

To guarantee that the Java or dual-stack SAP system can be correctly manipulated during the update/upgrade process, the Software Update Manager checks whether the patch level of SAP start service (sapstartsrv) on the source system is appropriate. This check is performed in the beginning of the SUM process so that known problems, related to system detection as well as proper stop and start of the SAP system, will be prevented. For more information, see SAP Note 1656036.

  1. b) ABAP

———————–< D029945 FEB/29/2016 >————————–

Non-Unicode not supported for SAP NW 7.5 and higher

Note that any path to a target system based on SAP NetWeaver 7.50 (such as SAP ERP 6.0 EHP 8) requires the source system to already be on Unicode. See also SAP Note 2033243.

—————– < D028310 MAR/24/2016 > ————————-

SUM ABAP SP16 in combination with nZDM: Consider SAP Note 2297511 !

It can occur under certain circumstances that SMIM objects (Information objects from the MIME repository) delivered by SAP might not be imported correctly. This is relevant if you meet the following conditions:

  • You use Software Update Manager 1.0 SP 16
  • The target release is SAP_BASIS 740 and higher
  • You run the Software Update Manager SUM with preconfiguration mode “Advanced”
  • You have chosen the feature “near-Zero Downtime Maintenance” (nZDM)

For any further details and how to avoid issues, see SAP Note 2297511.

—————– < D031330 FEB/12/2016 > ————————-

Zero Downtime Option (ZDO) of SUM available on request

The Software Update Manager (SUM) is equipped with the new feature zero downtime option (ZDO). With this option, you can run updates and upgrades of ABAP applications without a technical downtime and with a minimized business downtime. As of SUM 1.0 SP16, ZDO is part of the standard shipment and available on request, provided the necessary prerequisites are met. For more information, see SAP Note 2163060. The ZDO Guide is attached to this note.

  1. c) Java

———————–< D039661 OCT/28/2013 >————————–

Installing SAP Business Suite Usage Types on Top of an Existing SAP NetWeaver Java System

This installation scenario is described in the document SAP Solution Manager: Special Cases in Installation and Upgrade available at http://service.sap.com/mopz, section How-Tos and Guides. Follow the specific steps described in the chapter Add Installation of SAP Business Suite Usage Types to Existing NW System.

II/ Corrections to the Guide

  1. a) General

——————–<I043270 APR/20/2016>———————————–

Chapter “Configuring SAP Host Agent Authentication and SSL Connection” is optional.

It is only relevant if you perform a release upgrade and you do not have user credentials, but you want to use a certificate to authenticate in the system landscape.

  1. b) ABAP

/

  1. c) Java

/

———————————————————————–

III/ Preparing the Update

  1. a) General

————————-< D023536 MAR/29/16 >————————-

Solution Manager systems and BW systems only: Apply SAP Notes 2290149 and 2289603

If you want to install support package stacks or perform an upgrade for an SAP Solution Manager system or an SAP Business Warehouse system, apply the SAP Notes 2290149 and 2289603 beforehand.

——————–< Update D031330 JUN/29/16 >———————

————————-< D031330 FEB/26/16 >————————-

Configure SSL for the SAP Host Agent, if you use HTTPS

After you have installed or downloaded the latest SAP Host Agent, which is necessary among others for the use of the Software Update Manager with the SL Common UI, you must configure the secure socket layer (SSL) for the SAP Host Agent in case you want to use the Secure Hypertext Transmission Protocol (HTTPS) to start and restart the SUM. The procedure is described in the SAP Help Portal at http://help.sap.com -> Technology Platform -> SAP NetWeaver -> SAP NetWeaver <release> -> Application Help -> Function-Oriented View -> Solution Lifecycle Management -> SAP Host Agent -> SAP Host Agent Configuration -> SSL Configuration for the SAP Host Agent.

————————-< D023536 FEB/04/16 >————————-

Upgrade path NW 2004 or 730 to 740 SR2: Provide 7.42 kernel and latest DCK kernel in addition

If you run an upgrade to SAP NetWeaver 7.4 SR2 (= NW 7.4 SP8 or a higher support package) from SAP NW 2004 or SAP NW 7.3, procure the SAP Kernel 7.42 DVD. You will make known this kernel to the Software Update Manager during the upgrade procedure.

In case you want to use a newer, downward-compatible (DCK) kernel, procure this kernel in addition and place it in the download directory. The Software Update Manager will automatically use the latest kernel version from the download directory. The latest DCK kernel version is currently version 7.45.

————————-< I030847 UPDATED: JAN/15/16 >————————-

Install or Update SAP Host Agent to the minimum supported version

The SAP Host Agent is a tool for monitoring and controlling SAP instances and non-SAP instances, operating systems, and databases. As part of an SAP instance, the SAP Host Agent is automatically upgraded with the SAP kernel. However, it can also be installed and upgraded independently from an SAP instance.

Make sure that at least the relevant SAP Host Agent minimum version is present in your system. The minimum supported version is 7.21 version 3 (or higher).

We recommend  always using the latest version in the SAP Software Download Corner at http://service.sap.com/swdc. For additional information, such as the deprecation of lower versions, see SAP Note 2130510.

———————–< D001330 AUG/18/14 >————————–

Deactivate IOT feature for certain tables

The SUM tool does not support the (Oracle) IOT feature for certain tables because the SAP dictionary does not officially support the IOT feature. The tables are in DBDIFF exception table for index differences between DB and SAP dictionary. The solution or workaround is to deactivate the IOT feature for such tables before the SUM run. After finishing the SUM run, the IOT feature may be activated again.

Note that if the tables are not present in the dictionary, you do not need to disable the IOT feature.

———————–< D033486 OCT/14/10 >————————–

Apply SAP Note 1910464 before the import of certain SPs

If your system is on one of the following Support Package levels

SAPKB70029

SAPKB70114

SAPKB70214

SAPKB71017

SAPKB71112

SAPKB73010

SAPKB73109

SAPKB74004

and you want to import the next Support Packages, apply SAP Note 1910464 before the import.

——————–< D023890 OCT/13/2014 >—————————

No “Single System” mode on dual stack systems

On dual stack systems, do not use the preconfiguration mode “Single System”. Use preconfiguration mode “Standard” or “Advanced” instead.

In the case of a Solution Manager system, see also the comment “Solution Manager only: SPS update of ABAP or Java stack independently is supported” in section “I/ Important General Information” -> “a) General”.

———————< D035061 AUG/22/2012 >————————–

Implement note 1720495 before you start transaction SPAU or include the related Support Package

Make sure to implement SAP note 1720495 immediately after a Support Package import, an enhancement package installation, or an upgrade and before making any adjustments in transaction SPAU. Alternatively, you can include the related Support Package for your target release.

Otherwise you can observe after an EHP installation or a Support package import notes with status ‘SAP note <no.> obsolete; de-implementation necessary’ in transaction SPAU, when adjusting the note, and in the Snote. If you proceed in transaction SPAU and adjust this kind of notes, the de-implementation of the note can destroy the code of the support package and can make the system inconsistent.

The SAP note 1720495 corrects the status of the notes and avoids wrong deimplementation of obsolete notes.

———————< D035061 JUL/23/2012 >————————–

Check platform-specific requirements for the 7.20 EXT kernel

In case you want to install the 7.20 EXT kernel, or you want to change to this kernel, check beforhand the platform-specific requirements.

See SAP note 1553301 for the 7.20 EXT kernel requirements, especially section “Platform-Specific Information”.

If the requirements are not met, errors might occur in phase TOLVERSION_EXTRACT.

—————–< Update D035061 JAN/13/2016 >———————-

———————< D035061 JUL/23/2012 >————————–

Server Group SAP_DEFAULT_BTC must include Primary Application Server Instance

If you have defined a batch server group SAP_DEFAULT_BTC according to SAP Note 786412, make sure that the application server instance, which is used during downtime, is included in this server group. Otherwise it will not be possible to schedule the job RDDIMPDP correctly. The instance to be added is either the Primary Application Server Instance (this is the default case), or the instance created during shadow operation in case of dual stack systems updated in standard or advanced mode. The change must be active when entering the downtime at the latest.

———————–< D029385 MAR/08/11 >————————–

Upgrade on Windows only: Check registration of sapevents.dll

During the installation of your source release system, the installation procedure might have inadvertently registered the sapevents.dll from the central DIR_CT_RUN directory instead of from the local DIR_EXECUTABLE directories of the instance. This may lead to errors with locked kernel files during or after the upgrade. Therefore check the registration of sapevents.dll as described in SAP Note 1556113.

———————-< D053561 20/OCT/10 >—————————

Apply SAP Note to Avoid Error During Reset

We recommend to apply SAP Note 1518145 before starting the Software Update Manager (if it is not yet in your system as part of the corresponding Support Package). This note prevents an error that can occur when you reset the update procedure during the Preprocessing roadmap step. Without this note, some tables that need to be deleted during the reset cannot be deleted.

——————–< D033899 31/MAY/10 >—————————–

Preventing Errors with Table “SATC_MD_STEP”

To avoid problems during the update due to conflicting unique indexes, apply the correction described in SAP Note 1463168 or apply the corresponding Support Package.

  1. b) ABAP

———————< D035061 NOV/14/2014 >—————————

Enabled Data Aging and ICNV

In case you have enabled the Data Aging functionality to your data, related tables cannot be processed via incremental conversion (transaction ICNV). If those tables are excluded from ICNV during the update or upgrade due to this reason, an appropriate line will be added in the RUTNTICN.<SID> log file.

———————< D023536 OCT/21/2014 >—————————

De-implement SAP Note 1819126 before the upgrade or update

If you have implemented the SAP Note 1819126 in your system, you must de-implement it before you start the update or upgrade of your basis support packages to a support package that does not include this SAP Note. Otherwise a syntax error may occur in phase XPRAS_AIMMRG. Implement the SAP Note 1819126 again after the update or upgrade.

See SAP Note 2069772 for more information.

———————–< D035956 JUL/03/2014 >————————–

SFW activation: Prevent automatic activation of BC-Sets in all clients

In particular if table SFWPARAM contains an entry: NAME = ‘SBCSETS_ACTIVATE_IN_CLIENTS’ and VALUE = ‘X’, follow the steps described in SAP Note 2035728.

———————–< D024828 FEB/28/2014 >————————–

Consider SAP Note 1983758 while preparing the update

When you prepare the update/upgrade, consider SAP Note 1983758 to make sure that BW clients are not set wrongly by a previous update. Otherwise BW-specific error messages might occur during the follow-up activities.

———————–< D037517 DEC/13/2013 >————————–

Exclude Z languages

If you have installed your own languages (Z languages ) in the SAP system, you must exclude them from the upgrade or update process.

For this, you maintain the Z languages in the SAP system before the upgrade or update as follows:

  1. Logon to the SAP system
  2. Choose transaction SE16 and open table T002C
  3. Choose all Z language rows (max. Z1 – Z9) for editing
  4. Remove the “x” (if exists) from field “can be installed” (fieldname LAINST

——————–< D035061 FEB/12/2013 >—————————

Remove usages of customer-developed objects before you start SUM

The Software Update Manager applies the following security notes during the Extraction roadmap step by overwriting or deleting the related objects without further notice:

1668465, 1631124, 1631072, 1628606, 1584549, 1584548, 1555144, 1526853, 1514066, 1453164

If you have not installed those notes yet, check if any customer-developed objects make use of deleted or disabled objects and remove those usages before you start the Software Update Manager.

—————-< Update d023536 15/JUL/14 >————————–

——————–< D053561 13/DEC/12 >—————————–

See SAP Note 1413569 for table SMSCMAID

Before you start the Software Update Manager, check table SMSCMAID for duplicate records concerning field SCHEDULERID. Otherwise the upgrade might fail during downtime in phase PARCONV_UPG because a unique index cannot be created due to duplicate records in the table. See SAP Note 1413569 for more details.

——————–< D040050 19/SEP/12>—————————–

NTsystems: Install latest sapstartsrv before the update

If you use an NT-system with the <SID>ADM as domain user, make sure that you apply the SAP Note 1756703 before you start the update. Otherwise, if you enter during the update in phase PREP_PRE_CHECK/PROFREAD the <SID>ADM name and password as domain user, the phase PREP_INPUT/INSTANCELIST_PRE will not accept the <SID>ADM password, and the SUM stops.

———————– <D020214 30/MAY/11 >————————–

Preventing Errors Due to Unicode Length

A structure exists that uses a table type with a structure in at least

one component. When You call DDIF_FIELDINFO_GET, the system sometimes automatically selects the system Unicode length instead of the UCLEN

Unicode length that is specified in DDIF_FIELDINFO_GET. This can lead to an RFC error in phase PREP_INIT/SPAM_CHK_INI during the upgrade or update. To prevent this error, see SAP Note 1029444 and implement the attached correction instruction.

———————– <D003550 15/DEC/08 >————————–

Preventing Activation Errors

Under certain circumstances, information of runtime objects might get lost during the activation. This can lead to unwanted conversions of cluster tables. To prevent this error, see SAP Note 1283197 and implement the attached correction instruction.

  1. c) Java

———————-<I077286 29/APR/2013>—————————

Setting the instance profile parameter AutoStart to ‘0’

Before an upgrade, in each instance profile you must manually set the vaule of the AutoStart parameter to 0. This must be done for each application server instance. Proceed as follows:

  1. Log on to the instance.
  2. Navigate to the <drive>:\user\sap\<SID>\SYS\profile\ folder.
  3. Edit the <SID>_<Instance Name>_<host name> profile, and change the value of the AutoStart parameter to 0, that is,

AutoStart = 0

.This must be done to prevent unexpected start of instances, which might lead to connection errors.

———————-< I030727 21/SEP/2012 >————————

Upgrade from SAP NetWeaver 2004 to SAP NetWeaver 7.3 EHP1 Based PowerPC System on Linux: Update Your Instance Profile

Before starting an upgrade from SAP NetWeaver 2004 to SAP NetWeaver 7.3 EHP1 based PowerPC system on Linux, you need to add the following parameter to your instance profile:

jstartup/native_stack_size = 2097152

———————-< I035760 30/JAN/09 >—————————-

Cleaning Up the Profile Directory

Before starting the Software Update Manager, you need to clean up the profile directory. Remove any old, unused profiles and move any backup copies to another directory. The profile directory must only contain active profile files. By default, it is located in the central file share:

For UNIX: /sapmnt/<SAPSID>

For Windows: <Drive>:\usr\sap\<SAPSID>\SYS

For IBM i: /sapmnt/<SID>

———————————————————————–

IV/ Problems During the Update Roadmap Steps

This section addresses known problems that cannot be avoided using preventive measures. These problems will only occur under very specific circumstances.

  1. a) General

————————< D045929 09/DEC/2016 >————————————

Customer transport requests without stack.xml

If SUM stops in the phase REPACHK_EHPI with code 5 key QUEUE_FILE_NOT_FOUND, proceed with the following steps:

Activate the objects or remove the inactive versions and subsequently release the repairs and transport orders to ensure that the procedure can continue. If the inactive objects cannot be found in the SAP system, follow the instruction in note 538167. Afterwards, repeat the phase.

————————< I042050 3/SEPT/2015 >————————————

Activation errors in ACT_UPG for SACMRT_RULES_MR during update to NW 7.50

During an update to SAP NetWeaver 7.50, you encounter in phase ACT_UPG activation errors relating to the DDL source SACMRT_RULES_MR.

You can ignore these errors. See SAP Note 1343951 for further details.

————————< I042050 3/SEPT/2015 >————————————

Correcting startup issues in release upgrade scenarios from SAP NetWeaver 2004 to SAP NetWeaver 7.0-based releases

During SUM startup, you might encounter an error similar to the following:

[Thr 1234] *** ERROR => Error extracting data.

Type check failed [FileSystemSe 123]

[Thr 1234] *** ERROR => Unable to open <Drive>:\usr\sap\$[SID:#required]\p\SUM\sdt\param\sumjava_connectivity [resolved as <Drive>:\usr\sap\KMC\p\SUM\sdt\param\sumjava_connectivity]

(-127: Unknown error) [SLPProxyHand 673]

To correct this issue, you have to add the SAP_LocalAdmin user group to the list of permitted parties for folders and files below the <Drive>:\usr\sap\ directory.

———————–< I069357 NOV/11/2013 >————————–

Correcting Issues with Resetting the Upgrade

After you have reset the upgrade and a new SUM run is started, after using the “Cleanup and start afresh” option the buttons “Next” and Back” on the SUM GUI might be inactive. Alternatively, SUM may crash after the reset procedure when selecting ‘Exit’ or ‘Cleanup and start afresh'”.

In this case, proceed as follows:

  • For the ABAP part of the upgrade: Check in the log-file SAPup.log whether the phase SAVELOGS_RESET is mentioned in the end, either as started or skipped.
  • For the Java part of the upgrade: Check in the Java tab of the SUM GUI whether all steps have been completed.
  • Afterwards extract the SUM archive again to a new directory and start the new SUM run.

The above solution is valid when you reset the update by repeatedly choosing the “Back” button on the SUM GUI, or if you choose the Update -> Reset Update option.

——————< I077286 23/OCT/2013 >—————————-

Shadow instance reset during an upgrade

Linux- or Windows-based systems only: If during a switch upgrade you reset the SUM procedure after the SET_ENGINE_SAFE_MODE step has passed, afterwards SUM might stop at step “DELETE_SHADOW_DIR” with the following message:

Error while executing Task with input file FsoTasks.xml and task

DELETE_SHADOW_DIR. Could not finish Delete operation with parameters

file ”, directory ‘<drive:>/usr/sap/<SID>/SUM/sdt/<SID>’. Check whether the

current user has sufficient permission to execute this operation. Cannot

delete file <drive:>\usr\sap\<SID>\SUM\sdt\<SID>. Cannot delete

<drive:>\usr\sap\<SID>\SUM\sdt\<SID> using Windows console operation. 0

To correct this issue, proceed as follows:

  1. Stop the Software Update Manager back-end process. To do this, in the GUI menu bar choose Update -> Stop Update. If required, shut down the SUM GUI as well.
  2. Start the Software Update Manager back-end process and GUI again.

NOTE: After you have started the SUM GUI, do not choose Next.

  1. Reset the SUM update. To do this, in the SUM GUI menu bar choose Update -> Reset Update.
  2. Wait until the dialog for repeating a failed step appears again.
  3. Repeat the step from point of failure.

———————< D026178 AUG/22/2013 >————————–

Phase XPRAS_UPG: Errors during post-handling “RS_AFTER_IMPORT”

In phase XPRAS_UPG, the following error can occur:

2EEPU133 Errors occurred during post-handling “RS_AFTER_IMPORT” for “WWIB” “L”

This after-import method can fail if only SAP_BASIS 740 with SP03 or lower is imported.

To continue the upgrade, see SAP Note 1839664 in which a workaround is described.

To prevent this issue before starting the upgrade, see SAP Note 1894463.

The above procedure is required as temporary data for operating the shadow instance is locked and cannot be removed when the SUM procedure needs to do so.

———————–< D035061 05/FEB/13 >————————–

Wrong MCOD warning for dual stack systems

In case your system is a dual stack system with an independent schema name for the JAVA part, this schema might be detected as MCOD setup. In consequence of this, a number of warnings and tasks might be recommended by the tool and the guides, that apply to real MCOD systems.

If your dual stack system is the only system on the database, you can ignore related warnings and skip any MCOD related tasks.

———————–< D038245 10/NOV/11 >————————–

UNIX: Prevent Overwriting sapuxuserchk During the Update/Upgrade

In case sapuxuserchk inside instance executable directories gets overwritten during the update/upgrade process, the startup of those instances might fail due to failing authentication for sapcontrol calls executed by SUM.

It must be prevented that the set-user-ID bit for sapuxuserchk inside the instance executable directories is overwritten during kernel switch. To do this, apply the solution described in SAP Note 1650797 after the Checks roadmap step and before downtime start.

———————–< D021970 01/FEB/12 >————————–

Dual-Stack System Update: Phase STARTSAP_PUPG Fails

In special cases during an update (for example, if you perform manual actions after SAP kernel switch), Java shared memory conflicts might be reported in phase STARTSAP_PUPG.

To solve the problem, you need to run the “cleanipc all” command and then repeat the failing phase.

  1. b) ABAP

———————–< D050889 27/JUN/16 >————————–

Problems with the use of “sapcontrol” with option “systempki” for remote instances

Starting or stopping the remote instances using system PKI may fail due to different reason. For more information, see SAP Note 2200230.

As of SUM 1.0 SP16 with patch level 12 or higher, you can deactivate the system PKI usage. Instead, you can continue using the authentication with <SID>adm and password. Proceed as follows:

  1. Stop the SAPup processes
  2. Check if the file <SUM_DIR>/abap/bin/SAPup_add.par exist. If not, create it.
  3. Add the following line to SAPup_add.par: /sapcontrol/systempki = OFF
  4. Restart SUM again

————————< D044220 08/APR/2016 >————————————

Error in Phase RUN_RSUPGREV_UPGR  during reset of an upgrade to Solution Manager 7.1

The reset of an upgrade to Solution Manager 7.1 aborted with the error message “Illegal mode””UPGR” in phase RUN_RSUPGREV_UPGR.

Use the following workaround to continue the reset procedure in SUM:

  1. Logon to the ABAP system as user DDIC in client 000
  2. Execute the report RSUPGRES with default options
  3. Check if the file <SUM_DIR>/abap/bin/SAPup_add.par exist. If not, create it.
  4. Add the following line to SAPup_add.par: /phase_ignore/REV_PREPROC/RUN_RSUPGREV_UPGR = 18134

————————< D044220 08/APR/2016 >————————————

Error messages due to dropping of Global Temporary Tables

You run an update from a system based on 7.50 to a system based on 7.50. During the phase RUN_RSCPINTS_CLEANUP, the Software Update Manager tries to drop Global Temporary Tables (GTT). However, they do not exist because they were already dropped in an earlier phase. This causes Syslog messages and errors in the dev traces, indicating database errors.

For example, on DB2 the following messages are created:

Syslog: Database error -156 at EXE > [IBM][CLI Driver][DB2] THE STATEMENT DOES NOT IDENTIFY A TAB

dev trace: C  *** ERROR => DB2 Call ‘SQLExecDirectW’ Error: SQLCODE = -204 : [IBM][CLI Driver][DB2] SAPR3.DEMO_GTT~ IS AN UNDEFINED NAME [dbdb2cli.c   6110]

You can ignore these errors. The tables to be dropped were already dropped in an earlier phase of the update process.

———————< D023536 JAN/11/2016 >————————–

P messages in LONGPOST.LOG regarding DDL sources for ACM-objects

You see in the the file LONGPOST.LOG messages regarding ACM-objects such as

A3PEDDU 705 “DDL Source” “ACM_AUTHVIEW_01EADA3E29″ could not be activated”:”

A3PEDDU 705 “DDL Source” “ACM_AUTHVIEW_093081B05F” could not be activated”:”

or similar messages for other ACM-objects. Or the following messages may appear:

A3PEDDU 705 “DDL Source” “C_CONTRACTMAINTAIN” could not be activated” “

A3PEDDU 705 “DDL Source” “C_EQUIPMENT” could not be activated” “

A3PEDDU 705 “DDL Source” “C_PMNOTIFICATIONTYPE” could not be activated” “

A3PEDDU 705 “DDL Source” “C_TECHNICALOBJECT” could not be activated” “

You can ignore these messages. The inconsistency existed only temporarily during the upgrade and was resolved automatically during this time span.

———————< D023536 OCT/26/2015 >————————–

PARCONV_UPG stops with error messages DA510

If the phase PARCONV_UPG stops with error messages such as

  • 2EEDA510 View “xxxxxxx” is already in the database (whereas xxxxxxx can be any view name)

repeat the phase. The error can happen due to the parallelism which is used in this phase.

———————< D033068 OCT/26/2015 >————————–

R/3trans: Possible buffer overflow in TOOLIMPI

In certain circumstances it may occur that R3trans consumes too much memory during an import which leads in phase TOOLIMPI during a SUM run to a buffer overflow and to an abort of R3trans or other processes due to missing memory. For more information and solve the issue, see SAP Note 2226783.

———————< D044220 JUL/29/2015 >————————–

Windows only: Profile names are cut off in the phase PROFREAD

If you encounter the issue that the profile names are cut off in phase PROFREAD, you can – as a workaround – complete the names manually. The issue is solved with SAP Note 1000897.

———————< D050889 JUL/20/2015 >————————–

AIX: Error message “Text file busy”

If you perform an upgrade or update on systems with AIX and you encounter the “Text file busy” error message when replacing kernel binaries, see SAP Note 1156988 to solve the issue.

———————<  D044220 APR/07/2015 >————————–

SUM stops in phase REFRESH_PROFILES with error message

The phase REFRESH_PROFILES fails with the following error message:

Calling PFL_UPLOAD_TO_DB returned 99: Activatation: failed

To solve this issue, apply SAP note 2125844. However, the transaction SNOTE does not work in this phase, and the SAP Note cannot be implemented automatically.

You can therefore ignore the error in SUM using the option “Ignore phase errors and proceed to next phase”. Afterwards, you must upload the new profile manually using transaction RZ10.

———————< D056915 DEC/12/2014 >————————–

Error message in phase MAIN_SHDRUN/ACT_UPG with regard to activation of CDS views

If you encounter an error message in phase MAIN_SHDRUN/ACT_UPG with regard to activation of CDS views such as

1EEDO519X”Ddl Source” “SEPM_SDDL_LEAVE_REQUESTS” could not be activated

repeat the phase ACT_UPG. See SAP Note 2086899 for more information.

———————< D056915 DEC/12/2014 >————————–

Copying user for SPDD fails

You are running an upgrade and you are prompted in a SUM dialog to run transaction SPDD. In your system, SAP Note 1696748 is implemented .

Due to the prompt, you want to copy a user (for example user DDIC) with which you run transaction SPDD. However, the copy procedure fails with an error message in the following way:

Error: DBSQL_TABLE:UNKNOWN

“SQL message: invalid table name: Could not find table/view

MEP_USR_DIM_STAT in schema SAPSR3SHD: line 1 col 85 (at pos 84)”.

To solve this issue, carry out the following procedure.

  1. Log on to the shadow instance in client 000 with a user different from DDIC but with the apropriate privileges. Example: DDIC_DEV
  2. Start transaction SE20 and choose option “Enhancement Implementation”.
  3. Enter enhancement implementation ES_MEP_CHANGEDOC_EVENT_IMPL and choose “Change”.
  4. In section “Runtime Behaviour” of the new dialog, deactivate the option ‘Implementation is active’, and save the change. This is a modification and will be recorded in a transport request.
  5. Then copy the user to run transaction SPDD.
  6. Run now transaction SPDD with the copied user.
  7. Log on again to client 000 with the user from step 1 (for example DDIC_DEV) and reverse the setting done in step 2, that is, you activate again the enhancement implementation ES_MEP_CHANGEDOC_EVENT_IMPL.

CAUTION: This procedure is only feasible if a development user is available that differs from user DDIC in client 000. Otherwise you must reset the upgrade and implement SAP Note 2091348 before you restart the upgrade.

——————–< D023536 SEP/30/2014 >—————————–

Aborted conversions during phase PARCONV_UPG in step 6

Symptom: The conversion of tables aborts during phase PARCONV_UPG in step 6 of the conversion while creating dependent views.

Solution: See SAP Note 2070458 for further details.

———————< D023536 APR/11/2014 >————————–

P messages in LONGPOST.LOG due to BW object activation

It may occur that the file LONGPOST.LOG contains P error messages concerning the activation of BW objects, such as:

2PETK754 Error when creating object directory entry “R3TR” “TABL” “/BI0/STCAIFAREA”

A2PERSTCO_UT 003 An error occurred while activating BW object &2″0TCAIFAREA” (<(>&<)>1″IOBJ”)&3″OM”

SUM has added these message in phase XPRAS_AIMMRG during the execution of report RS_TCO_ACTIVATION_XPRA. This report installs basic technical content BW objects, but their activation generates in some cases an error. Check the log file to see what BW objects cause problems during the activation. You can execute the report again manually after the upgrade phase. If there are still problems with some objects, try to activate the affected objects using transaction RSOR.

You can also skip the execution of report RS_TCO_ACTIVATION_XPRA during the upgrade. In this case, make sure that you execute this report manually after the upgrade phase. See SAP Note 1629923 for more information.

———————< D024828 FEB/28/2014 >————————–

Runtime error INSERT_PROGRAM_NAME_BLANK in phase XPRAS_AIMMRG

If the update or upgrade stops in phase XPRAS_AIMMRG with the runtime error INSERT_PROGRAM_NAME_BLANK, see SAP Note 1941711 for more information and further instructions.

———————< D020904 FEB/03/2014 >————————–

(Windows only:) Error “Access denied” in phase MAIN_UPTRANS/UPCONF

During an update or upgrade, the process may stop with the following error message:

Severe error(s) occured in phase MAIN_UPTRANS/UPCONF!

Last error code set: Cannot kill process 59720: Access is denied.

The error may disappear after repeating the phase. If the error occurs again, see SAP Note 1973135 for more information.

———————< D041506 JAN/14/2014 >————————–

DYNPRO_NOT_FOUND during parallel DBCLONE processes

In phase MAIN_SHDCRE/SUBMOD_SHDDBCLONE/DBCLONE, several DBCLONE processes have been started and run in parallel, but some of them stop with ST22 dump DYNPRO_NOT_FOUND. For more information and a solution, see SAP Note 1964350.

———————< D024828 DEC/16/2013 >————————–

Solaris X86_64: Timeout Error during phase MAIN_NEWBAS/STOPSAP_FINAL

You use a Solaris X86_64 system and encounter a timeout error during phase MAIN_NEWBAS/STOPSAP_FINAL. A repeat of the phase will solve the error.

———————< D023536 JUL/16/2013 >————————–

Phase ACT_UPG: Certain search helps could not be activated

During an update or upgrade, the Software Update Manager displays in phase ACT_UPG error messages such as

1EEDO519 “Srch Help” “H_5ITCN” could not be activated” or

1EEDO519 “Srch Help” “H_5ITTT” could not be activated”

You can ignore these errors. See SAP Note 1243014 for more information

———————–< D035061 OCT/14/10 >————————–

Error in Phase MAIN_NEWBAS/SUCCCHK_PROD

Symptom:

You read in the log-file PHASES.LOG the following line:

2EETQ399 Change request ‘SAPK-<vers>INCTSPLGN not removed from buffer

This message indicates, that the import of a transport request of the CTS Plug-In could not performed.

Reason known to date:

The system could not create primary indices for tables, if an object with the same name already exists. To solve this issue, drop the tables CL_CTS_REQUEST_REMOTE~~OLD and CTS_REQ_OVERLAPS~~OLD directly in the database.

Solution:

  1. Find out the cause of the import error and resolve it.
  2. Start the report /CTSPLUG/CTS_ACTIVATION and set the parameter FORCEACT=’X’. This report starts the import again.
  3. Afterwards, check whether the import was successful and the import queue is empty now. If the problem continues to exist, contact the SAP Support.
  4. If the report has run successfully, repeat the phase

MAIN_NEWBAS/SUCCCHK_PROD in the Software Update Manager to continue the upgrade

———————< D023536 JUL/16/2013 >————————–

Phase ACT_UPG: Certain tables cannot be activated

During an update or upgrade, the Software Update Manager displays in phase ACT_UPG the error message that the following tables cannot be activated :

  • /SOMO/MA_S_KEYFIG and
  • /SOMO/MA_S_MONOBJ

You can ignore this error by using the option “Accept non-severe errors”.

———————< D035061 MAY/15/2013 >————————–

Error in phases XPRAS_SHD_AIMMRG, XPRAS_AIMMRG, OR XPRAS_TRANS

During an update or upgrade, the SUM can stop during the phases XPRAS_SHD_AIMMRG, XPRAS_AIMMRG, OR XPRAS_TRANS with an error message using the following model:

Object ‘&’ language ‘&’ not created

In this case, you need to apply SAP Note 1866886. Implement manually the correction which corresponds to your target release. Afterwards repeat the affected phase in the SUM.

To avoid the error proactively, select a target Support Package level that covers that note.

———————< d001330 MAY/13/2013 >————————–

Phase XPRAS_UPG: Problems in FDT_AFTER_IMPORT or FDT_AFTER_IMPORT_C

If you encounter a problem during the upgrade in phase XPRAS_UPG in method FDT_AFTER_IMPORT or FDT_AFTER_IMPORT_C that requires a code correction, see SAP Note 1357207 for further information and consider the solution in the note.

———————–< D051861 APR/24/13 >————————–

View EPIC_V_BRS_BSEG not activated

The activation of view EPIC_V_BRS_BSEG fails during an upgrade or update. In the log file of the ABAP Dictionary activation, you see the following message: View “EPIC_V_BRS_BSEG” was not activated

To solve this issue, see SAP Note 1846998.

———————< D035061 25/MAR/13 >————————–

RFC_COMMUNICATION_FAILURE during phase CHECKSYSSTATUS

When additional instances are installed but currently stopped, the phase CHECKSYSSTATUS stops with an RFC_COMMUNICATION_FAILURE error regarding these instances.

In this case, start all installed instances during this phase so that their status can be checked. After the phase has passed successfully, you can stop the installed instances again if required. Alternatively, the services of the stopped instances need to be stopped as well, followed by a reset of SUM and start from scratch.

———————–< D053561 OCT/10/10 >————————–

tp 212 error in MAIN_NEWBAS/TABIM_UPG: left-over semaphore

The SUM stops during phase TABIM_UPG in module MAIN_NEWBAS with the following error message:

Calling <path to> tp.exe failed with return code 212, check <path to> SAPup.ECO for details.

This stop can occur when tp does not finish correctly due to one or more semaphores that haven’t been removed correctly after the end of r3trans. In general, it can happen in each phase where tp is started that semaphores are

left over. Note that the semaphores have to be kept if the tp or R3trans process of them still exists.

If you encounter the error, use the operating system first to check whether the corresponding tp is still active, for example, whether the process still exists. For more information about semaphores in tp and how to solve the problem, see SAP Note 12746.

———————< I065580 11/SEP/12 >—————————

MAIN_NEWBAS/STARTSAP_TBUPG:System start failed on NT IA64

During the MAIN_NEWBAS/STARTSAP_TBUPG phase the upgrade stops with the error message:

Checks after phase MAIN_NEWBAS/STARTSAP_TBUPG were negative! (…) System start failed

A possible solution can be note 1696517. To prevent the error, select a target kernel version that includes the related correction.

———————< D035061 13/AUG/12 >—————————

Error while sapcpe copies vcredist_x64.msi

While using the Software Update Manager for updates or upgrades from systems based on NetWeaver 7.1, errors might occur in phase MOD_INSTNR_POST when sapcpe tries to copy the file vcredist_x64.msi.

In this case, enable the write access on this file and repeat the phase.

——————– < D037517 18/MAY/11 > ————————-

Phase STARTSAP_PUPG: System start of the dialog instances failed

Checks after phase MAIN_NEWBAS/STARTSAP_PUPG were negative! Last error code set: Unknown dialogue variable ‘INSTLIST’ System start failed.

Solution: Install the latest version of the Visual C++ Runtime on the host for the dialogue instances. Repeat the upgrade step afterwards.

——————— < D035061 17/MAY/11 > ————————-

Phase ACT_UPG during EHP installation

In this phase, either the following short dump can occur:

Runtime Errors………TSV_TNEW_PAGE_ALLOC_FAILED

or this phase can take unusually long time.

In this case refer to note 1387739 and follow the instructions there.

——————–< D031901 22/OCT/10 >—————————–

Preprocessing:ERROR: Found pattern “R3load:…

You have reset the update in the Preprocessing roadmap step and now, when running the Software Update Manager again, you get the following error message:

“ERROR: Found pattern “R3load: job completed” 0 times, but expected 1! Analyze the log file for further error messages or program abort.”

This error occurs if you did not apply SAP Note 1518145 before the reset. To solve the problem, repeat the phase in which the error occured.

————————< D030559 07/JUN/10 >————————–

Preventing long runtime of SUSR_AFTER_IMP_PROFILE

During the update, the after-import method SUSR_AFTER_IMP_PROFILE can have a long runtime, and there may be a longer system downtime as a result.

For information about how to prevent long runtimes of this method, see SAP Note 821496.

——————–< D028597 29/APR/08 >—————————-

Modification Adjustment with SPDD

If you adjust modifications during the enhancement package installation using transaction SPDD and mark the change request with the “Select for transport” function, you are asked whether the modification adjustment is performed for an Upgrade or for a Support Package update. Choose “Upgrade”.

—————–< updated D023536 14/OCT/09 >————————-

———————-< D023536 19/SEP/08 >—————————-

Activation Error

An activation error for domains can occur if your source release system has a Support Package level of SAP NetWeaver 7.1 SP3, SP4, SP5 or SP6. The issue can be solved by repeating the failed phase. For more information, see SAP Note 1242867. If you have already implemented SAP Note 1242867 in your system, the error does not occur.

——————– < C5003135 26/AUG/08 > —————————

Phase MAIN_SHDIMP/SHDUNINST_DB

Description: In this phase, the following error might occur

ERROR: Error by drop user SAP<SID>SHD

In the detailed log files, you may find the error, that the user is still connected to the database. For example, for SAP MaxDB, the error message in the file XCMDOUT.LOG is as follows:

-7048,DROP/ALTER USER not allowed while user is connected

Solution: Wait for about 15 minutes and then repeat the phase. You can also repeat the phase, if you cannot clearly identify in the detailed log whether the above mentioned error occured, since repeating the phase is harmless. You can also repeat the phase several times.

  1. c) Java

———————–< I311698 MAR/18/2015 >————————–

Windows only: Correcting Issues During the Automated Mode Update

When starting the SDT GUI in automated mode, you might receive the following error:

This application has failed to start because MSVCR100.dll was not found. Re-installing the application may fix this problem.

To correct the error, proceed as follows:

  1. Install the vcredist_*.msi, located in <Drive>:\usr\SAP\<SAPSID>\SUM\ directory.
  2. Start again the automatic update procedure as described in SAP Note 2135829 – “SUM SP14: Performing SUM Automated Update”.

———————< I042050 FEB/11/2014 >—————————–

Windows only: Correcting Issues in the “Delete Old Java Content” Step

During the removal of redundant update process data, SUM might stop with an error stating that a folder under the <DRIVE>:\usr\sap\<SID>\<Instance_name>\j2ee\ path cannot be deleted, for example the “admin” folder. This issue might occur when a Windows process named “conime.exe” has a handle on the folder, thus preventing it from deletion.

To correct this issue, first you have to end the “conime.exe” process (for example, by using the Windows Task Manager) and then repeat the failed SUM step.

———————–< I071217 28/MAR/13 >————————–

Preventing Issues with Wily AutoProbe connectors

The Software Update Manager may not be able to rebuild the Wily AutoProbe connectors of the Wily Introscope Agent. To prevent this, ensure the following:

  1. The <SID>adm user executing the update process must have full administrator rights for the directories containing a Wily AutoProbe connector.
  2. Verify that the name of each used Wily AutoProbe connector jar file is connector.jar. If the name of a connector is AutoProbeConnector.jar, you have to rename it to connector.jar.

———————-< I036707 JUL/28/11 >————————–

UNIX: Remote AAS Instance startup fails in phase START-SYSTEM

For updates from SAP NetWeaver 7.1 (or higher) to SAP NetWeaver 7.3 on UNIX, it might happen that any remote additional application server instance fails to start in phase START-SYSTEM.

In this case, proceed as described in SAP Note 1613445.

———————–< D025792 MAY/19/11 >————————–

UNIX only: Apply SAP Note 995116

If your source release has a lower level than one of the following:

  • SAP Basis 6.40 Kernel patch level 169 or SP 20
  • SAP Basis 7.00 Kernel patch 96 or SP 12

you have to apply the solution in Note 995116 before starting a release upgrade. Otherwise, the Software Update Manager is unable to start and stop your SAP system as it uses sapcontrol for this.

———————-< I024101 MAY/12/11 >————————–

Error in Phase DETECT_START_RELEASE_COMPONENTS

When running an upgrade on a NetWeaver 2004-based system, the phase DETECT_START_RELEASE_COMPONENTS might fail with the following error message:

The software component <component name> could not be read from the BC_COMPVERS table; the table schema may be outdated. Fix it and then repeat the phase from the beginning.

In this case, apply SAP Note 873624.

———————-< I056573 SEP/15/09 >————————–

IBM Databases: Error in Phase DEPLOY_ONLINE_DEPL

The following error can occur in the DEPLOY_ONLINE_DEPL phase:

“Table WCR_USERSTAT Conversion currently not possible.”

For the solution, see SAP Note 1156313.

———————< I031257 NOV/19/08 >—————————-

Phase DEPLOY_ONLINE_DEPL: Timeout During AS Java Restart

On slow/loaded systems, the DEPLOY_ONLINE_DEPL phase might fail due to a timeout during AS Java restart. This restart can take several hours as during this time portal applications are updated. If this restart takes longer than expected (3h), the Software Update Manager stops with an error.

To complete the enhancement package installation, wait for the AS Java restart in SAFE mode to finish and then resume SUM. If the system is still in SAFE mode after the update process completes, apply SAP Note 1267123.

————————< D030182 20/Jun/08 >————————–

Error in Phase DEPLOY_ONLINE_DEPL (IBM DB2 for z/OS)

You may encounter an error in phase DEPLOY_ONLINE_DEPL and the following error message can be found in the log file:

===

Info: E R R O R ******* (DbModificationManager)

Info: … dbs-Error: Table KMC_WF_TEMPLATES: Conversion currently not possible

===

See SAP Note 989868 for the solution.

Additionally, you may need to increase the heap size of your Java VM. For more information, see SAP Note 1229300.

———————————————————————-

V/ Problems After the Update

This section addresses known problems that cannot be avoided using preventive measures. These problems will only occur under specific circumstances.

  1. a) General

/

  1. b) ABAP

———————< D023536 OCT/27/2015 >————————

DB02: Unknown index SFW_PACKAGE^P

Under certain circumstances, the index SFW_PACKAGE^P is not properly deleted during the update. If the index appears in the “Tables and Indexes Monitor” (transaction DB02) in section “Unknown objects in ABAP Dictionary” of the missing tables/indexes diagnostics, you can drop the index using database tools.

———————< D023536 MAR/10/2015 >————————

Upgrade of Solution Manager system from 700 to 710: Unknown table in ABAP dictionary

You use transaction DB02 (Tables and Indexes Monitor) after an upgrade of your SAP Solution Manager system from 700 to 710, and you see in Diagnostics -> Missing Tables and Indexes -> Unknown objects in ABAP Dictionary the following entry:

GTABKEYEXC~

This table is only required during the upgrade procedure. To solve this issue, drop the table on database level using database utilities.

—————–< Update D023536 JAN/14/2016 >——————–

———————< D023536 MAR/10/2015 >————————

Phase RUN_RSDB02CK_END: Missing views in RSDB02EN.ELG

At the end of an update or upgrade, the log file RSDB02CK.ELG contains information about missing views on the database. In this case, implement SAP Note 2140827 and repeat the phase.

Target release SAP NetWeaver 7.5 only: In case the log file contains information about missing views beginning with ACM, such as

2EETG002 View “ACMAUT5AF500F8D3” does not exist in the database

2EETG002 View “ACMAUT5CF0ACED61” does not exist in the database

2EETG002 View “ACMAUTCDAC2DAB2F” does not exist in the database

call transaction SACMINT and choose the option “Delete orphaned ABAP-Artifacts”. Execute the option and repeat the phase afterwards.

———————< D035956 SEP/30/2014 >————————

Detect orphaned implementations of former classic BAdI definitions

Relevant for upgrades from a source release lower than SAP_BASIS 700 to target release SAP_BASIS 700 or higher:

After an upgrade, implementations of classic BAdIs are no longer executed since the corresponding BAdI definitions do no longer exist. To detect such orphaned implementations, implement SAP Note 2046770 and execute the report FIND_ORPHANED_BADI_IMPLS. If the report finds orphaned BAdI implementations, see the SAP Note 2046770 for more details.

———————< D024828 FEB/25/2014 >————————

Ignorable short dumps LOAD_NOT_FOUND_AFTER_GEN in Phase MAIN_NEWBAS/XPRAS_AIMMRG

After the upgrade you might find short dumps LOAD_NOT_FOUND_AFTER_GEN that happenend (from a time perspective) during phase MAIN_NEWBAS/XPRAS_AIMMRG if your system was upgraded to Kernel Version 7.41 PL 23 or lower.

You can ignore these short dumps. The problem is fixed with Kernel 7.41 PL 24.

———————< D028310 DEC/16/2013 >————————

Error: DDIC_ILLEGAL_KEY_COMP_NAME

After an upgrade or update, you encounter the following error message:

DDIC_ILLEGAL_KEY_COMP_NAME

You can ignore this error.

———————< D057512 DEC/12/2013 >————————

Warnings and messages in work process trace files

After a successful update or upgrade using near-zero downtime maintenance (nZDM/SUM) capability of SUM, you see in the trace files of the work processes (dev_w*) warnings similar to the following:

C head_p=ffff80ffbfffa710: dbsl err=103=DBSL_ERR_DBOBJECT_UNKNOWN ->

dbds err=512=DS_DBOBJECTUNKNOWN, dbdsoci.c:962

C *** ERROR => ^^ Ds_exec_imm() -> err=512=DS_DBOBJECTUNKNOWN

[dbdsoci.c 976]

You can ignore these warnings. They are caused by the automatic deletion of temporary objects that were used in the shadow system only.

——————-< D047912 OCT/21/2012 >————————–

Message: DDIC deletes RFC destination SAP_UPGRADE_SHADOW_SYSTEM

After an successful upgrade or update, you see in the system log using

transaction SM21 the error message:

DDIC deletes RFC destination SAP_UPGRADE_SHADOW_SYSTEM

with the following details: A destination has been deleted in SM59,

destination maintenance of RFC. Problems can occur if this destination is still used in existing ABAP programs.

You can ignore this error message.

——————-< D035061 03/Apr/2013 >————————–

SAP_BASIS 731 SP05 to 740: Some tables remain on database

After an update from SAP_BASIS 731 SP05 or higher to SAP_BASIS 740, the tables DDREPLIAPPLI and DDREPLIAPPLIT remain on the database. You can remove these tables using transaction SE14 or database commands.

——————-< D033123 17/Nov/2012 >————————–

LONGPOST.LOG: Error message GI747

SUM has added in phase XPRAS_UPG the error message GI747 (Error during creation ofstructure GLU1″RECID””TEXT4″”JV_RECIND”) to the LONGPOST.LOG file. See SAP note 1779102 and check, if this note solves the problem.

——————< Update D035061 10/JUL/2013 >———————-

———————–< D026178 OCT/10/10 >————————–

Ignorable P messages in LONGPOST.LOG

Problem: SUM has added in phase ACT_UPG the following message to the LONGPOST.LOG file:

4PDDH176 Parameter list of append search help “RDM_WKBK” differs from appending one.

In phase CHK_POSTUP, you will be prompted as a result to check that message.

Solution: You can ignore this P message. It was written during ACT_UPG, but no followup action is required.

—————< Update D036824 31/AUG/2015 >———————

——————-< D053561 10/FEB/2012 >————————–

LONGPOST.LOG: Tables without DDIC reference or not existing in DDIC

After an upgrade or update, the file LONGPOST.LOG contains lines that indicate that a table has no DDIC reference. It can be either the following message:

1PEPU203X > Messages extracted from log file “RDDNTPUR.<SID>”

<3PETG447 Table and runtime object “NAVERS2” exist without DDIC reference (“Transp. table”) or a message such as 4 ETG003 Table “NCVERS2” does not exist in the ABAP Dictionary

The following tables can be be affected from this error message:

/1SAP1/CCE_RUN01

CRR_CONFDT

CRR_TFW_RUN_LOG

CRR4TABLES

CRRPARAMETERS

CRRRTI

CRRRTIT

CRRSCENARIOS

CRRTASKHIST

CRRTASKINFO

CRRTCONFID

NAVERS2

NCVERS2

PATALLOWED

SUBST_SLANA_HDR

SUBST_SLANA_POS

Note: We know of the list above, and the mentioned tables can safely be deleted in the database. If there are additional tables mentioned in the LONGPOST.LOG, please check the relevance for your system before you remove them.

Proceed as follows to solve this issue:

  1. Choose transaction SE11 to display the mentioned tables
  2. If the tables don’t exist in the transaction, you can remove the tables from the database.
  3. In addition, you delete the runtime objects that belong to these tables:
  4. a) Choose transaction SE37.
  5. b) Check if the function module DD_SHOW_NAMETAB contains runtime objects that belong to these tables.
  6. c) Delete the runtime objects of the tables using the function module DD_NAMETAB_DELETE.

The following tables might appear in upgrades from 702 to 730 and can safely be removed in this case. See SAP Note 824971 for more information.

GENSETM

RSJOBTABM

SERVTYPEM

If they appear in other updates, please contact the SAP support and report an incident under component BC-UPG-TLS-TLA.

Caution:

If you run a Combined Upgrade & Unicode Conversion (CU&UC), the generation of the Unicode nametab of the same objects fails in phase RUN_RADCUCNT_NEW due to missing DDIC reference. The runtime object has to be deleted as described above.

  1. c) Java

——————–< D001712 AUG/28/09 >——————————

Changing the start profile

Include the following entry in your start profile:

  • Unix:

DIR_LIBRARY = $(DIR_LIBRARY)

PATH = $(DIR_EXECUTABLE):%(PATH)

  • Windows:

PATH = $(DIR_EXECUTABLE);%(PATH)

This prevents a problem with the jmon.dll file.

Part D Chronological Summary

Date……….Topic….Short description

—————————————————————————————

NOV/11/16…IV…Customer transport requests without stack.xml

JUL/12/16…I…Verifying signed content in the stack.xml file

JUN/27/16…IV…Problems with the use of “sapcontrol” with option “systempki” for remote instances

MAY/17/16…I….Updating systems running different OS on the primary AS and SCS instances

APR/20/16…II…Chapter “Configuring SAP Host Agent Authentication and SSL Connection” is optional.

APR/08/16…IV…Error in Phase RUN_RSUPGREV_UPGR  during reset of an upgrade to Solution Manager 7.1

APR/08/16…IV…Error messages due to dropping of Global Temporary Tables

APR/01/16…IV…Activation errors in ACT_UPG for SACMRT_RULES_MR during update to NW 7.50

MAR/29/16…III..Solution Manager systems and BW systems only: Apply SAP Notes 2290149 and 2289603

MAR/24/16…I….SUM ABAP SP16 in combination with nZDM: Consider SAP Note 2297511 !

MAR/03/16…I….Customer transport requests without stack.xml supported as of PL 02

FEB/29/16…I….Non-Unicode not supported for SAP NW 7.5 and higher

FEB/26/16…III..Configure SSL Configuration for the SAP Host Agent

FEB/15/22…A….Update Notes

FEB/15/16…B….SUM Version, Maintenance Strategy and Documentation

FEB/12/16…I….Zero Downtime Option (ZDO) of SUM available on request

FEB/08/16…I….Upgrade path SAP NW 6.40 to SAP NW 7.0, NW 7.01, and NW 7.02

FEB/05/16…I….Conversion to S/4HANA, on-premise edition

FEB/05/16…I….SAP NetWeaver versions: Release Restrictions and Limitations

FEB/04/16…III..Upgrade path NW 2004 or 730 to 740 SR2: Provide 7.42 kernel and latest DCK kernel in addition

JAN/14/16…I….Phase RUN_RSDB02CK_END: Missing views in RSDB02EN.ELG

JAN/13/16…III..Server Group SAP_DEFAULT_BTC must include Primary Application Server Instance

JAN/11/16…IV…P messages in LONGPOST.LOG regarding DDL sources for ACM-objects

OCT/27/15…V….DB02: Unknown index SFW_PACKAGE^P

OCT/26/15…IV…PARCONV_UPG stops with error messages DA510

OCT/26/15…IV…R/3trans: Possible buffer overflow in TOOLIMPI

SEPT/3/15..IV..Correcting startup issues in release upgrade scenarios from SAP NetWeaver 2004 to SAP NetWeaver 7.0-based releases

AUG/31/15….V….LONGPOST.LOG: Tables without DDIC reference or not existing in DDIC

JUL/29/15…IV…Windows only: Profile names are cut off in the phase PROFREAD

JUL/20/15…IV…AIX: Error message “Text file busy”

JUN/18/15…III..Install or Update SAP Host Agent to the minimum supported version

JUN/16/15…I….Selection of higher support packages in BIND_PATCH no longer possible for certain components

APR/07/15…IV…SUM stops in phase REFRESH_PROFILES with error message

APR/01/15…I….SAP Simple Finance add-on 2.0: Consider SAP Note 2150542

MAR/26/15…V….Upgrade of Solution Manager system from 700 to 710: Unknown table in ABAP dictionary

MAR/18/15…IV…Windows only: Correcting Issues During the Automated Mode Update

MAR/10/15…IV…Error message in phase MAIN_SHDRUN/ACT_UPG with regard to activation of CDS views

DEC/12/14…IV…Copying user for SPDD fails

NOV/14/14…I….New UI available for SUM ABAP and for SUM Java scenarios

NOV/14/14…III..Enabled Data Aging and ICNV

OCT/21/14…III..De-implement SAP Note 1819126 before the upgrade or update

AUG/13/14…III..No “Single System” mode on dual-stack systems

SEP/30/14…V….Detect orphaned implementations of former classic BAdI definitions

SEP/30/14…IV…Aborted conversions during phase PARCONV_UPG in step 6

AUG/18/14…III..Deactivate IOT feature for certain tables

JUL/03/14…III..SFW activation: Prevent automatic activation of BC-Sets in all clients

APR/11/14…IV…P messages in LONGPOST.LOG due to BW object activation

FEB/28/14…IV…Runtime error INSERT_PROGRAM_NAME_BLANK in phase XPRAS_AIMMRG

FEB/25/14…V….Ignorable short dumps LOAD_NOT_FOUND_AFTER_GEN in Phase MAIN_NEWBAS/XPRAS_AIMMRG

FEB/12/14…IV…Windows only: Correcting Issues in the “Delete Old Java Content” Step

FEB/03/14…IV…(Windows only:) Error “Access denied” in phase MAIN_UPTRANS/UPCONF

JAN/14/14…IV…DYNPRO_NOT_FOUND during parallel DBCLONE processes

DEC/16/13…V…Error message DDIC_ILLEGAL_KEY_COMP_NAME

DEC/16/13…IV…Solaris X86_64: Timeout Error during phase MAIN_NEWBAS/STOPSAP_FINAL

DEC/13/13…III…Exclude Z languages

DEC/13/13…I…..Solution Manager only: SPS update of ABAP or Java stack independently is supported

NOV/16/13…V….Warnings and messages in work process trace files

NOV/11/13…IV…Correcting Issues with Resetting the Upgrade

NOV/05/13…IV…Phase ACT_UPG: Certain search helps could not be activated

OCT/29/13…I…..Software Update Manager 1.0 SP09 Release Restrictions

OCT/28/13…I…..Installing SAP Business Suite Usage Types on Top of an Existing SAP NetWeaver Java System

OCT/23/13…IV…Shadow instance reset during an upgrade

OCT/21/13…V….Message: DDIC deletes RFC destination SAP_UPGRADE_SHADOW_SYSTEM

OCT/14/13…IV…Error in Phase MAIN_NEWBAS/SUCCCHK_PROD

OCT/14/13…III…Apply SAP Note 1910464 before the import of certain SPs

AUG/16/13…IV…Phase XPRAS_UPG: Errors during post-handling “RS_AFTER_IMPORT”

JUL/26/13….I….Update of shared Wily AutoProbe connectors

JUL/15/13…IV…Phase ACT_UPG: Certain tables cannot be activated

JUN/25/13….IV…Error in phases XPRAS_SHD_AIMMRG, XPRAS_AIMMRG, OR XPRAS_TRANS

JUN/17/13….V….Tables without DDIC reference: Message ETG447 in LONGPOST.LOG

MAY/14/13…IV…Phase XPRAS_UPG: Problems in FDT_AFTER_IMPORT or FDT_AFTER_IMPORT_C

MAY/02/13…IV…ICNVREQ: Incremental conversion in special namespaces

APR/29/13…III..Setting the instance profile parameter AutoStart to ‘0’

APR/24/13…IV…View EPIC_V_BRS_BSEG not activated

APR/03/13…V….SAP_BASIS 731 SP05 to 740: Some tables remain on database

MAR/28/13…IV…Preventing Issues with Wily AutoProbe connectors

MAR/25/13…IV…RFC_COMMUNICATION_FAILURE during phase CHECKSYSSTATUS

MAR/25/13…I….SUM requires SAP kernel 7.20 or higher for target release

FEB/11/13…III..Remove usages of customer-developed objects before you start SUM

FEB/05/13…IV…Wrong MCOD warning for dual stack systems

DEC/13/12…III..See SAP Note 1413569 for table SMSCMAID

NOV/17/12…V….LONGPOST.LOG: Error message GI747

OCT/10/12…IV…Ignorable P messages in LONGPOST.LOG

OCT/10/12…IV…tp 212 error in MAIN_NEWBAS/TABIM_UPG: left-over semaphore

SEP/18/12…III..Upgrade from SAP NetWeaver 2004 to SAP NetWeaver 7.3 EHP1 Based PowerPC System on Linux: Update Your Instance Profile

SEP/18/12…III..NTsystems: Install latest sapstartserv before the update

SEP/09/12…IV…MAIN_NEWBAS/STARTSAP_TBUPG: System start failed on NT IA64

AUG/22/12…III..Implement note 1720495 before you start transaction SPAUAUG/13/12…IV…Error while sapcpe copies vcredist_x64.msi

AUG/01/12…III..Check platform-specific requirements for the 7.20 EXT kernel

JUN/07/12…II…User Management Engine on a remote instance host

FEB/01/12…IV…Dual-Stack System Update: Phase STARTSAP_PUPG Fails

NOV/10/11…IV…UNIX: Prevent Overwriting sapuxuserchk During Update

JUL/28/11…IV…UNIX: Remote AASI startup fails in phase START-SYSTEM

MAY/30/11…III..Preventing Errors Due to Unicode Length

MAY/19/11…IV…UNIX only: Apply SAP Note 995116

MAY/18/11…IV…Phase STARTSAP_PUPG: System start of the dialog instances failed

MAY/17/11…IV…Phase ACT_UPG during EHP installation

MAY/12/11…IV…Error in Phase DETECT_START_RELEASE_COMPONENTS

MAR/08/11…III..Windows only: Check registration of sapevents.dll

NOV/25/10…III..No Automatic Update of SAPCryptolib

NOV/23/10…III..Support Package Stack Update only

OCT/22/10…IV…Preprocessing:ERROR: Found pattern “R3load:..

OCT/20/10…III..Apply SAP Note 1518145 to Avoid Error During Reset

JUN/07/10…IV…Preventing long runtime of SUSR_AFTER_IMP_PROFILE

MAY/31/10…IV…Preventing Errors with Table “SATC_MD_STEP”

SEP/15/09…IV…IBM databases: Error in DEPLOY_ONLINE_DEPL phase

AUG/28/09…V….Changing the Start Profile

APR/29/09…IV…Modification Adjustment

JAN/30/09…III..Cleaning Up the Profile Directory

DEC/15/08…III..Preventing Activation Errors

NOV/20/08…IV…File HUGETABS.LST

NOV/19/08…IV…Phase DEPLOY_ONLINE_DEPL:Timeout During AS Java Restart

NOV/13/08…IV…”/ISQC/S_UT_REF” could not be activated

SEP/19/08…IV…Activation Error

AUG/26/08…IV…Phase: MAIN_SHDIMP/SHDUNINST_DB

AUG/20/08…IV…Phase XPRAS_UPG: COMPUTE_INT_PLUS_OVERFLOW

Software Components

Software Component    From     To           And Subsequent

SUM      1.0          1.0

Support Package Patches

Software Component    Support Package              Patch Level         Download

SOFTWARE UPDATE MANAGER 1.0          SP016    13

References

This document refers to

Number               Title

995116  Backward porting of sapstartsrv for earlier releases

873624  Error in phase DETECT_START_RELEASE_COMPONENTS

824971  Message ETG447 for /1SAP1/CCE_RUN01 in LONGPOST.LOG

821496  Runtime of after-import method SUSR_AFTER_IMP_PROFILE

797147  Introscope Installation for SAP Customers

786412  Determining execution server of jobs w/o target server

2297511                SUM ABAP SP16 in combination with nZDM for upgrades and updates

2269869                Additional information on converting to S/4HANA using SUM SP16

2226783                Memory leak in R3trans

2200230                Problems with use of system PKI

2164046                SAP Release Note for SL Toolset 1.0 SPS 16

2163060                Prerequisites and Restrictions of Zero Downtime Option of SUM

2150542                SAP Simple Finance, on-premise edition 1503: Important installation/upgrade/update information

2140827                Views reported as missing in DB in phase MAIN_POSTCLEAN/RUN_RSDB02CK_END_FA of upgrade

2125844                Automatic upload of profiles after an upgrade.

2091348                CD: No call of BAdI on shadow instance during upgrade

2086899                Upgrade phase MAIN_SHDRUN/ACT_UPG returns error messages: Cycle problems

2070458                Conversion: Error when creating dependent views

2046770                Detect orphaned implementations of former classic BAdI definitions

2035728                SFW activation: Prevent automatic activation of BC-Sets in all clients

  • More

[ 20 / 97 ]

This document is referenced by

Number               Title

2389621                OASM 3.0 (402) SP08

2408199                OASM 4.0 (414) SP00 Patch 1

2372841                OASM 4.0 (414) SP02

2339164                Release Note OASM 4.0 SP01

2371551                Release Note OASM 3.0 – Technical Release Version 402 SP07

2372789                OAM 4.0 (414) – Display name for the responsible person on the SPC Overview List incorrectly shown

2371809                OAM 4.0 (414) – Applicant deletes submitted document

2369766                Release Note OASM 3.0 – Technical Release Version 402 SP06

2323751                Release Note OASM 3.0 – Technical Release Version 402 SP05

2198483                Database Migration Option (DMO) of SUM 1.0 SP16

2198501                Release Note OASM 3.0 – Technical Release Version 410 SP02

2291937                Online Application Submission Management 4.0 Upgrade

2248894                Online Application Submission Management 4.0 Installation

2307257                Release Hesse CDP SP0 for OASM 4.0

2307038                Release Note Wolfsburg CDP SP0 for OASM 4.0

2198407                SAP HANA: Additional information – Software Update Manager 1.0 SP16

2200154                DB2 z/OS: Add. Info. – Software Update Manager 1.0 SP16

2200892                MSS: Additional Information � Software Update Manager 1.0 SP16

2197895                Oracle: Add. Information – Software Update Manager 1.0 SP16

You may also like...

1 Response

  1. Raghuchowdary says:

    Nice explained..

Leave a Reply

Your email address will not be published. Required fields are marked *