sapnote_0001732061 central note sum 1.0sp07

23.07.2013 of 28

SAP Note 1732061 - Central Note - Software Update Manager1.0 SP07 [lmt_008]

Note Language: English Version: 28 Validity: Valid Since 23.07.2013

Summary

Symptom

Errors in the update process; preparations for the update; additionalinformation to the update guides

Other terms

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

Reason and Prerequisites

This note applies to Software Update Manager 1.0 SP07.Use Software Update Manager 1.0 SP07 for the following maintenanceprocesses:

o Updating to SAP NetWeaver 7.4 for the following update paths:

- Updating from SAP NetWeaver 7.3 including enhancement package 1

- Updating from SAP NetWeaver 7.0-based systems (ABAP systemsonly)

- Updating from SAP NetWeaver 7.3 Java (except usage type PIAdapter Engine)

- Updating from SAP NetWeaver Composition Environment 7.2

- Updating from SAP NetWeaver Composition Environment 7.1 and SAPNetWeaver Composition Environment 7.1 including enhancementpackage 1

Refer to SAP Note 1843183 for information regarding theupcoming release of other update/upgrade paths to SAP NetWeaver7.4.

o Upgrading to SAP NetWeaver 7.3 including enhancement package 1 forthe following upgrade paths:

- Upgrading from SAP NetWeaver 2004 (except for dual-stacksystems)

For Java standalone systems: this upgrade path is onlysupported for pure portal systems

- Upgrading from SAP NetWeaver 7.0 (with SP 14 or higher) or SAPNetWeaver 7.0 including enhancement package 1 or 2

- Upgrading from SAP NetWeaver Process Integration 7.1 or SAP

23.07.2013 of 28


NetWeaver Process Integration 7.1 including enhancement package1

- Upgrading from SAP NetWeaver Composition Environment 7.1, SAPNetWeaver Composition Environment 7.1 including enhancementpackage 1 or SAP NetWeaver Composition Environment 7.2(production edition)

- Upgrading from SAP NetWeaver BW 7.3 on SAP HANA DB

- Upgrading from SAP NetWeaver 7.0-based Java hub systems whichhave Business Suite 7 applications installed on top (enablementon SAP NetWeaver 7.3 EHP1)

- Upgrading from SAP NetWeaver 7.0-based Java hub systems whichhave Business Suite 7i2010 applications installed on top(enablement on SAP NetWeaver 7.3 EHP1)

- Upgrading from SAP NetWeaver 7.0-based Java hub systems whichhave Business Suite 7i2011 applications installed on top(enablement on SAP NetWeaver 7.3 EHP1)

o Upgrading to SAP NetWeaver 7.3 for the following upgrade paths:

- Upgrading from SAP NetWeaver Process Integration 7.1 or SAPNetWeaver Process Integration 7.1 including enhancement package1

- Upgrading from SAP NetWeaver 7.0 - Process Integration, SAPNetWeaver Process Integration 7.1, or SAP NetWeaver ProcessIntegration 7.1 including enhancement package 1, each withinstalled PI Adapters (SWIFT, BCONS, ELSTER) on top

- Upgrading from SAP NetWeaver Mobile 7.1 or SAP NetWeaver Mobile7.1 including enhancement package 1

- Upgrading from SAP NetWeaver Composition Environment 7.1, SAPNetWeaver Composition Environment 7.1 including enhancementpackage 1 or SAP NetWeaver Composition Environment 7.2(production edition)

- Upgrading from SAP NetWeaver 2004

- Upgrading from SAP NetWeaver 7.0 or SAP NetWeaver 7.0 includingenhancement package 1 or 2

- Upgrading from SAP NetWeaver 7.0-based Java hub systems whichhave Business Suite 7 applications installed on top (enablementon SAP NetWeaver 7.3)

- Upgrading from SAP NetWeaver 7.0-based Java hub systems whichhave Business Suite 7i2010 applications installed on top(enablement on SAP NetWeaver 7.3)

- Upgrading from SAP NetWeaver 7.0-based Java hub systems whichhave Business Suite 7i2011 applications installed on top(enablement on SAP NetWeaver 7.3)

23.07.2013 of 28


o Upgrading to SAP Solution Manager 7.1 from the following upgradepaths:

- Upgrading from SAP Solution Manager 7.0

- Upgrading from SAP Solution Manager 7.0 EHP1

o Updating to SAP enhancement package 6 for SAP ERP 6.0, version forSAP HANA (based on SAP NetWeaver Application Server ABAP 7.4) fromSAP enhancement package 6 for SAP ERP 6.0 (ABAP components only)

See also the restriction in section I.Important General Information-> ABAP -> No single system mode for certain update paths.

o Updating to SAP enhancement package 2 for SAP SCM 7.0, version forSAP HANA (based on SAP NetWeaver Application Server ABAP 7.4) fromSAP enhancement package 2 for SAP SCM 7.0


o Updating to SAP enhancement package 2 for SAP CRM 7.0, version forSAP HANA (based on SAP NetWeaver Application Server ABAP 7.4) fromSAP enhancement package 2 for SAP CRM 7.0 (ABAP components only)


o Upgrading to SAP Business Suite 7 Innovation 2011 for the followingupgrade paths (SAP Business Suite systems are considered below):

- Upgrading from SAP Basis 4.6C-based systems

- Upgrading from SAP Basis 4.6D-based systems

- Upgrading from SAP Web AS ABAP 6.20-based systems

- Upgrading from SAP NetWeaver 04-based systems

- Upgrading from SAP NetWeaver 7.0-based systems

o Updating to SAP Business Suite 7 Innovation 2011 (enhancementpackage installation) for the following update paths:

- Updating from SAP ERP 6.0

- Updating from SAP ERP 6.0 including enhancement package 1, 2,or 3

- Updating from SAP Business Suite 7 (SAP ERP 6.0 EHP4, SAP CRM7.0, SAP SCM 7.0, SAP SRM 7.0)

- Updating from SAP Business Suite 7 Innovation 2010 (SAP ERP 6.0EHP5, SAP CRM 7.0 EHP1, SAP SCM 7.0 EHP1, SAP SRM 7.0 EHP1)

- Updating from SAP NetWeaver 7.3 Java Hub systems which haveBusiness Suite 7 applications installed on top

23.07.2013 of 28


- Updating from SAP NetWeaver 7.3 Java Hub systems which haveBusiness Suite 7i2010 applications installed on top

- Updating from SAP NetWeaver 7.3 EHP1 Java Hub systems whichhave Business Suite 7 applications installed on top

- Updating from SAP NetWeaver 7.3 EHP1 Java Hub systems whichhave Business Suite 7i2010 applications installed on top

o Updating to SAP Business Suite 7 Innovation 2010 (enhancementpackage installation) for the following update paths:



- Updating from SAP Business Suite 7 (SAP ERP 6.0 EHP4, SAP CRM7.0, SAP SCM 7.0, SAP SRM 7.0)

- Updating from SAP NetWeaver 7.3 Java Hub systems which haveBusiness Suite 7 applications installed on top

- Updating from SAP NetWeaver 7.3 EHP1 Java Hub systems whichhave Business Suite 7 applications installed on top

o Updating to SAP ERP 6.0 including enhancement package 4 for thefollowing update paths:



o Updating to SAP NetWeaver 7.3 including enhancement package 1(enhancement package installation) for the following update paths:

- Updating from SAP NetWeaver 7.3

- Updating from SAP NetWeaver 7.3-based Java hub systems whichhave Business Suite 7 applications installed on top

- Updating from SAP NetWeaver 7.3-based Java hub systems whichhave Business Suite 7i2010 applications installed on top

- Updating from SAP NetWeaver 7.3-based Java hub systems whichhave Business Suite 7i2011 applications installed on top

o Updating to SAP NetWeaver Composition Environment 7.2 from thefollowing update paths:

- SAP NetWeaver Composition Environment 7.1

- SAP NetWeaver Composition Environment 7.1 including enhancementpackage 1

o Updating to SAP NetWeaver Composition Environment 7.1 EHP1 from SAP

23.07.2013 of 28


NetWeaver Composition Environment 7.1

o Updating to SAP NetWeaver Process Integration 7.1 includingenhancement package 1 (enhancement package installation) from SAPNetWeaver Process Integration 7.1

o Updating to SAP NetWeaver Mobile 7.1 including enhancement package1 (enhancement package installation) from SAP NetWeaver Mobile 7.1

o Updating to SAP NetWeaver 7.0 including enhancement package 2(enhancement package installation) for the following update paths:

- Updating from SAP NetWeaver 7.0

- Updating from SAP NetWeaver 7.0 including enhancement package 1

o Updating to SAP NetWeaver 7.0 including enhancement package 1 fromSAP NetWeaver 7.0 (enhancement package installation)

o Applying Support Packages Stacks to the following systems:

- Systems based on SAP NetWeaver AS ABAP 7.4 (including BusinessSuite applications on SAP HANA on top)

- Systems based on SAP NetWeaver 7.0 (including Business Suiteapplications on top)

- Systems based on SAP NetWeaver 7.0 including enhancementpackage 1 (including Business Suite applications on top)



- Systems based on SAP NetWeaver 7.1 and SAP NetWeaver 7.1including enhancement package 1 (CE, PI, Mobile, bankingservices from SAP 7.0 and SAP 8.0)

- Systems based on SAP NetWeaver Composition Environment 7.2

- Systems based on SAP NetWeaver 7.3 (including systems with PIadapters SWIFT, BCONS, ELSTER on top and Java Hub systems withBusiness Suite applications on top)

- Systems based on SAP NetWeaver 7.3 including enhancementpackage 1 (including systems with PI adapters SWIFT, BCONS,ELSTER on top and Java Hub systems with Business Suiteapplications on top)

- SAP Solution Manager 7.0 including enhancement package 1

- SAP Solution Manager 7.1

o Installing additional Java usage types / technical usages on top ofexisting Java systems

23.07.2013 of 28


o Updating and patching single software components (not supported forABAP only systems)

See the attached document SUM_SP07_paths.pdf for a graphical representationof the supported update and upgrade paths.

SolutionThis is the central SAP Note for Software Update Manager 1.0SP07.CAUTION:This note is updated regularly!Therefore, you must read it again immediately before starting the tool.

ContentsPart A: Update Notes and KeywordsPart B: Software Update Manager VersionPart 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 Notes and Keywords

Keyword for Phase KEY_CHK: 1732899

For more information about the update of your specific application, see thefollowing Notes:SAP NetWeaver 7.4.......................................1751237SAP Solution Manager 7.1................................1781833SAP NetWeaver 7.3 EHP1..................................1609441SAP NetWeaver 7.3.......................................1390477EHP1 for SAP NetWeaver 7.1..............................1162299ERP on HANA 1.0 - Release Information Note..............1730095CRM on HANA 1.0 - Release Information Note..............1730098SCM on HANA 1.0 - Release Information Note..............1730175SAP ERP 6.0 EHP 6:......................................1496212SAP CRM 7.0 EHP 2:......................................1497032SAP SCM 7.0 EHP 2:......................................1497083SAP SRM 7.0 EHP 2:......................................1582094

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

23.07.2013 of 28


Database ................................................. Note number_____________________________________________________________________SAP MaxDB ....................................................1775263IBM DB2 for i ................................................1794471IBM DB2 for Linux, UNIX and Windows ..........................1774730IBM DB2 for z/OS .............................................1775281MS SQL Server ................................................1775206Oracle .......................................................1795196SAP Sybase ASE................................................1758017SAP HANA DB...................................................1775141_____________________________________________________________________

Part B: Software Update Manager VersionThis note applies to Software Update Manager 1.0 SP07.Before you start the update, check if there is a newer tool versionavailable on SAP Service Marketplace.SAP recommends that you download the latest tool version as only thisversion contains the latest corrections and is updated regularly.

The Software Update Manager is available on the SAP Service Marketplace athttp://service.sap.com/sltoolset -> Software Logistics Toolset 1.0 -> tablewith the Software Logistics tools -> Software Update Manager <version> ->Download Link.

Maintenance StrategyThe Software Update Manager 1.0 SP07 is currently in maintenance mode.The maintenance strategy for the Software Update Manager and the othertools delivered with SL Toolset 1.0 SP07 is described in the documentattached to the SL Toolset 1.0 SPS07 Release Note 1758266.

----------------------------------------------------------------------Part C: General Problems / Information

I/ Important General Information

a) General

---------------------< D023536 JUL/22/2013 >--------------------------SUM SP07 patch level 6: Error in phaseMAIN_SWITCH/SQLSELEXE_DROPBASVIEWThe following severe error occurs in phaseMAIN_SWITCH/SQLSELEXE_DROPBASVIEW with SUM SP07 patchlevel 6:tp fails with return code 237To avoid this error, make sure that you use either SUM SP07 with patchlevel 5 or lower, or patch level 7 and higher.If you encounter this error, download the current SUM SP07 from SAP ServiceMarketplace and extract it to a different directory than the current SUMdirectory. After the extraction, copy the file bin/SAPupSQLStatements.xmlfrom the extracted area to your current directory <DIR_PUT>/bin and repeatthe phase.

---------------------< D024828 MAY/17/2013 >--------------------------SAP NetWeaver 7.4: Release Restrictions and Limitations

23.07.2013 of 28


Before the update, you must familiarize with the following important SAPNotes:

o Note 1730102 - Release Restrictions for SAP NetWeaver 7.4

---------------------< D031178 MAY/17/2013 >--------------------------SAP Business Suite Powered by SAP HANA: Release Restrictionsand LimitationsBefore the update, you must familiarize with the following important SAPNotes:

o Note 1774566: SAP Business Suite Powered by SAP HANA - Restrictions

o Note 1830894: Availability of SAP NetWeaver 7.4 on IBM i

---------------------< D035061 APR/08/2013 >--------------------------Do not select "Cleanup and start refresh" before finalizationWhen the Software Update Manager has completed the update or upgrade and isat the end of the post-processing roadmap step, the dialog

"You can clean up the tool directory and start a new run."

appears on the SUM GUI with the following options:

o Continue

o Cleanup and start afresh

In this case, select "Continue" and choose the button "Continue"afterwards.Do not select "Cleanup and start refresh". This ends the internal SAPupprogramm immediately and prevents the display of the screen "Summary andEvaluation of the process". However, your update or upgrade is notaffected, as this has already been completed successfully.

---------------------< D038245 MAR/25/2013 >--------------------------SUM requires SAP kernel 7.20 or higher for target releaseThe Softwre Update Manager requires target release kernel 7.20 or higherfor all platforms.We recommend to always check before starting the update or upgrade whetherthere is a newer version of the SAP kernel available on SAP ServiceMarketplace and download it to the download directory.Lower target release kernel versions are no no longer supported and maylead to an error during the update or upgrade.

-----------------------< D029945 NOV/16/12 >--------------------------Built-in Capabilities of SUM to include customer transportrequestsAs of version 1.0 SP06, the Software Update Manager is enhanced with a newfeature to reduce the downtime by including customer transport requests tothe update phase.However, this feature is not generally released yet. We offer interestedcustomers and partners to use this new feature on an 'availability onrequest' basis.

23.07.2013 of 28


The procedure to follow in order to make use of the inclusion of customertransport requests of SUM 1.0 is described in SAP Note 1759080 (Conditionsfor SUM including customer transport requests).

----------------- < D041206 March/26/2013 > -------------------------Built-in capability near-zero downtime maintenance (nZDM/SUM)The Built-in capability near-zero downtime maintenance (nZDM/SUM) to runthe main import almost in the shadow during uptime is generally availablewithout any restrictions since SUM 1.0 SP7. nZDM/SUM is a main feature tooptimize the downtime and is available in the advanced pre-configuration ofSUM.Further release information about nZDM/SUM is described in the note1678565.

---------------------< D035061 AUG/22/2012 >--------------------------No "Single System" mode on dual stack systemsOn dual stack systems, do not use the preconfiguration mode "SingleSystem". Either use preconfiguration mode "Standard" or "Advanced" instead,or use JSPM and SPAM/SAINT separately for Support Package application.

-----------------------< 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 SoftwareUpdate Manager, an error occurs for component BI_CONT.If you want to import Support Package queues that contain this SupportPackage stack, you either use the Support Package Manager (SPAM) or youinclude at least Support Package stack 05 as well.

-----------------------< I053650 DEC/19/11 >--------------------------Java, ABAP+Java: Check for sapstartsrv Patch Level on theSource SystemTo guarantee that the Java or dual-stack SAP system can be correctlymanipulated during the update/upgrade process, the Software Update Managerchecks whether the patch level of SAP start service (sapstartsrv) on thesource system is appropriate. This check is performed in the beginning ofthe SUM process so that known problems, related to system detection as wellas proper stop and start of the SAP system, will be prevented. For moreinformation, see SAP Note 1656036.

------------------< updated D029128 MAY/31/12 >----------------------------------------------< D041112 NOV/22/11 >--------------------------SAP NetWeaver 7.3 EHP1: Release Restrictions and LimitationsBefore the update/upgrade, you must familiarize with the followingimportant SAP Notes:

o Release Restrictions for SAP EHP1 for SAP NetWeaver 7.3 - Note1522700

o SAP Business Suite for SAP NetWeaver 7.31 Hub Systems - Note1698276

-----------------------< D038722 OCT/28/11 >--------------------------

23.07.2013 of 28


SAP NetWeaver 7.0 EHP3: Release Restrictions and LimitationsBefore the update/upgrade, you must familiarize yourself with the followingimportant SAP Notes:

o Release Restrictions for EHP3 for SAP NetWeaver 7.0 - Note 1557825

o Installation of SAP EHP3 for SAP NetWeaver 7.0 - Note 1637366

o No Process Integration in SAP EHP3 FOR SAP NETWEAVER 7.0 - Note1637629

-----------------------< D025095 APR/13/11 >--------------------------SAP NetWeaver 7.3: Release Restrictions and LimitationsBefore the update, you must familiarize with the following important SAPNotes:

o Release Restrictions for SAP NetWeaver 7.3 - Note 1407532

o SAP Business Suite PI Adapters for SAP NetWeaver PI 7.3 - Note1570738

o SAP Business Suite 7 for SAP NetWeaver 7.3 hub systems - Note1468349

----------------------< I031257 SEP/08/09 >---------------------------JSPM NOT to be Used During the Update ProcessYou must not run the tool Java Support Package Manager (JSPM) when runningthe Software Update Manager. This is critical for the successful completionof the process.

b) ABAP

-----------------------< D035061 JUL/10/2012 >-------------------------Memory-Optimized Activation not supported for target releaseNW 7.4The activation of ABAP Dictionary objects in a memory-optimized mode duringan upgrades or update with target release SAP NetWeaver 7.4 is notsupported until further notice.

----------------------< D024828 NOV/26/12 >---------------------------No single system mode for certain update pathsFor the following update paths, do not use the preconfiguration mode"Single System". Either use preconfiguration mode "Standard" or "Advanced"instead:

o Updating to SAP enhancement package 6 for SAP ERP 6.0, version forSAP HANA (based on SAP NetWeaver Application Server ABAP 7.4) fromSAP enhancement package 6 for SAP ERP 6.0 (ABAP components only)

o Updating to SAP enhancement package 2 for SAP SCM 7.0, version forSAP HANA (based on SAP NetWeaver Application Server ABAP 7.4) fromSAP enhancement package 2 for SAP SCM 7.0

o Updating to SAP enhancement package 2 for SAP CRM 7.0, version for

23.07.2013 of 28


SAP HANA (based on SAP NetWeaver Application Server ABAP 7.4) fromSAP enhancement package 2 for SAP CRM 7.0 (ABAP components only)

Note: This restriction is not valid anymore as of SAP NetWeaver 7.4 SP02 orhigher.

c) Java

/

II/ Corrections to the Guide

a) General

---------------------< D023890 JUL/15/2013>----------------------------Release Upgrade: Dual-Stack Additional Appl. Server InstancesMust be ReinstalledWhen upgrading a dual-stack system, SUM is not able to automaticallyupgrade additional application server instances.You must uninstall them manually before entering downtime and reinstallthem on the new release after the upgrade. To do this, use the SoftwareProvisioning Manager 1.0 tool and the installation guide for your targetrelease.

b) ABAP

---------------------< D031330 JUN/25/2013>----------------------------Length of password of user DDICChapter "5.Running the Software Update Manager" -> "Making Entries for theExtraction Roadmap Step" -> section "Password of User DDIC (Phase PROFREAD)-> Caution:

The sentence "The length of the password of user DDIC is limited to 10characters." is not correct. The correct sentence reads as follows:"The length of the password of user DDIC is limited to 8 characters.", andit is only valid for SAP NetWeaver systems lower than 7.0. As of SAPNetWeaver 7.0, there is no such limitation.

c) Java

/

-----------------------------------------------------------------------

III/ Preparing the Update

a) General

---------------------< I067013 JAN/24/2013>----------------------------Release Upgrade only: Apply SAP Note 1805735 to preventcomponent deployment errors

In the "DEPLOY_SOFTWARE_COMPONENT" phase of the "Execution" roadmap step

23.07.2013 of 28


the following error message may appear:'Error. Server process is down or disconnected from ICM. Check serverserver process traces and ICM logs for details. Error message: therequested server is not available. Check if the host and port specified arecorrect and AS Java is up and running.'

The reason for this might be that two components with equal checksums havethe CRC deployment status set to "Aldeady deployed".To correct the problem, proceed as described in SAP Note 1805735.

---------------------< D035061 AUG/22/2012 >--------------------------No "Single System" mode on dual stack systemsOn dual stack systems, do not use the preconfiguration mode "SingleSystem". Either use preconfiguration mode "Standard" or "Advanced" instead,or use JSPM and SPAM/SAINT separately for Support Package application.

---------------------< D035061 AUG/22/2012 >--------------------------Implement note 1720495 before you start transaction SPAUMake sure to implement SAP note 1720495 immediately after a Support Packageimport, an enhancement package installation, or an upgrade and beforemaking any adjustments in transaction SPAU.Otherwise you can observe after an EHP installation or a Support packageimport notes with status 'SAP note <no.> obsolete; de-implementationnecessary' in transaction SPAU, when adjusting the note, and in the Snote.If you proceed in transaction SPAU and adjust this kind of notes, thede-implementation of the note can destroy the code of the support packageand can make the system inconsistent.The SAP note 1720495 corrects the status of the notes and avoids wrongdeimplementation of obsolete notes.

---------------------< D035061 JUL/23/2012 >--------------------------Check platform-specific requirements for the 7.20 EXT kernelIn case you want to install the 7.20 EXT kernel, or you want to change tothis kernel, check beforhand the platform-specific requirements.See SAP note 1553301 for the 7.20 EXT kernel requirements, especiallysection "Platform-Specific Information".If the requirements are not met, errors might occur in phaseTOLVERSION_EXTRACT.

---------------------< D035061 JUL/23/2012 >--------------------------Server Group SAP_DEFAULT_BTC must include Primary ApplicationServer InstanceIf you have defined a batch server group SAP_DEFAULT_BTC according to SAPNote 786412, make sure that the primary application server instance isincluded in this server group.

-----------------------< D029385 MAR/08/11 >--------------------------Upgrade on Windows only: Check registration of sapevents.dllDuring the installation of your source release system, the installationprocedure might have inadvertently registered the sapevents.dll from thecentral DIR_CT_RUN directory instead of from the local DIR_EXECUTABLEdirectories of the instance. This may lead to errors with locked kernelfiles during or after the upgrade. Therefore check the registration of

23.07.2013 of 28


sapevents.dll as described in SAP Note 1556113.

-----------------------< D037517 08/DEC/10 >--------------------------Adjust Start ProfileBefore you start the update, add the SAPSYSTEM parameter to the startprofile of your system. The entry should look like:SAPSYSTEM = <instance number>

----------------------< D037517 25/NOV/10 >--------------------------No Automatic Update of SAPCryptolibDue to problems with the format of the SAP Cryptographic Library(SAPCryptolib) files from SAP Service Marketplace, the Software UpdateManager is currently not able to update the SAP Cryptographic Library(SAPCryptolib). However, the Software Update Manager can take over theexisting SAPCryptolib. To do so, you have to copy the file sapcrypto.lst tothe directory /usr/sap/ <SID>/SYS/exe/run. The file sapcrypto.lst isincluded in the SAPCryptolib archive that you can download from SAP ServiceMarketplace.

--------------------< D050889 23/NOV/10>-------------------------------Support Package Stack Update onlyIf you want to apply a Support Package Stack on a newly installed SAPNetWeaver 7.3 system, you have to create a temporary license on the systemfirst.Call up saplicense -temp NAME=<SID>. Ignore any errors that may occur.If your system runs on Oracle 11.2, execute the following SQL command inaddition:insert into <schema>.mlicheck values (' ', ' ', ' ', ' ', ' ', 1 ,' ', ' ', ' ', ' ');commit;

----------------------< D053561 20/OCT/10 >---------------------------Apply SAP Note to Avoid Error During ResetWe recommend to apply SAP Note 1518145 before starting the Software UpdateManager (if it is not yet in your system as part of the correspondingSupport Package). This note prevents an error that can occur when you resetthe update procedure during the Preprocessing roadmap step. Without thisnote, some tables that need to be deleted during the reset cannot bedeleted.

--------------------< 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 thecorresponding Support Package.

b) ABAP

--------------------< D035061 FEB/12/2013 >---------------------------Remove usages of customer-developed objects before you startSUM

23.07.2013 of 28


The Software Update Manager applies the following security notes during theExtraction roadmap step by overwriting or deleting the related objectswithout further notice:1668465, 1631124, 1631072, 1628606, 1584549, 1584548, 1555144, 1526853,1514066, 1453164If you have not installed those notes yet, check if any customer-developedobjects make use of deleted or disabled objects and remove those usagesbefore you start the Software Update Manager.

--------------------< D053561 13/DEC/12 >-----------------------------See SAP Note 1413569 for table SMSCMAIDBefore you start the Software Update Manager, check if you use the tableSMSCMAID. If so, see SAP Note 1413569 to avoid a termination of theupgrade due to duplicate records in the table.

--------------------< D040050 19/SEP/12>-----------------------------NTsystems: Install latest sapstartserv before the updateIf you use an NT-system with the <SID>ADM as domain user, make sure thatyou apply the SAP Note 1756703 before you start the update. Otherwise, ifyou enter during the update in phase PREP_PRE_CHECK/PROFREAD the <SID>ADMname and password as domain user, the phase PREP_INPUT/INSTACELIST_PRE willnot accept the <SID>ADM password, and the SUM stops.

----------------------- <D020214 30/MAY/11 >--------------------------Preventing Errors Due to Unicode LengthA structure exists that uses a table type with a structure in at leastone component. When You call DDIF_FIELDINFO_GET, the system sometimesautomatically selects the system Unicode length instead of the UCLENUnicode length that is specified in DDIF_FIELDINFO_GET. This can lead to anRFC error in phase PREP_INIT/SPAM_CHK_INI during the upgrade or update. Toprevent this error, see SAP Note 1029444 and implement the attachedcorrection instruction.

----------------------- <D003550 15/DEC/08 >--------------------------Preventing Activation ErrorsUnder certain circumstances, information of runtime objects might get lostduring the activation. This can lead to unwanted conversions of clustertables. To prevent this error, see SAP Note 1283197 and implement theattached correction instruction.

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 vauleof the AutoStart parameter to 0. This must be done for each applicationserver 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 thevalue of the AutoStart parameter to 0, that is, AutoStart = 0.

23.07.2013 of 28


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

----------------------< I030727 21/SEP/2012 >------------------------Upgrade from SAP NetWeaver 2004 to SAP NetWeaver 7.3 EHP1Based PowerPC System on Linux: Update Your Instance ProfileBefore starting an upgrade from SAP NetWeaver 2004 to SAP NetWeaver 7.3EHP1 based PowerPC system on Linux, you need to add the following parameterto your instance profile:

jstartup/native_stack_size = 2097152

----------------------< I035760 30/JAN/09 >----------------------------Cleaning Up the Profile DirectoryBefore starting the Software Update Manager, you need to clean up theprofile directory. Remove any old, unused profiles and move any backupcopies to another directory. The profile directory must only contain activeprofile files. By default, it is located in the central file share:For UNIX: /sapmnt/<SAPSID>For Windows: <Drive>:\usr\sap\<SAPSID>\SYSFor IBM i: /sapmnt/<SID>

-----------------------------------------------------------------------

IV/ Problems During the Update Roadmap StepsThis section addresses known problems that cannot be avoided usingpreventive measures. These problems will only occur under very specificcircumstances.

a) General

-------------------------<I053650 14/MAY/2013>-------------------------Correcting errors in PhaseTypeExecuteTask phaseDuring an upgrade of a system with additional application server instances,the following error might occur:

'Error while executing PhaseTypeExecuteTask with input fileDialogInstancesTasks.xml and task DETERMINE_DI_OS. Executing command OSNamefail. Could not finish OSName command. Reading OSName on nodeID<instance_id>. com.sap.sdt.j2ee.tools.configutils.BatchConfigException:Could not create common factory.com.sap.engine.frame.core.configuration.NameNotFoundException:Aconfiguration with the path"cluster_data/dispatcher/ID<instance_id>/element-info" does not exist.'

This issue occurs if the parameter 'j2ee/instance_id' is missing from thecorresponding additional application server instance profile.To correct this issue, proceed as follows:

1. Navigate to the instance profile of the specific additionalapplication server instance, located in /usr/sap/<SAPSID>/SYS/profilefor UNIX-based systems or <DRIVE>:\usr\sap\<SAPSID>\profile forWindows-based systems.

23.07.2013 of 28


2. Add the following parameter to the profile:j2ee/instance_id = ID<ID of instance>The ID of the instance can be checked in the config tool undercluster_data.If you have not done this prior to upgrading your system, you must startSUM from the beginning so that the instance can be correctly detected.

---------------------< D035061 APR/08/2013 >--------------------------SUM terminates without finalizationThe "Summary and Evaluation of the process" screen in the Finalization stepdoes not appear. This happens when a) the Software Update Manager hascompleted the update or upgrade and is at the end of the post-processingroadmap step, and b) when you have selected at that point in time in thedialog "You can clean up the tool directory and start a new run." theoption "Cleanup and start afresh".This option ends the internal SAPup programm immediately and prevents thedisplay of the screen "Summary and Evaluation of the process". However,your update or upgrade is not affected, as this has already been completedsuccessfully.

----------------------< C5163478 25/MAR/13 >--------------------------Phase XPRAS_AIMMRG ended with errorsIt may occur in some cases that the report RS_TCO_ACTIVATION_XPRA runsduring the upgrade in phase XPRAS_AIMMRG and ends with errors.This report installs basic technical content BW objects, and you might geterrors during the activation of these objects. However, this is notcritical for the upgrade phase.Check the log file to see the BW objects that cause problems during theactivation. You can execute the report again manually after the upgradephase. If there are still problems with some objects, try to activate theseobjects using transaction RSOR.You can also skip the report execution during the upgrade. In this casemake sure that you execute the report RS_TCO_ACTIVATION_XPRA manually afterthe upgrade phase. See SAP Note 1629923 for more information.

-----------------------< D035061 05/FEB/13 >--------------------------Wrong MCOD warning for dual stack systemsIn case your system is a dual stack system with an independent schema namefor the JAVA part, this schema might be detected as MCOD setup. Inconsequence of this, a number of warnings and tasks might be recommended bythe tool and the guides, that apply to real MCOD systems.If your dual stack system is the only system on the database, you canignore related warnings and skip any MCOD related tasks.

-----------------------< D038245 10/NOV/11 >--------------------------UNIX: Prevent Overwriting sapuxuserchk During theUpdate/UpgradeIn case sapuxuserchk inside instance executable directories getsoverwritten during the update/upgrade process, the startup of thoseinstances might fail due to failing authentication for sapcontrol callsexecuted by SUM.It must be prevented that the set-user-ID bit for sapuxuserchk inside theinstance executable directories is overwritten during kernel switch. To do

23.07.2013 of 28


this, apply the solution described in SAP Note 1650797 after the Checksroadmap step and before downtime start.

-----------------------< D021970 01/FEB/12 >--------------------------Dual-Stack System Update: Phase STARTSAP_PUPG FailsIn special cases during an update (for example, if you perform manualactions after SAP kernel switch), Java shared memory conflicts might bereported in phase STARTSAP_PUPG.To solve the problem, you need to run the "cleanipc all" command and thenrepeat the failing phase.

b) ABAP

---------------------< D035061 MAY/15/2013 >--------------------------Errore in phases XPRAS_SHD_AIMMRG, XPRAS_AIMMRG, ORXPRAS_TRANSDuring an update or upgrade, the SUM can stop during the phasesXPRAS_SHD_AIMMRG, XPRAS_AIMMRG, OR XPRAS_TRANS with an error message usingthe following model:Object '&' language '&' not createdIn this case, you need to apply SAP Note 1866886. Implement manually thecorrection which corresponds to your target release. Afterwards repeat theaffected phase in the SUM.To avoid the error proactively, select a target Support Package level thatcovers that note.

---------------------< D035061 MAY/15/2013 >--------------------------Target Kernel 740 and higher: Invalid values for profileparametersYou are performing an upgrade or update with target kernel 740 or higher.During the downtime, messages can appear in the system log referring toinvalid values used for profile parameters rspo/spool_id/use_tskh andrdisp/bufrefmode.These messages can be ignored and should not occur after the upgrade orupdate anymore.

---------------------< D001330 MAY/13/2013 >--------------------------Phase XPRAS_UPG: Problems in FDT_AFTER_IMPORT orFDT_AFTER_IMPORT_CIf you encounter a problem during the upgrade in phase XPRAS_UPG in methodFDT_AFTER_IMPORT or FDT_AFTER_IMPORT_C that requires a code correction, seeSAP Note 1357207 for further information and consider the solution in thenote.

---------------------< D035061 MAY/02/2013 >--------------------------ICNVREQ: Incremental conversion in special namespacesIf you plan to use incremental conversion for tables in reservednamespaces, see SAP Note 1009759 before starting the step Initialization intransaction ICNV.

-----------------------< D051861 APR/24/13 >--------------------------View EPIC_V_BRS_BSEG not activated

23.07.2013 of 28


The activation of view EPIC_V_BRS_BSEG fails during an upgade or update. Inthe log file of the ABAP Dictionary activation, you see the followingmessage: View "EPIC_V_BRS_BSEG" was not activatedTo solve this issue, see SAP Note 1846998.

-----------------------< D057031 APR/10/13 >--------------------------(Windows only:) Phase MAIN_UPTRANS/STARTSAP_PUPG: Start of AASinstances failed During an update or upgrade of distributed and high availability systems,the start of additional application server instances fails in phaseMAIN_UPTRANS/STARTSAP_PUPG. The reason is that the SAPGLOBALHOST parameterin the instance profiles cannot be analyzed.To solve the issue, proceed as follows:

3. Check the instance profiles of all additional application serverinstances for a line that starts with #SAPGLOBALHOST.

4. Remove the # at the beginning of the line, because this sign changesthe line to a comment so that the value of the parameter cannot beanalyzed.

5. Repeat phase MAIN_UPTRANS/STARTSAP_PUPG.

----------------------< D035061 25/MAR/13 >--------------------------RFC_COMMUNICATION_FAILURE during phase CHECKSYSSTATUSWhen additional instances are installed but currently stopped, the phaseCHECKSYSSTATUS stops with an RFC_COMMUNICATION_FAILURE error regardingthese instances.In this case, start all installed instances during this phase so that theirstatus can be checked. After the phase has passed successfully, you canstop the installed instances again if required.

-----------------------< D053561 OCT/10/10 >--------------------------tp 212 error in MAIN_NEWBAS/TABIM_UPG: left-over semaphoreThe SUM stops during phase TABIM_UPG in module MAIN_NEWBAS with thefollowing 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 moresemaphores that haven't been removed correctly after the end of r3trans. Ingeneral, it can happen in each phase where tp is started that semaphoresareleft over. Note that the semaphores have to be kept if the tp or R3transprocess of them still exists.

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

---------------------< I065580 11/SEP/12 >---------------------------MAIN_NEWBAS/STARTSAP_TBUPG:System start failed

23.07.2013 of 28


During the MAIN_NEWBAS/STARTSAP_TBUPG phase the upgrade stops with theerror message:Checks after phase MAIN_NEWBAS/STARTSAP_TBUPG were negative! (...) Systemstart failedTo solve this problem, see SAP Note 1696517.

---------------------< D035061 13/AUG/12 >---------------------------Error while sapcpe copies vcredist_x64.msiWhile using the Software Update Manager for updates or upgrades fromsystems based on NetWeaver 7.1, errors might occur in phase MOD_INSTNR_POSTwhen sapcpe tries to copy the file vcredist_x64.msi.In this case, enable the write access on this file and repeat the phase.

---------------------< D028310 05/JUL/11 >---------------------------Missing tables during DB02 check after reset of updateYou have reset an update and before you restart this update, you run a DB02check (Missing Tables and Indexes). This check comes to the result that twotables (CLU4 and VER_CLUSTR) are missing in the database.You can ignore these missing tables and continue with the upgrade. Thenametabs, which caused this DB02 check result, will be deleted after theupdate has been finished.

-------------------- < D037517 18/MAY/11 > -------------------------Phase STARTSAP_PUPG: System start of the dialog instancesfailedChecks after phase MAIN_NEWBAS/STARTSAP_PUPG were negative! Last error codeset: Unknown dialogue variable 'INSTLIST' System start failed.Solution: Install the latest version of the Visual C++ Runtime on the hostfor the dialogue instances. Repeat the upgrade step afterwards.

--------------------- < D035061 17/MAY/11 > -------------------------Phase ACT_UPG phase during EHP installationIn this phase, either the following short dump can occur:Runtime Errors.........TSV_TNEW_PAGE_ALLOC_FAILEDor 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, whenrunning the Software Update Manager again, you get the following errormessage:"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_PROFILEDuring the update, the after-import method SUSR_AFTER_IMP_PROFILE can havea 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

23.07.2013 of 28


Note 821496.

----------------------< D035061 12/MAY/09 >---------------------------Resetting the Update When Using the Incremental TableConversionIf you use the incremental table conversion (ICNV) for a table which hasthe character '_' (underscore) at the sixth position and you need to resetthe Software Update Manager using "Reset Update", check if there is anindex QCM1<abcde>_QCM left on the database after the reset. <abcde> standsfor the first 5 characters of the table.You need to drop that index manually using database means before yourestart the update. For more information, see SAP Note 1337378.

--------------------< D028597 29/APR/08 >----------------------------Modification Adjustment with SPDDIf you adjust modifications during the enhancement package installationusing transaction SPDD and mark the change request with the "Select fortransport" function, you are asked whether the modification adjustment isperformed for an Upgrade or for a Support Package update. Choose "Upgrade".

-----------------< updated D023536 14/OCT/09 >-----------------------------------------------< D023536 19/SEP/08 >----------------------------Activation ErrorAn activation error for domains can occur if your source release system hasa Support Package level of SAP NetWeaver 7.1 SP3, SP4, SP5 or SP6. Theissue can be solved by repeating the failed phase. For more information,see SAP Note 1242867. If you have already implemented SAP Note 1242867 inyour system, the error does not occur.

-------------------- < C5003135 26/AUG/08 > ---------------------------Phase MAIN_SHDIMP/SHDUNINST_DBDescription: In this phase, the following error might occurERROR: Error by drop user SAP<SID>SHDIn the detailed log files, you may find the error, that the user is stillconnected to the database. For example, for SAP MaxDB, the error message inthe file XCMDOUT.LOG is as follows:-7048,DROP/ALTER USER not allowed while user is connectedSolution: Wait for about 15 minutes and then repeat the phase. You can alsorepeat the phase, if you cannot clearly identify in the detailed logwhether the above mentioned error occured, since repeating the phase isharmless. You can also repeat the phase several times.

c) Java

-----------------------< I071217 28/MAR/13 >--------------------------Preventing Issues with Wily AutoProbe connectorsThe Software Update Manager may not be able to rebuild the Wily AutoProbeconnectors of the Wily Introscope Agent. To prevent this, ensure thefollowing:

1. The <SID>adm user executing the update process must have fulladministrator rights for the directories containing a Wily AutoProbeconnector.

23.07.2013 of 28


2. Verify that the name of each used Wily AutoProbe connector jar file isconnector.jar. If the name of a connector is AutoProbeConnector.jar,you must rename it to connector.jar.

----------------------< I036707 JUL/28/11 >--------------------------UNIX: Remote AAS Instance startup fails in phase START-SYSTEMFor updates from SAP NetWeaver 7.1 (or higher) to SAP NetWeaver 7.3 onUNIX, it might happen that any remote additional application serverinstance 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 995116If your source release has a lower level than one of the following:

o SAP Basis 6.40 Kernel patch level 169 or SP 20

o SAP Basis 7.00 Kernel patch 96 or SP 12you have to apply the solution in Note 995116 before starting a releaseupgrade. Otherwise, the Software Update Manager is unable to start and stopyour SAP system as it uses sapcontrol for this.

----------------------< I024101 MAY/12/11 >--------------------------Error in Phase DETECT_START_RELEASE_COMPONENTSWhen running an upgrade on a NetWeaver 2004-based system, the phaseDETECT_START_RELEASE_COMPONENTS might fail with the following errormessage:

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

In this case, apply SAP Note 873624.

----------------------< I056573 SEP/15/09 >--------------------------IBM Databases: Error in Phase DEPLOY_ONLINE_DEPLThe 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 RestartOn slow/loaded systems, the DEPLOY_ONLINE_DEPL phase might fail due to atimeout during AS Java restart. This restart can take several hours asduring this time portal applications are updated. If this restart takeslonger than expected (3h), the Software Update Manager stops with an error.To complete the enhancement package installation, wait for the AS Javarestart in SAFE mode to finish and then resume SUM. If the system is stillin SAFE mode after the update process completes, apply SAP Note 1267123.

------------------------< D030182 20/Jun/08 >--------------------------

23.07.2013 of 28


Error in Phase DEPLOY_ONLINE_DEPL (IBM DB2 for z/OS)You may encounter an error in phase DEPLOY_ONLINE_DEPL and the followingerror message can be found in the log file:===Info: E R R O R ******* (DbModificationManager)Info: ... dbs-Error: Table KMC_WF_TEMPLATES: Conversion currently notpossible===See SAP Note 989868 for the solution.Additionally, you may need to increase the heap size of your Java VM. Formore information, see SAP Note 1229300.

----------------------------------------------------------------------

V/ Problems After the UpdateThis section addresses known problems that cannot be avoided usingpreventive measures. These problems will only occur under specificcircumstances.

a) General

b) ABAP

-----------------------< D055577 MAY/31/13 >----------------------Runtime object for VMC table is invalidAfter an update, a VM Container function module encounters an error becausethe column positions is not known for these tables which are accessed byOpenSQL for Java.For a description about the error signature and a manual workaround, seeSAP Note 1635670.

-----------------------< D026513 26/Apr/2013 >----------------------P messages in LONGPOST.LOG file referring to phase ACT_UPGProblem: SUM has added in phase ACT_UPG the following message to theLONGPOST.LOG file:4PDDH176 Parameter list of append search help "COWIPB_MCH1" differs fromappending oneSolution: You can ignore this P message.

-------------------< D035061 03/Apr/2013 >--------------------------SAP_BASIS 731 SP05 to 740: Some tables remain on databaseAfter an update from SAP_BASIS 731 SP05 or higher to SAP_BASIS 740, thetables DDREPLIAPPLI and DDREPLIAPPLIT remain on the database. You canremove 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 duringcreation ofstructure GLU1"RECID""TEXT4""JV_RECIND") to the LONGPOST.LOGfile. See SAP note 1779102 and check, if this note solves the problem.

23.07.2013 of 28


-----------------------< D026178 OCT/10/10 >--------------------------P messages in LONGPOST.LOG file referring to phase ACT_UPGProblem: SUM has added in phase ACT_UPG the following message to theLONGPOST.LOG file:4PDDH176 Parameter list of append search help "RDM_WKBK" differs fromappending oneSolution: You can ignore this P message.

-------------------< D001330 17/JUN/2013 >--------------------------Tables without DDIC reference: Message ETG447 in LONGPOST.LOGAfter the CHK_POSTUP phase, the LONGPOST.LOG log contains an entry such asthe following:3PETG447 Table and runtime object "/1SAP1/CCE_RUN01" exist without DDICreference ("Transp. table")Regarding this, see SAP Note 824971 for more information.

-------------------< D053561 10/FEB/2012 >--------------------------LONGPOST.LOG: NAVERS2 and NCVERS2 without DDIC referenceAfter an upgrade, the file LONGPOST.LOG contains the following lines:1PEPU203X > Messages extracted from log file "RDDNTPUR.<SID>" <3PETG447 Table and runtime object "NAVERS2" exist without DDIC reference("Transp. table")3PETG447 Table and runtime object "NCVERS2" exist without DDIC reference("Transp. table")

Proceed as follows to solve this issue:

1. Choose transaction SE11 to display the tables NAVERS2 and NCVERS2.

2. If the tables don't exist in the transaction, you can remove thetables NAVERS2 and NCVERS2 from the database.

3. In addition, you delete the runtime objects that belong to thesetables:

a) Choose transaction SE37.

b) Check if the function module DD_SHOW_NAMETAB contains runtimeobjects that belong to these tables.

c) Delete the runtime objects of the tables NAVERS2 and NCVERS2 usingthe function module DD_NAMETAB_DELETE.

c) Java

-----------------------< D001712 AUG/28/09 >--------------------------Changing the start profileInclude the following entry in your start profile:

o Unix:

DIR_LIBRARY = $(DIR_LIBRARY)

23.07.2013 of 28


PATH = $(DIR_EXECUTABLE):%(PATH)

o Windows:

PATH = $(DIR_EXECUTABLE);%(PATH)This prevents a problem with the jmon.dll file.

Part D Chronological Summary

Date.......Topic...Short description-----------------------------------------------------------------------JUL/22/13...I....SUM SP07 patch level 6: Error in phaseMAIN_SWITCH/SQLSELEXE_DROPBASVIEWJUL/15/13...II..Release Upgrade: Dual-Stack Additional Appl. ServerInstances Must be ReinstalledJUL/10/13...I....Memory-Optimized Activation not supported for targetrelease NW 7.4JUN/25/13...IV...Errore in phases XPRAS_SHD_AIMMRG, XPRAS_AIMMRG, ORXPRAS_TRANSJUN/25/13...II...Length of password of user DDICJUN/17/13...V....Tables without DDIC reference: Message ETG447 inLONGPOST.LOGMAY/31/13...V....Runtime object for VMC table is invalidMAY/17/13...I....SAP NetWeaver 7.4: Release Restrictions and LimitationsMAY/17/13...I....SAP Business Suite Powered by SAP HANA: ReleaseRestrictions and LimitationsMAY/15/13...IV...Target Kernel 740 and higher: Invalid values for profileparametersMAY/14/13...IV...Correcting errors in PhaseTypeExecuteTask phaseMAY/14/13...IV...Phase XPRAS_UPG: Problems in FDT_AFTER_IMPORT orFDT_AFTER_IMPORT_CMAY/02/13...IV...ICNVREQ: Incremental conversion in special namespacesAPR/29/13...III..Setting the instance profile parameter AutoStart to '0'APR/24/13...IV...View EPIC_V_BRS_BSEG not activatedAPR/11/13...IV...(Windows only:) Phase MAIN_UPTRANS/STARTSAP_PUPG: Start ofAAS instances failedAPR/08/13...IV...SUM terminates without finalizationAPR/08/13...I....Do not select "Cleanup and start refresh" beforefinalizationAPR/03/13...V....SAP_BASIS 731 SP05 to 740: Some tables remain on databaseMAR/28/13...IV...Preventing Issues with Wily AutoProbe connectorsMAR/26/13...I....Built-in capability near-zero downtime maintenance(nZDM/SUM)MAR/25/13...IV...RFC_COMMUNICATION_FAILURE during phase CHECKSYSSTATUSMAR/25/13...IV...Phase XPRAS_AIMMRG ended with errorsMAR/25/13...I....SUM requires SAP kernel 7.20 or higher for target releaseFEB/11/13...III..Remove usages of customer-developed objects before youstart SUMFEB/05/13...IV...Wrong MCOD warning for dual stack systemsJAN/24/13...III..Apply SAP Note 1805735 to prevent component deploymenterrorsDEC/13/12...III..See SAP Note 1413569 for table SMSCMAIDNOV/26/12...I....No single system mode for certain update pathsNOV/17/12...V....LONGPOST.LOG: Error message GI747NOV/16/12...I....Build-in Capabilities of SUM to include customer transportrequests

23.07.2013 of 28


OCT/10/12...IV...P messages in LONGPOST.LOG file referring to phase ACT_UPGOCT/10/12...IV...tp 212 error in MAIN_NEWBAS/TABIM_UPG: left-over semaphoreSEP/18/12...III..Upgrade from SAP NetWeaver 2004 to SAP NetWeaver 7.3 EHP1Based PowerPC System on Linux: Update Your Instance ProfileSEP/18/12...III..NTsystems: Install latest sapstartserv before the updateSEP/09/12...IV...MAIN_NEWBAS/STARTSAP_TBUPG:System start failedAUG/22/12...III..No "Single System" mode on dual-stack systemsAUG/22/12...III..Implement note 1720495 before you start transactionSPAUAUG/13/12...IV...Error while sapcpe copies vcredist_x64.msiAUG/01/12...III..Check platform-specific requirements for the 7.20 EXTkernelJUL/23/12...III..Server Group SAP_DEFAULT_BTC must include PrimaryApplication Server InstanceJUN/07/12...II...User Management Engine on a remote instance hostFEB/10/12...V....LONGPOST.LOG: NAVERS2 and NCVERS2 w/o DDIC referenceFEB/01/12...IV...Dual-Stack System Update: Phase STARTSAP_PUPG FailsNOV/22/11...I....SAP NetWeaver 7.3 EHP1: Release Restrictions andLimitationsNOV/10/11...IV...UNIX: Prevent Overwriting sapuxuserchk During UpdateOCT/28/11...I....SAP NetWeaver 7.0 EHP3: Release Restrictions andLimitationsJUL/28/11...IV...UNIX: Remote AASI startup fails in phase START-SYSTEMJUL/05/11...IV...Missing tables during DB02 check after reset of updateMAY/30/11...III..Preventing Errors Due to Unicode LengthMAY/19/11...IV...UNIX only: Apply SAP Note 995116MAY/18/11...IV...Phase STARTSAP_PUPG: System start of the dialog instancesfailedMAY/17/11...IV...Phase ACT_UPG phase during EHP installationMAY/12/11...IV...Error in Phase DETECT_START_RELEASE_COMPONENTSAPR/13/11...I....SAP NetWeaver 7.3: Release Restrictions and LimitationsMAR/08/11...III..Windows only: Check registration of sapevents.dllDEC/08/10...III..Adjust Start ProfileNOV/25/10...III..No Automatic Update of SAPCryptolibNOV/23/10...III..Support Package Stack Update onlyOCT/22/10...IV...Preprocessing:ERROR: Found pattern "R3load:..OCT/20/10...III..Apply SAP Note 1518145 to Avoid Error During ResetJUN/07/10...IV...Preventing long runtime of SUSR_AFTER_IMP_PROFILEMAY/31/10...IV...Preventing Errors with Table "SATC_MD_STEP"SEP/15/09...IV...IBM databases: Error in DEPLOY_ONLINE_DEPL phaseSEP/08/09...I....JSPM NOT to be Used During the Update ProcessAUG/28/09...V....Changing the Start ProfileMAY/12/09...IV...Resetting the Installation When Using ICNVAPR/29/09...IV...Modification AdjustmentJAN/30/09...III..Cleaning Up the Profile DirectoryDEC/15/08...III..Preventing Activation ErrorsNOV/20/08...IV...File HUGETABS.LSTNOV/19/08...IV...Phase DEPLOY_ONLINE_DEPL:Timeout During AS Java RestartNOV/13/08...IV..."/ISQC/S_UT_REF" could not be activatedSEP/19/08...IV...Activation ErrorAUG/26/08...IV...Phase: MAIN_SHDIMP/SHDUNINST_DBAUG/20/08...IV...Phase XPRAS_UPG: COMPUTE_INT_PLUS_OVERFLOW

Header Data

Release Status: Released for CustomerReleased on: 23.07.2013 12:35:45

23.07.2013 of 28


Master Language: EnglishPriority: Correction with high priorityCategory: Upgrade informationPrimary Component: BC-EHP-INS Enhancement Package Installer

Secondary Components:BC-UPG-TLS Upgrade Tools

BC-UPG Upgrade - general

BC-UPG-TLS-TLA Upgrade tools for ABAP

BC-UPG-TLS-TLJ Upgrade tools for Java

BC-UPG-SLC Software Logistics Controller

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

SUM 1.0 1.0 1.0

Related Notes

Number Short Text

1846998 View EPIC_V_BRS_BSEG not activated

1830894 Availability of SAP NetWeaver 7.4 on IBM i

1805735 DB2 z/OS: J2EE accounting, single quote in acc string

1795196 Oracle: Add. Information - Software Update Manager 1.0 SP07

1794471 IBM DB2 for i: Add. Info - Software Update Manager 1.0 SP07

1779102 RGZZGLUX: Error GU093 or GI747 because of field RECID

1775281 DB2 z/OS: Add. Info. - Software Update Manager 1.0 SP07

1775263 MaxDB: Add. information - Software Update Manager 1.0 SP07

1775206 MSS: Add. Info. - Software Update Manager 1.0 SP7

1775141 SAP HANA: Additional info - Software Update Manager 1.0 SP07

1774730 DB6: Add. Info - Software Update Manager 1.0 SP07

1774566 SAP Business Suite Powered by SAP HANA - Restrictions

1759080 Conditions for SUM including customer transport requests

1758266 SAP Release Note for SL Toolset 1.0 SPS07

1758017 SYB: Add. Info - Software Update Manager 1.0 SP07

1756703 sapstartsrv: instance property is missing for ERS

1751237 Add. info about the update/upgrade to SAP NetWeaver 7.4

1720495 Invalid deimplementation of obsolete notes by Snote tool

1698276 SAP Business Suite for SAP NetWeaver 7.31 hub systems

1696517 Memory alignment problem in sapstartsrv.exe process

1678565 Prerequisites, Terms and Conditions for nZDM/SUM

1668465 Directory traversal in RSUPG_COPY_SHD_VIEWS

1656036 SUM functionality for checking sapstartsrv patch level

1650797 Prevent overwriting of sapuxuserchk during update/upgrade

1637629 No Process Integration in SAP EHP3 FOR SAP NETWEAVER 7.0

1637366 Installation of SAP EHP3 for SAP NetWeaver 7.0

1635670 Runtime object for VMC table is invalid

23.07.2013 of 28


Number Short Text

1633876 SUM fails in INSTALL_TEMP_LICENSE phase

1631124 Potential modification of persisted data by RDDCP6TB

1631072 Potential modification of persisted data by RDDNT4DL

1629923 Skip BW technical content objects activation during upgrade

1628606 Potential modification of persisted data by RSTRESNC

1615463 SAP Business Suite 7i 2010 for SAP NetWeaver 7.3 hub systems

1613445 Remote AAS instance startup fails during SUM update on UNIX

1609441 Add. info about the upgrade to SAP NetWeaver 7.3 EHP1

1584549 Directory traversal in function group SUGPEWA

1584548 Directory traversal in RSUPGSUM

1577595 Index P of table SFW_PACKAGE is not deleted

1570738 SAP Business Suite PI adapters for SAP NetWeaver PI 7.3

1557825 Release Restrictions for SAP EHP 3 for SAP NetWeaver 7.0

1556113 sapevents.dll in DIR_CT_RUN is locked

1555144 Potential information disclosure relating to file system

1526853 Safeguarding the upgrade tools against acts of sabotage

1522700 Release Restrictions for SAP EHP1 for SAP NetWeaver 7.3

1518145 FM DD_DB_MISSING_OBJECTS returns incorrect no. of objects

1514066 Overwriting files during upgrade or EHP installation

1489787 Software Update Manager 1.0: IBM DB2 for i

1468467 Sequence problem during DROP/CREATE of indexes

1468349 SAP Business Suite 7 for SAP NetWeaver 7.3 hub systems

1463168 Tables "SATC_MD_STEP" and "SATC_AC_CHK" and upgrade tools

1453164 Missing authorization check in module of upgrade

1413569 SCMA - performance, index for SMSCMAID table

1407532 Release Restrictions for SAP NetWeaver 7.3

1390477 Additional info about the upgrade to SAP NetWeaver 7.3

1387739 Out of memory errors during shadow system operation

1357207 Implementation of coding corrections during phase XPRAS_UPG

1337378 ICNV: Form oidx_cre:Operation DB_CREATE_INDEX failed

1283197 Clustertabellen: Unnötige Umsetzung

1267123 System remains in SAFE mode after update

1264734 Error message for reference table and reference fields

1243486 Dump COMPUTE_INT_PLUS_OVERFLOW during background cleanup

1242867 Domain append structure is not activated

1162299 Installation of Enhancement Package 1 for NetWeaver 710

1162171 DDIC: Texts of domain fixed values are lost after transport

1161733 SQL Server: SAP EHPI for SAP NetWeaver 7.0

1160166 DB6: Add. Information - SAP Enhancement Package Installer

1156313 Activity Report Upgrade with IBM Databases (DB2, DB4, DB6)

1142632 Enhancements for Enhancement Package installer: MaxDB

1127815 DB2-z/OS: Additions EhP installer / SUM

1109375 Values from fixed value append are missing in the domain

1029444 DDIF_FIELDINFO_GET:Prob with UCLEN <> system Unicode length

1025085 How to manually patch the SAPJVM

23.07.2013 of 28


Number Short Text

1009759 Incremental conversion in special namespaces

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 Wily Introscope Installation for SAP Customers

786412 Determining execution server of jobs w/o target server

12746 WARN <file> is already in use (), I'm waiting 5 sec

Attachments

FileType

File Name Language Size

PDF SUM_SP07_paths.pdf E 184 KB

sapnote_0001732061 central note sum 1.0sp07

Documents