SAP Basis Tech Supports

Symptom
Errors in the update procedure or in the Support Package Stack Guide for SAP NetWeaver 7.0
Other terms
Update, maintenance, patch, import, correction process, SPS, Support Package Stack, AS ABAP, AS Java, EPC, EP, MI, BI, DI, PI (XI), JSPM, SPAM
Reason and Prerequisites
This is the central note of the Support Packages Stacks for SAP NetWeaver 7.0.
Solution

Contents
I/ …. General Information
II/ … Tools to import/apply Support Package Stacks
III/ .. Corrections to the SP Stack Guide

Change log
DATE…….TOPIC….SHORT DESCRIPTION
———————————————————————–
18/MAR/08…III…..IBM i5/OS: SAP Kernel and IGS are updated manually
15/JAN/08…III…..ST22: Many shortdumps “LOAD_PROGRAM_NOT_FOUND”
11/JAN/08…III…..MaxDB only: TASK LIMIT error
28/NOV/07…III…..IBM DB2 for z/OS: Conversion currently not possible
12/SEP/07…III…..PI/XI SPS13: SDM aborts with signal SIGSEGV
30/MAY/07…III…..SPS11: Deployment failure with CAF
23/MAY/07…III…..SPS12: Patch level of MaxDB
05/MAR/07…III…..BI Java SPS11
05/DEC/06…III…..EP SPS10: Deployment failure of SAP EU 7.00
25/OCT/06…III…..UME properties interrupted after an update
10/OCT/06…III…..Securing CAF UI configuration files
04/OCT/06…III…..SPS09: KMC update on Oracle aborts due to a Java Dictionary issue
19/SEP/06…III…..SPS09: BI post-configuration using CTC
30/MAY/06…III…..Updating a Java system with Dialog Instances
10/MAY/06…III…..Dual stack system: JSPM restarts the ABAP part
10/APR/06…III…..SPS07: JSPM hangs on while starting the J2EE Engine
12/JAN/06…III…..SPS05: Deployment failure with CAF EU SPS05
16/DEC/05…III…..SPS05: IGS patch file missing in the download
06/DEC/05…III…..SPS05: Error during the CAF deployment
24/OCT/05…III…..Information on update to SPS04

I/ General Information

The Support Package Stack Guide for SAP NetWeaver 7.0 will be available as of SP Stack 05 on the scheduled release date at http://service.sap.com/maintenanceNW70.
The current versions of the SAP NetWeaver 7.0 SP Stack Guide:
SPS05:1.01SPS06:1.01SPS07:1.01SPS08:1.01SPS09:1.01SPS10:1.01SPS11:1.00SPS12:1.01SPS13:1.00SPS14:1.01SPS15:1.00SPS16:1.01SPS17:1.00SPS18:1.00SPS19:1.00

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

II/ Tools to import/apply Support Package Stacks

To import ABAP Support Packages, you use the Support Package Manager (transaction SPAM). For more information, seeSAP Note 822379.
To apply Java Support Packages, you use the Java Support Package Manager (JSPM). For more information, seeSAP Note 891983.

III/ Corrections to the SP Stack Guide

———————-<I031257, 18/MAR/08>—————————–
If your operating system is IBM i5/OS, you must update the SAP Kernel and SAP IGS manually. To update the kernel, proceed as described in SAP Note912575. To update the IGS, proceed as described in SAP Note937000.
———————-<D022642, 15/JAN/08>—————————–
After applying SPS14 or Kernel 700 patch level 133 to an ABAP system, in transaction ST22 many short dumps of type “LOAD_PROGRAM_NOT_FOUND” may occur with the following short text:
Program “SAPLSALI” not found.
You must update to at least Kernel 700 PL135 or higher once it is available on SAP Service Marketplace. For more information, see SAP Note1105125.
———————-<D024848, 11/JAN/08>—————————–
When applying Support Packages to a Java system with MaxDB as the underlying database, the system may issue a TASK LIMIT error if the configured number of database sessions (parameter MAXUSERTASKS) is no longer sufficient. To prevent this, proceed as follows prior to starting the update procedure:
Check the value of the MAXUSERTASKS database parameter.
The following rule of thumb applies for setting the MAXUSERTASKS value:
MAXUSERTASKS = 2* <number of work processes> + 4
If your value of MAXUSERTASKS was set to a lower number, change it according to this formula (at least 85 is recommended) and restart the database. For more information, see SAP Note 757914.
———————-<D020040, 28/NOV/07>—————————–
When applying Support Packages to a Java system on IBM DB2 for z/OS, the JSPM may abort with the following error message:
Info: E R R O R ******* (DbModificationManager)
Info: … dbs-Error: Table … Conversion currently not possible
SeeSAP Note 989868for details and workaround.
———————-<D037666, 12/SEP/07>—————————–
When updating PI/XI system to SPS13, and JVM from IBM is used, SDM may crash due to JVM errors. SeeSAP Note 1043512and1024539for workaround and recommended settings.
———————-<D037666, 23/MAY/07>—————————–
When updating to SPS11, you may encounter deployment failure. If the
error message resembles (java.lang.NoClassDefFoundError:javax/jdo/spi/PersistenceCapable), seeSAP Note 1059751for workaround.
———————-<D037666, 23/MAY/07>—————————–
When updating an ABAP system to SPS12, if the underlying database is
MaxDB 7.6.xx, please update the MaxDB to at least the version 7.6.0.36 first, before you can apply SPS12 to your SAP system. SeeNote 649814on how to update MaxDB.
———————-<D037666, 05/MAR/07>—————————–
The SPS11 PL0 for the Usage Type BI Java inadvertently contains errors that have already been fixed with one of the higher Patch Level of SPS09or SPS10, respectively. You must directly apply the PL1 or higher of SPS11. SeeSAP Note 1033468for more details.
———————-<D037666, 05/DEC/06>—————————–
When updating your EP system to SPS10, the deployment of the software Component SAP EU 7.00 might fail. SeeSAP Note 1006153for more details and workaround.
———————-<D037666, 25/OCT/06>—————————–
The UME user mappings are interrupted after the update of systems based on Application Server Java which are installed using SR0/SR1 versions of the NetWeaver installation tool (SAPinst) due to UME encryption settings. One indication is that pages are rendered incorrectly.
You can correct this error either before or after the update as described inSAP Note 984683.
———————-<D037666, 10/OCT/06>—————————–
If you have developed CAF applications in the system to be updated, you must back up the UI configuration files before the update takes place by downloading the configurations of all UIs fromhttp://<host>:<port>/caf -> User Interface Configuration -> Repository Backup.
After the update process, you can restore all configurations by uploading the configuration files athttp://<host>:<port>/caf -> User Interface Configuration -> Repository Restore.
———————-<D037666, 04/OCT/06>—————————–
When updating a Java system with EP, the deployment of KMC components on Oracle aborts due to an error of Java Dictionary, implement the workaround described inSAP Note 978042.
———————-<D037666, 19/SEP/06>—————————–
When configuring BI using CTC template after the update to SPS09, you might encounter problems. SeeSAP Note 923359for workaround.
———————-<D037666, 30/MAY/06>—————————–
When updating a Java system with dialog instances from SPS06 or lower SP stacks, an error could occur during starting JSPM. SeeSAP Note 941627for workaround.
——————<changed I044400, 08/MAY/08>———————–
———————-<D037666, 10/MAY/06>—————————–
When applying a Support Package Stack to a Java system, JSPM will restart the system to make the changes effective. In case of a dual stack system (AS ABAP + AS Java), the ABAP part will only be restarted when JSPM is updating the SAP kernel and IGS.
————————<I031420, 10/APR/06>—————————
When updating the NetWeaver AS Java to SPS07 on Windows platforms, JSPM cannot restart the engine under some circumstances due to wrong starting parameters of the CCMSR a agent.SeeSAP Note 933687for the solution.
———————-<D037666, 12/JAN/06>—————————–
SPS05: Under some circumstances the update to SPS05 fails upon the deployment of the software componentCAF EUwhich is included in the usage type EP. In this case you must apply the patch at least PL 2 of CAF EU SP05 which can be downloaded at service.sap.com/patches -> Enter by Application Group -> SAP NetWeaver -> SAP NETWEAVER -> SAP NETWEAVER 7.0 (2004S) -> Enter by Component -> Enterprise Portal (EP) -> CAF EU 7.00 -> #OS independent. Proceed as follows:
1. Copy the downloaded patch to the JSPM inbox.2. Choose the buttonNew Deploymentand select the optionSingle Support Packages.3. In the subsequent screen choose the appropriate patch level of the software component CAF EU in the drop-down listTarget SP Leveland choose the buttonNext. (Skip all other components that has not been deployed yet.)4. If the specified deploy queue is appropriate, chooseNextto start the deployment.5. After the patch has been applied, you can restart the stack update with JSPM by choosing the buttonNew Deployment. JSPM will deploy the SPs of the remaining SCs.
———————————————————————–
———————-<D037666, 06/DEC/05>—————————–
IGS patch file is not included in the set of the stack download for SPS05. You have to download it separately on the SAP Service Marketplace at service.sap.com/patches -> Entry by Application Group -> SAP NetWeaver -> SAP NETWEAVER -> SAP NETWEAVER 7.0 (2004S) -> Entry by Component -> Application Server Java -> SAP IGS 7.00.
The patch file name is IGS.SAR, not as stated in the SP Stack Guide.
———————————————————————–
———————-<D037666, 06/DEC/05>—————————–
During the update to SPS05 of the Java stack, JSPM aborts upon the deployment of the component CAF due to a missing deploy-time dependency. SeeNote 903609for workaround.
———————————————————————–
———————-<D037666, 24/OCT/05>—————————–
After the installation of the SAP NetWeaver Application Server 7.0
(2004s), the AS-ABAP is of the SP level 0. You must apply the Support Packages of all relevant software components up to the SP level 04 immediately. The update includes the following components:
SAP Kernel – Kernel patch level 22SAP BASIS 7.00 – SP04SAP ABA 7.00 – SP04BW 7.00 – SP04PI_BASIS 2005_1_700 – SP04
In case of upgrade, you should include the Support Packages of the components above with the upgrade procedure.
———————————————————————–