| Released On | 21.10.2014 |
| Component | BC-UPG-RDM README: Upgrade Supplements |
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 note applies to Software Update Manager 1.0 SP11.
Use Software Update Manager 1.0 SP11 for the following maintenance processes:
- Upgrading to SAP Business Suite 7 Innovation 2013 (based on SAP NetWeaver 7.4) for the following upgrade paths (SAP Business Suite systems are considered below):
- Upgrading from SAP R/3 4.6C
- Upgrading from SAP R/3 Enterprise 4.70 / Extension Set 1.10
- Upgrading from SAP R/3 Enterprise 4.70 / Extension Set 2.00
- Upgrading from SAP NetWeaver 2004-based systems (SAP ERP 2004, SAP SCM 4.1)
- Upgrading from SAP NetWeaver 7.0-based systems (SAP ERP 6.0 and higher, SAP SCM 5.0 and higher, SAP SRM 5.0 and higher, SAP CRM 5.0 and higher)
- Updating to SAP Business Suite 7 Innovation 2013 (based on SAP NetWeaver 7.4) for the following update/EHP installation 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 CRM 7.0, SAP SCM 7.0, SAP SRM 7.0)
- Updating from SAP Business Suite 7 Innovation 2010 (SAP ERP 6.0 EHP5, SAP CRM 7.0 EHP1, SAP SCM 7.0 EHP1, SAP SRM 7.0 EHP1)
- Updating from SAP Business Suite 7 Innovation 2011 (SAP ERP 6.0 EHP6, SAP CRM 7.0 EHP2, SAP SCM 7.0 EHP2, SAP SRM 7.0 EHP2)
- Updating from SAP enhancement package 6 for SAP ERP 6.0, version for SAP HANA
- Updating from SAP enhancement package 2 for SAP CRM 7.0, version for SAP HANA
- Updating from SAP enhancement package 2 for SAP SCM 7.0, version for SAP HANA
- Updating to SAP Business Suite 7 Innovation 2013 (based on SAP NetWeaver 7.3 including enhancement package 1) for the following update/EHP installation paths:
- Updating from SAP NetWeaver 7.3 EHP1 Java Hub systems which have Business Suite applications installed on top
- Updating to SAP Business Suite 7 Innovation 2013 (based on SAP NetWeaver 7.3) for the following update/EHP installation paths:
- Updating from SAP NetWeaver 7.3 Java Hub systems which have Business Suite applications installed on top
- Updating to SAP NetWeaver 7.4 for the following update paths:
- Upgrading from SAP NetWeaver 7.0 (with SP 14 or higher) or SAP NetWeaver 7.0 including enhancement package 1 or 2
- Updating from SAP NetWeaver AS ABAP 7.1 (for banking services from SAP 7.0 and 8.0)
- Updating from SAP NetWeaver Process Integration 7.1 or SAP NetWeaver Process Integration 7.1 including enhancement package 1
- Updating from SAP NetWeaver Composition Environment 7.1, SAP NetWeaver Composition Environment 7.1 including enhancement package 1 or SAP NetWeaver Composition Environment 7.2 (production edition)
- Updating from SAP NetWeaver 7.3 or SAP NetWeaver 7.3 including enhancement package 1
- Updating from SAP NetWeaver 7.3 Java Hub systems which have SAP Business Suite 7i2013 applications installed on top
- Updating from SAP NetWeaver 7.3 EHP1 Java Hub systems which have SAP Business 7i2013 applications installed on top
- Upgrading from SAP NetWeaver 7.0-based Java hub systems which have Business Suite 7 applications installed on top (enablement on SAP NetWeaver 7.4)
- Upgrading from SAP NetWeaver 7.0-based Java hub systems which have Business Suite 7i2010 applications installed on top (enablement on SAP NetWeaver 7.4)
- Upgrading from SAP NetWeaver 7.0-based Java hub systems which have Business Suite 7i2011 applications installed on top (enablement on SAP NetWeaver 7.4)
- Updating from SAP NetWeaver 7.3-based Java hub systems which have Business Suite 7 applications installed on top (enablement on SAP NetWeaver 7.4)
- Updating from SAP NetWeaver 7.3-based Java hub systems which have Business Suite 7i2010 applications installed on top (enablement on SAP NetWeaver 7.4)
- Updating from SAP NetWeaver 7.3-based Java hub systems which have Business Suite 7i2011 applications installed on top (enablement on SAP NetWeaver 7.4)
Note that depending on whether your system is ABAP-based or Java-based, “updating” here means performing a release upgrade or enhancement package installation (on the technical level, this is handled differently on ABAP vs Java stack).
- Upgrading to SAP NetWeaver 7.3 including enhancement package 1 for the following upgrade paths:
- Upgrading from SAP NetWeaver 2004 (except for dual-stack systems)
For Java standalone systems: this upgrade path is only supported for pure portal systems
- Upgrading from SAP NetWeaver 7.0 (with SP 14 or higher) or SAP NetWeaver 7.0 including enhancement package 1 or 2
- Upgrading from SAP NetWeaver Process Integration 7.1 or SAP NetWeaver Process Integration 7.1 including enhancement package 1
- Upgrading from SAP NetWeaver Composition Environment 7.1, SAP NetWeaver Composition Environment 7.1 including enhancement package 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 which have Business Suite 7 applications installed on top (enablement on SAP NetWeaver 7.3 EHP1)
- Upgrading from SAP NetWeaver 7.0-based Java hub systems which have Business Suite 7i2010 applications installed on top (enablement on SAP NetWeaver 7.3 EHP1)
- Upgrading from SAP NetWeaver 7.0-based Java hub systems which have Business Suite 7i2011 applications installed on top (enablement on SAP NetWeaver 7.3 EHP1)
- Upgrading to SAP NetWeaver 7.3 for the following upgrade paths:
- Upgrading from SAP NetWeaver Process Integration 7.1 or SAP NetWeaver Process Integration 7.1 including enhancement package 1
- Upgrading from SAP NetWeaver 7.0 – Process Integration, SAP NetWeaver Process Integration 7.1, or SAP NetWeaver Process Integration 7.1 including enhancement package 1, each with installed PI Adapters (SWIFT, BCONS, ELSTER) on top
- Upgrading from SAP NetWeaver Mobile 7.1 or SAP NetWeaver Mobile 7.1 including enhancement package 1
- Upgrading from SAP NetWeaver Composition Environment 7.1, SAP NetWeaver Composition Environment 7.1 including enhancement package 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 including enhancement package 1 or 2
- Upgrading from SAP NetWeaver 7.0-based Java hub systems which have Business Suite 7 applications installed on top (enablement on SAP NetWeaver 7.3)
- Upgrading from SAP NetWeaver 7.0-based Java hub systems which have Business Suite 7i2010 applications installed on top (enablement on SAP NetWeaver 7.3)
- Upgrading from SAP NetWeaver 7.0-based Java hub systems which have Business Suite 7i2011 applications installed on top (enablement on SAP NetWeaver 7.3)
- Upgrading to SAP Solution Manager 7.1 from the following upgrade paths:
- Upgrading from SAP Solution Manager 7.0
- Upgrading from SAP Solution Manager 7.0 EHP1
- Updating to SAP enhancement package 6 for SAP ERP 6.0, version for SAP HANA (based on SAP NetWeaver Application Server ABAP 7.4) from SAP ERP 6.0 and higher (ABAP components only)
- Updating to SAP enhancement package 2 for SAP SCM 7.0, version for SAP HANA (based on SAP NetWeaver Application Server ABAP 7.4) from SAP SCM 7.0 and higher
- Updating to SAP enhancement package 2 for SAP CRM 7.0, version for SAP HANA (based on SAP NetWeaver Application Server ABAP 7.4) from SAP CRM 7.0 (ABAP components only)
- Upgrading to SAP Business Suite 7 Innovation 2011 for the following upgrade 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
- Updating to SAP Business Suite 7 Innovation 2011 (enhancement package 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 CRM 7.0, SAP SCM 7.0, SAP SRM 7.0)
- Updating from SAP Business Suite 7 Innovation 2010 (SAP ERP 6.0 EHP5, 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 have Business Suite 7 applications installed on top
- Updating from SAP NetWeaver 7.3 Java Hub systems which have Business Suite 7i2010 applications installed on top
- Updating from SAP NetWeaver 7.3 EHP1 Java Hub systems which have Business Suite 7 applications installed on top
- Updating from SAP NetWeaver 7.3 EHP1 Java Hub systems which have Business Suite 7i2010 applications installed on top
- Updating to SAP Business Suite 7 Innovation 2010 (enhancement package 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 CRM 7.0, SAP SCM 7.0, SAP SRM 7.0)
- Updating from SAP NetWeaver 7.3 Java Hub systems which have Business Suite 7 applications installed on top
- Updating from SAP NetWeaver 7.3 EHP1 Java Hub systems which have Business Suite 7 applications installed on top
- Updating to SAP ERP 6.0 including enhancement package 4 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 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 which have SAP Business Suite applications installed on top
- Updating to SAP NetWeaver Composition Environment 7.2 from the following update paths:
- SAP NetWeaver Composition Environment 7.1
- SAP NetWeaver Composition Environment 7.1 including enhancement package 1
- Updating to SAP NetWeaver Composition Environment 7.1 EHP1 from SAP NetWeaver Composition Environment 7.1
- Updating to SAP NetWeaver Process Integration 7.1 including enhancement package 1 (enhancement package installation) from SAP NetWeaver Process Integration 7.1
- Updating to SAP NetWeaver Mobile 7.1 including enhancement package 1 (enhancement package installation) from SAP NetWeaver Mobile 7.1
- 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
- Updating to SAP NetWeaver 7.0 including enhancement package 1 from SAP NetWeaver 7.0 (enhancement package installation)
- Applying Support Packages Stacks to the following systems:
- Systems based on SAP NetWeaver 7.4 (including Business Suite applications on SAP HANA on top)
- Systems based on SAP NetWeaver 7.0 (including Business Suite applications on top)
- Systems based on SAP NetWeaver 7.0 including enhancement package 1 (including Business Suite applications on top)
- Systems based on SAP NetWeaver 7.0 including enhancement package 2 (including Business Suite applications on top)
- Systems based on SAP NetWeaver 7.0 including enhancement package 3 (including Business Suite applications on top)
- Systems based on SAP NetWeaver 7.1 and SAP NetWeaver 7.1 including enhancement package 1 (CE, PI, Mobile, banking services 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 PI adapters SWIFT, BCONS, ELSTER on top and Java Hub systems with Business Suite applications on top)
- Systems based on SAP NetWeaver 7.3 including enhancement package 1 (including systems with PI adapters SWIFT, BCONS, ELSTER on top and Java Hub systems with Business Suite applications on top)
- SAP Solution Manager 7.0 including enhancement package 1
- SAP Solution Manager 7.1
- Installing additional Java usage types / technical usages on top of existing Java systems
- Updating and patching single software components (not supported for ABAP only systems)
See the attached document SUM_SP11_paths.pdf for a graphical representation of the supported update and upgrade paths.
Solution
This is the central SAP Note for Software Update Manager 1.0 SP11.
CAUTION:
This note is updated regularly!
Therefore, you must read it again immediately before starting the tool.
CAUTION:
This note is updated regularly!
Therefore, you must read it again immediately before starting the tool.
Contents
Part A: Update 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 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 Notes and Keywords
Keyword for Phase KEY_CHK: 1747235
For more information about the update of your specific application, see the following Notes:
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
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
CRM on HANA 1.0 – Release Information Note…………..1730098
SCM on HANA 1.0 – Release Information Note…………..1730175
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 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
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 …………………………………………..1993051
_________________________________________________________________
IBM i …………………………………………..1993051
Database ……………………………………..Note number
_________________________________________________________________
SAP MaxDB ……………………………………….1926740
IBM DB2 for Linux, UNIX and Windows ………………..1999514
IBM DB2 for z/OS …………………………………1926798
MS SQL Server ……………………………………1926923
Oracle ………………………………………….1926454
SAP ASE………………………………………….1926697
SAP HANA DB………………………………………1926741
IBM DB2 for i ……………………………………1993051
_________________________________________________________________
_________________________________________________________________
SAP MaxDB ……………………………………….1926740
IBM DB2 for Linux, UNIX and Windows ………………..1999514
IBM DB2 for z/OS …………………………………1926798
MS SQL Server ……………………………………1926923
Oracle ………………………………………….1926454
SAP ASE………………………………………….1926697
SAP HANA DB………………………………………1926741
IBM DB2 for i ……………………………………1993051
_________________________________________________________________
Part B: SUM Version, Maintenance Strategy and Documentation
SUM Version
This note applies to Software Update Manager 1.0 SP11.
Before you start the update, check if there is a newer tool version available on SAP Service Marketplace.
SAP recommends that you download the latest tool version as only this version contains the latest corrections and is updated regularly.
This note applies to Software Update Manager 1.0 SP11.
Before you start the update, check if there is a newer tool version available on SAP Service Marketplace.
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 on the SAP Service Marketplace at http://service.sap.com/sltoolset -> Software Logistics Toolset 1.0 -> table with the Software Logistics tools -> Software Update Manager <version> -> Download Link.
Maintenance Strategy
The Software Update Manager 1.0 SP11 is currently in maintenance mode.
The maintenance strategy for the Software Update Manager and the other tools delivered with SL Toolset 1.0 SP11 is described in the document attached to the SL Toolset 1.0 SPS11 Release Note 1922474.
The Software Update Manager 1.0 SP11 is currently in maintenance mode.
The maintenance strategy for the Software Update Manager and the other tools delivered with SL Toolset 1.0 SP11 is described in the document attached to the SL Toolset 1.0 SPS11 Release Note 1922474.
DocumentationBefore you start using the SUM tool, make sure you have the latest version of the corresponding document, which is available on the SAP Service Marketplace at: http://service.sap.com/sltoolset -> Software Logistics Toolset 1.0 -> Documentation -> System Maintenance -> Updating SAP Systems Using Software Update Manager 1.0 SP11.
———————————————————————-
Part C: General Problems / Information
———————————————————————-
Part C: General Problems / Information
I/ Important General Information
a) General
———————< I044400 OCT/07/14 >——————————-
Using the ampersand symbol in passwords – RestrictionIf you are using system passwords that contain the ampersand (“&”) symbol, you might encounter errors during a release upgrade. To avoid them, change the passwords accordingly before you start the upgrade process. You can restore the original system passwords after the process has finished.
Using the ampersand symbol in passwords – RestrictionIf you are using system passwords that contain the ampersand (“&”) symbol, you might encounter errors during a release upgrade. To avoid them, change the passwords accordingly before you start the upgrade process. You can restore the original system passwords after the process has finished.
—————< Update D023536 OCT/10/2014 >————————–
——————–< D023536 SEP/30/2014 >—————————–
Target Release SAP_BASIS 740 SP8: Single System Mode with Minimum Patch Level 7
If you want to update or upgrade your system to SAP_BASIS 740 SP8 with Single System mode, you need SUM 1.0 SP11 with patch level 07 or higher.
——————–< D023536 SEP/30/2014 >—————————–
Target Release SAP_BASIS 740 SP8: Single System Mode with Minimum Patch Level 7
If you want to update or upgrade your system to SAP_BASIS 740 SP8 with Single System mode, you need SUM 1.0 SP11 with patch level 07 or higher.
——————–< I036200 DEC/13/2013 >—————————–
Solution Manager only: SPS update of ABAP or Java stack independently is supported
If you want to update the ABAP or Java stack of a dual-stack Solution Manager system to the latest SPS independently, 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 Note1595736.
Solution Manager only: SPS update of ABAP or Java stack independently is supported
If you want to update the ABAP or Java stack of a dual-stack Solution Manager system to the latest SPS independently, 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 Note1595736.
———————–< 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.
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.
———————< D024828 MAY/17/2013 >————————–
SAP NetWeaver 7.4: Release Restrictions and Limitations
Before the update, you must familiarize with the following important SAP Notes:
SAP NetWeaver 7.4: Release Restrictions and Limitations
Before the update, you must familiarize with the following important SAP Notes:
- 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)
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.
See also the SAP Note 1751237 which additional information info about the update or upgrade to SAP NetWeaver 7.4 and higher.
———————< 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:
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.
———————< 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.
———————–< D029945 NOV/16/12 >————————–
Built-in Capabilities of SUM to include customer transport requests
As of version 1.0 SP06, the Software Update Manager 1.0 SP06 is enhanced with a new feature to reduce the downtime by including customer transport requests to the update phase.
However, this feature is not generally released yet. We offer interested customers and partners to use this new feature on an ‘availability on request’ basis.
The procedure to follow in order to make use of the inclusion of customer transport requests of the SUM is described in SAP Note 1759080 (Conditions for SUM including customer transport requests).
Built-in Capabilities of SUM to include customer transport requests
As of version 1.0 SP06, the Software Update Manager 1.0 SP06 is enhanced with a new feature to reduce the downtime by including customer transport requests to the update phase.
However, this feature is not generally released yet. We offer interested customers and partners to use this new feature on an ‘availability on request’ basis.
The procedure to follow in order to make use of the inclusion of customer transport requests of the SUM is described in SAP Note 1759080 (Conditions for 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 run the main import almost in the shadow during uptime is generally available without any restrictions since SUM 1.0 SP7. nZDM/SUM is a main feature to optimize the downtime and is available in the advanced pre-configuration of SUM.
Further release information about nZDM/SUM is described in the note 1678565.
Built-in capability near-zero downtime maintenance (nZDM/SUM)
The Built-in capability near-zero downtime maintenance (nZDM/SUM) to run the main import almost in the shadow during uptime is generally available without any restrictions since SUM 1.0 SP7. nZDM/SUM is a main feature to optimize the downtime and is available in the advanced pre-configuration of SUM.
Further release information about nZDM/SUM is described in the note 1678565.
———————–< 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.
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.
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.
——————< updated D029128 MAY/31/12 >———————–
———————–< D041112 NOV/22/11 >————————–
SAP NetWeaver 7.3 EHP1: Release Restrictions and Limitations
Before the update/upgrade, you must familiarize with the following SAP Note:
Release Restrictions for SAP EHP1 for SAP NetWeaver 7.3 – Note 1522700
———————–< D041112 NOV/22/11 >————————–
SAP NetWeaver 7.3 EHP1: Release Restrictions and Limitations
Before the update/upgrade, you must familiarize with the following SAP Note:
Release Restrictions for SAP EHP1 for SAP NetWeaver 7.3 – Note 1522700
———————–< D038722 OCT/28/11 >————————–
SAP NetWeaver 7.0 EHP3: Release Restrictions and Limitations
Before the update/upgrade, you must familiarize yourself with the following important SAP Notes:
SAP NetWeaver 7.0 EHP3: Release Restrictions and Limitations
Before the update/upgrade, you must familiarize yourself with the following important SAP Notes:
- Release Restrictions for EHP3 for SAP NetWeaver 7.0 – Note 1557825
- Installation of SAP EHP3 for SAP NetWeaver 7.0 – Note 1637366
- No Process Integration in SAP EHP3 FOR SAP NETWEAVER 7.0 – Note 1637629
———————–< D025095 APR/13/11 >————————–
SAP NetWeaver 7.3: Release Restrictions and Limitations
Before the update, you must familiarize with the following important SAP Notes:
SAP NetWeaver 7.3: Release Restrictions and Limitations
Before the update, you must familiarize with the following important SAP Notes:
- Release Restrictions for SAP NetWeaver 7.3 – Note 1407532
- SAP Business Suite PI Adapters for SAP NetWeaver PI 7.3 – Note 1570738
———————-< I031257 SEP/08/09 >—————————
JSPM NOT to be Used During the Update Process
You must not run the tool Java Support Package Manager (JSPM) when running the Software Update Manager. This is critical for the successful completion of the process.
JSPM NOT to be Used During the Update Process
You must not run the tool Java Support Package Manager (JSPM) when running the Software Update Manager. This is critical for the successful completion of the process.
b) ABAP
/
c) Java
———————–< D023890 SEP/10/2014 >————————–
New UI available for SUM Java scenarios
Scenarios based on SUM Java can now be run using a new user interface that is named SL Common Graphic User Interface. This new UI is based on SAPUI5. It runs in a browser and does not require any Java UI component. The scenario Database Migration Option (DMO) of SUMuses already this UI.
For more information about the new UI and how to use it, see the blog “SUM: extending the new UI to AS Java scenarios”, which is available in the SAP Community Network (SCN) at http://scn.sap.com/community/it-management/alm/software-logistics/blog/2014/07/16/sum-extending-the-new-ui-to-as-java-scenarios.
New UI available for SUM Java scenarios
Scenarios based on SUM Java can now be run using a new user interface that is named SL Common Graphic User Interface. This new UI is based on SAPUI5. It runs in a browser and does not require any Java UI component. The scenario Database Migration Option (DMO) of SUMuses already this UI.
For more information about the new UI and how to use it, see the blog “SUM: extending the new UI to AS Java scenarios”, which is available in the SAP Community Network (SCN) at http://scn.sap.com/community/it-management/alm/software-logistics/blog/2014/07/16/sum-extending-the-new-ui-to-as-java-scenarios.
———————–< 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 athttp://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.
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 athttp://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
a) General
———————–< I046284 JUN/07/2012 >————————-
User Management Engine on a remote instance host
During the upgrade or update of an SAP system that has a User Management Engine(UME) located on a remote instance host, make sure that this instance is operational.
User Management Engine on a remote instance host
During the upgrade or update of an SAP system that has a User Management Engine(UME) located on a remote instance host, make sure that this instance is operational.
b) ABAP
———————–< D031330 JUL/17/2014 >————————-
STMS: Distributing the Configuration as Follow-up Activity
In the SUM Guide the section “6 Follow-Up Activities” -> “Transport Management System: Distributing the Configuration”: The procedure within the note, that is relevant in case the display of the releases is not updated automatically, is also valid for target release SAP NetWeaver 7.4.
STMS: Distributing the Configuration as Follow-up Activity
In the SUM Guide the section “6 Follow-Up Activities” -> “Transport Management System: Distributing the Configuration”: The procedure within the note, that is relevant in case the display of the releases is not updated automatically, is also valid for target release SAP NetWeaver 7.4.
c) Java
————————< I036200 8/9/2014 >——————————-
Resetting the Software Update Manager during the Preprocessing Roadmap Step
————————< I036200 8/9/2014 >——————————-
Resetting the Software Update Manager during the Preprocessing Roadmap Step
The steps for deleting the update directory and afterward unpacking SUM again are not required. You can start the procedure from the beginning after the reset of the procedure has finished and SUM returns to the Welcome dialog.
———————————————————————–
III/ Preparing the Update
a) General
——————< Update D019500 OCT/06/14 >———————–
———————–< D003550 SEP/05/14 >————————–
Target release SAP_BASIS 740 SP7: Prevent Error in Conversion for Pool/Cluster Tables with CURR and QUAN colums
To avoid this issue, set a break-point in phase PARCONV_UPG or PARCONV_TRANS and manually implement the correction attached in Note 1994569 once the break-point is reached. PARCONV_TRANS is only used in case of a resource-minimized execution of an EHP-installation, in all other execution modes PARCONV_UPG is executed. When the break-point is reached, the system must be unlocked and the manual correction must be performed by a non-DDIC user.
Note: This information is relevant for SUM 1.0 SP11 patch levels 00 to 05. The issue is solved with patch level 06.
———————–< D003550 SEP/05/14 >————————–
Target release SAP_BASIS 740 SP7: Prevent Error in Conversion for Pool/Cluster Tables with CURR and QUAN colums
To avoid this issue, set a break-point in phase PARCONV_UPG or PARCONV_TRANS and manually implement the correction attached in Note 1994569 once the break-point is reached. PARCONV_TRANS is only used in case of a resource-minimized execution of an EHP-installation, in all other execution modes PARCONV_UPG is executed. When the break-point is reached, the system must be unlocked and the manual correction must be performed by a non-DDIC user.
Note: This information is relevant for SUM 1.0 SP11 patch levels 00 to 05. The issue is solved with patch level 06.
———————–< 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 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.
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 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.
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.
—————-< Update D023890 OCT/13/2014 >———————–
———————< D035061 AUG/22/2012 >————————–
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 coment “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 >————————–
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 coment “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.
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.
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.
———————< 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 primary application server instance is included in this server group.
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 primary application server instance is included in this server group.
———————–< 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.
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.
———————–< D037517 08/DEC/10 >————————–
Adjust Start Profile
Before you start the update, add the SAPSYSTEM parameter to the start profile of your system. The entry should look like:
SAPSYSTEM = <instance number>
Adjust Start Profile
Before you start the update, add the SAPSYSTEM parameter to the start profile of your system. The entry should look like:
SAPSYSTEM = <instance number>
———————-< 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.
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.
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.
b) ABAP
———————< D023536 OCT/21/2014 >—————————
De-implenment 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.
De-implenment 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.
———————< I36200 AUG/11/2014 >—————————
Preventing issues with Zero Administration Management (ZAMM)If you perform a release upgrade in an ABAP or dual-stack system, make sure that you are familliar with the information provided in SAP Note 88416. In addition, if you face ZAMM issues caused by insufficient page size and virtual memory, see SAP Note 1518419.
Preventing issues with Zero Administration Management (ZAMM)If you perform a release upgrade in an ABAP or dual-stack system, make sure that you are familliar with the information provided in SAP Note 88416. In addition, if you face ZAMM issues caused by insufficient page size and virtual memory, see SAP Note 1518419.
———————–< D035956 JUL/03/2014 >————————–
SFW activation: Prevent automatic activation of BC-Sets in all clientsIn particular if table SFWPARAM contains an entry: NAME = ‘SBCSETS_ACTIVATE_IN_CLIENTS’ and VALUE = ‘X’, follow the steps described in SAP Note 2035728.
SFW activation: Prevent automatic activation of BC-Sets in all clientsIn 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.
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:
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:
- Logon to the SAP system
- Choose transaction SE16 and open table T002C
- Choose all Z language rows (max. Z1 – Z9) for editing
- 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.
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 SMSCMAIDBefore 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.
——————–< D053561 13/DEC/12 >—————————–
See SAP Note 1413569 for table SMSCMAIDBefore 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.
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.
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.
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.
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:
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
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>
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.
This section addresses known problems that cannot be avoided using preventive measures. These problems will only occur under very specific circumstances.
a) General
———————< D038245 AUG/27/2014 >—————————–
Windows: Unknown macro ‘VCREDISTPATH’ in phase EXTRACTKRN_PREDescription:
The following error occurs in phase EXTRACTKRN_PRE on Windows: Unknown macro ‘VCREDISTPATH’, and you see in the log “EXTRKRN.LOG” the entry: PID XXXXX exited with status 3010
Reason:
The actual problem is that the installation of the visual studio library requires a restart of the operating system to complete the installation process.
Solution:
If the new SAP kernel does not work properly, the host has to be restarted. The error should vanish on phase repeat.
———————< D038245 AUG/27/2014 >—————————–
Windows: Unknown macro ‘VCREDISTPATH’ in phase EXTRACTKRN_PREDescription:
The following error occurs in phase EXTRACTKRN_PRE on Windows: Unknown macro ‘VCREDISTPATH’, and you see in the log “EXTRKRN.LOG” the entry: PID XXXXX exited with status 3010
Reason:
The actual problem is that the installation of the visual studio library requires a restart of the operating system to complete the installation process.
Solution:
If the new SAP kernel does not work properly, the host has to be restarted. The error should vanish on phase repeat.
———————–< 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:
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:
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
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.
- 3. Reset the SUM update. To do this, in the SUM GUI menu bar choose Update -> Reset Update.
- 4. Wait until the dialog for repeating a failed step appears again.
- 5. 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.
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.
———————<I067708 23/MAY/2013>—————————
Correcting issues with primary application server instance host name connectivity
During SUM startup, in the console the following error might appear:
‘Unable to detect an abap and/or AS java instance of the SAP system <SID> installed on host <host name>’ .
To correct this error, restart SUM and after the startup command enter the command ‘hostname=<host name>’, where <host name> is the primary application server instance host. For example:
‘STARTUP.BAT hostname=wdmlbmd5799′ .
The error might appear when the host where the instance profile directory is located is not directly accessible due to, for example, a specific customer setup.
Correcting issues with primary application server instance host name connectivity
During SUM startup, in the console the following error might appear:
‘Unable to detect an abap and/or AS java instance of the SAP system <SID> installed on host <host name>’ .
To correct this error, restart SUM and after the startup command enter the command ‘hostname=<host name>’, where <host name> is the primary application server instance host. For example:
‘STARTUP.BAT hostname=wdmlbmd5799′ .
The error might appear when the host where the instance profile directory is located is not directly accessible due to, for example, a specific customer setup.
———————–< 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.
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.
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.
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.
b) ABAP
——————–< 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.
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.
———————< D024828 SEPT/16/2014 >————————–
HP-UX for IA64 only: Correcting issues during phase PREP_PRE_CHECK/INITPUT_PREIf you have encountered an error in this phase with an error message Password for ‘sapsso’ does not work, please reenter, proceed as described in SAP Note 2061940.
HP-UX for IA64 only: Correcting issues during phase PREP_PRE_CHECK/INITPUT_PREIf you have encountered an error in this phase with an error message Password for ‘sapsso’ does not work, please reenter, proceed as described in SAP Note 2061940.
———————< 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:
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”
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.
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.
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.
(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 processesIn 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.
DYNPRO_NOT_FOUND during parallel DBCLONE processesIn 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.
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
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”
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.
———————–< 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.
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
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 :
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.
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.
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 upgade 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.
View EPIC_V_BRS_BSEG not activated
The activation of view EPIC_V_BRS_BSEG fails during an upgade 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.
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:
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.
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.
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.
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.
———————< D028310 05/JUL/11 >—————————
Missing tables during DB02 check after reset of update
You have reset an update and before you restart this update, you run a DB02 check (Missing Tables and Indexes). This check comes to the result that two tables (CLU4 and VER_CLUSTR) are missing in the database.
You can ignore these missing tables and continue with the upgrade. The nametabs, which caused this DB02 check result, will be deleted after the update has been finished.
Missing tables during DB02 check after reset of update
You have reset an update and before you restart this update, you run a DB02 check (Missing Tables and Indexes). This check comes to the result that two tables (CLU4 and VER_CLUSTR) are missing in the database.
You can ignore these missing tables and continue with the upgrade. The nametabs, which caused this DB02 check result, will be deleted after the update has been finished.
——————– < 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.
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.
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.
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.
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”.
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.
———————-< 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.
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.
c) Java
———————< I042050 FEB/11/2014 >—————————–
Windows only: Correcting Issues in the “Delete Old Java Content” StepDuring 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.
————————-< I024107 27/FEB/14 >————————-
SAP NetWeaver 7.3 and higher only: Preventing refusal issues caused by column drop of NZDM_VALUE2While updating your SAP system, an error similar to the following might appear:
Windows only: Correcting Issues in the “Delete Old Java Content” StepDuring 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.
————————-< I024107 27/FEB/14 >————————-
SAP NetWeaver 7.3 and higher only: Preventing refusal issues caused by column drop of NZDM_VALUE2While updating your SAP system, an error similar to the following might appear:
E R R O R ******* (DbDeployConfig dev <Date> <Time>)
<Time> <Date> dbs-Error: Refuse due to drop column NZDM_VALUE2
<Time> <Date> dbs-Error: Refuse due to drop column NZDM_VALUE2
The issue is caused by an additional column added facilitate the near-Zero Downtime Maintenance Java tool. To correct this issue, proceed as described in SAP Note 1978632.
———————–< 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:
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:
- The <SID>adm user executing the update process must have full administrator rights for the directories containing a Wily AutoProbe connector.
- 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.
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:
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:
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.
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.
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.
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.
This section addresses known problems that cannot be avoided using preventive measures. These problems will only occur under specific circumstances.
a) General
——————————–< D057755 28/FEB/14>————————————-
Correcting issues with the SAP MC applet digital signature
If you open the SAP Management Console (SAP MC) by using its web interface after a SUM update procedure has been completed, a warning about the digital signature of the applet archives may appear. The reason for this is that these archives are self-signed. To correct this, acquire the archives relevant for your kernel as follows:
- Go to the SAP Software Distribution Center at: http://service.sap.com/swdc and logon with your SAP Service Marketplace ID.
- In the navigation bar, choose SAP Software Download Center -> Support Packages and Patches -> Browse our Download Catalog -> Additional Components -> SAP Kernel -> SAP KERNEL <OS> -> SAP KERNEL <Release> -> Database independent.
- Select the appropriate sapmc_<version>.sararchive from the “Download” tab.
Note: Make sure that the SAPCAR tool is available in the host where you want to update the SAP Management Console. For more information about acquiring and using the SAPCAR tool, see SAP Note 212876.
4. Open a command prompt or PowerShell and extract the sapmc_<version>.sar archive to a local directory by executing the following command:
– for Windows: SAPCAR.exe –xvf sapmc_<version>.sar
– For UNIX and IBM-i: ./SAPCAR -xvf sapmc_<version>.sar
5. Replace the existing sapmc directory with the sapmc directory that was extracted during the previous step.
For more information about installing and updating the SAP MC, see SAP Note 1014480.
b) ABAP
———————< 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.
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.
———————< D023536 APR/22/2014 >————————
SAP_BASIS 740 SP4: Missing Views in the database
After an update to SAP_BASIS 740 SP4, the views V_DSH_ASSIGNED and V_DSH_TF_DETAIL are missing in the database. These views were delivered accidentally and cannot be created on a system based on SAP_BASIS 740 SP4. You can ignore this inconsistency as the views are not needed by the system. This issue will be solved with SUM version 1.0 SP12.
SAP_BASIS 740 SP4: Missing Views in the database
After an update to SAP_BASIS 740 SP4, the views V_DSH_ASSIGNED and V_DSH_TF_DETAIL are missing in the database. These views were delivered accidentally and cannot be created on a system based on SAP_BASIS 740 SP4. You can ignore this inconsistency as the views are not needed by the system. This issue will be solved with SUM version 1.0 SP12.
———————< 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.
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.
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 filesAfter 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.
Warnings and messages in work process trace filesAfter 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.
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.
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.
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.
———————–< 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 D023536 16/JUL/2013 >———————–
——————-< 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:
——————-< 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”)
<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
CRR4TABLES
CRRPARAMETERS
CRRRTI
CRRRTIT
CRRSCENARIOS
CRRTASKHIST
CRRTASKINFO
CRRTCONFID
NAVERS2
NCVERS2
PATALLOWED
SUBST_SLANA_HDR
SUBST_SLANA_POS
CRR_CONFDT
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:
- a) Choose transaction SE37.
- b) Check if the function module DD_SHOW_NAMETAB contains runtime objects that belong to these tables.
- 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
RSJOBTABM
SERVTYPEM
If they appear in other updates, please contact the SAP support and report an incident under component BC-UPG-TLS-TLA.
c) Java
——————–< D001712 AUG/28/09 >——————————
Changing the start profile
Include the following entry in your start profile:
——————–< 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)
PATH = $(DIR_EXECUTABLE):%(PATH)
- Windows:
PATH = $(DIR_EXECUTABLE);%(PATH)
This prevents a problem with the jmon.dll file.
This prevents a problem with the jmon.dll file.
Part D Chronological Summary
Date……….Topic….Short description
—————————————————————————————
OCT/21/14…III..De-implenment SAP Note 1819126 before the upgrade or update
OCT/13/14…III..No “Single System” mode on dual-stack systems
OCT/10/14…I….Target Release SAP_BASIS 740 SP8: Single System Mode with Minimum Patch Level 7
OCT/07/14…I….Using the ampersand symbol in passwords – Restriction
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
SEP/16/14…IV…HP-UX for IA64 only: Correcting issues during phase PREP_PRE_CHECK/INITPUT_PRE
SEP/08/2014…II…Resetting the Software Update Manager during the Preprocessing Roadmap Step
SEP/05/14…III..Target release SAP_BASIS 740 SP7: Prevent Error in Conversion for Pool/Cluster Tables with CURR and QUAN colums
AUG/11/27…IV…Windows: Unknown macro ‘VCREDISTPATH’ in phase EXTRACTKRN_PRE
AUG/11/14…III..Preventing issues with Zero Administration Management (ZAMM)
JUL/17/14…II…STMS: Distributing the Configuration as Follow-up Activity
JUL/03/14…III..SFW activation: Prevent automatic activation of BC-Sets in all clients
APR/22/14…V….SAP_BASIS 740 SP4: Missing Views in the database
APR/11/14…IV…P messages in LONGPOST.LOG due to BW object activation
FEB/28/14…V….Correcting issues with the SAP MC applet digital signature
FEB/28/14…IV…Runtime error INSERT_PROGRAM_NAME_BLANK in phase XPRAS_AIMMRG
FEB/28/14…III…Consider SAP Note 1983758 while preparing the update
FEB/27/14…IV…SAP NetWeaver 7.3 and higher only: Preventing refusal issues caused by column drop of NZDM_VALUE2
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
JUL/15/13….V….LONGPOST.LOG: Tables without DDIC reference or not existing in DDIC
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/23/13…IV…Correcting issues with primary application server instance host name connectivity
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/26/13…I….Built-in capability near-zero downtime maintenance (nZDM/SUM)
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
NOV/16/12…I….Build-in Capabilities of SUM to include customer transport requests
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
JUL/23/12…III..Server Group SAP_DEFAULT_BTC must include Primary Application Server Instance
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/22/11…I….SAP NetWeaver 7.3 EHP1: Release Restrictions and Limitations
NOV/10/11…IV…UNIX: Prevent Overwriting sapuxuserchk During Update
OCT/28/11…I….SAP NetWeaver 7.0 EHP3: Release Restrictions and Limitations
JUL/28/11…IV…UNIX: Remote AASI startup fails in phase START-SYSTEM
JUL/05/11…IV…Missing tables during DB02 check after reset of update
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
APR/13/11…I….SAP NetWeaver 7.3: Release Restrictions and Limitations
MAR/08/11…III..Windows only: Check registration of sapevents.dll
DEC/08/10…III..Adjust Start Profile
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
SEP/08/09…I….JSPM NOT to be Used During the Update Process
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
—————————————————————————————
OCT/21/14…III..De-implenment SAP Note 1819126 before the upgrade or update
OCT/13/14…III..No “Single System” mode on dual-stack systems
OCT/10/14…I….Target Release SAP_BASIS 740 SP8: Single System Mode with Minimum Patch Level 7
OCT/07/14…I….Using the ampersand symbol in passwords – Restriction
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
SEP/16/14…IV…HP-UX for IA64 only: Correcting issues during phase PREP_PRE_CHECK/INITPUT_PRE
SEP/08/2014…II…Resetting the Software Update Manager during the Preprocessing Roadmap Step
SEP/05/14…III..Target release SAP_BASIS 740 SP7: Prevent Error in Conversion for Pool/Cluster Tables with CURR and QUAN colums
AUG/11/27…IV…Windows: Unknown macro ‘VCREDISTPATH’ in phase EXTRACTKRN_PRE
AUG/11/14…III..Preventing issues with Zero Administration Management (ZAMM)
JUL/17/14…II…STMS: Distributing the Configuration as Follow-up Activity
JUL/03/14…III..SFW activation: Prevent automatic activation of BC-Sets in all clients
APR/22/14…V….SAP_BASIS 740 SP4: Missing Views in the database
APR/11/14…IV…P messages in LONGPOST.LOG due to BW object activation
FEB/28/14…V….Correcting issues with the SAP MC applet digital signature
FEB/28/14…IV…Runtime error INSERT_PROGRAM_NAME_BLANK in phase XPRAS_AIMMRG
FEB/28/14…III…Consider SAP Note 1983758 while preparing the update
FEB/27/14…IV…SAP NetWeaver 7.3 and higher only: Preventing refusal issues caused by column drop of NZDM_VALUE2
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
JUL/15/13….V….LONGPOST.LOG: Tables without DDIC reference or not existing in DDIC
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/23/13…IV…Correcting issues with primary application server instance host name connectivity
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/26/13…I….Built-in capability near-zero downtime maintenance (nZDM/SUM)
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
NOV/16/12…I….Build-in Capabilities of SUM to include customer transport requests
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
JUL/23/12…III..Server Group SAP_DEFAULT_BTC must include Primary Application Server Instance
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/22/11…I….SAP NetWeaver 7.3 EHP1: Release Restrictions and Limitations
NOV/10/11…IV…UNIX: Prevent Overwriting sapuxuserchk During Update
OCT/28/11…I….SAP NetWeaver 7.0 EHP3: Release Restrictions and Limitations
JUL/28/11…IV…UNIX: Remote AASI startup fails in phase START-SYSTEM
JUL/05/11…IV…Missing tables during DB02 check after reset of update
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
APR/13/11…I….SAP NetWeaver 7.3: Release Restrictions and Limitations
MAR/08/11…III..Windows only: Check registration of sapevents.dll
DEC/08/10…III..Adjust Start Profile
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
SEP/08/09…I….JSPM NOT to be Used During the Update Process
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
Post a Comment