SAP Basis Tech Supports

Symptom
This note provides information about problems that can occur when you use the Support Package Manager to import Support Packages for ABAP components. On the initial screen of the Support Package Manager, choose the ‘i’ button to find more information on the Support Package Manager.
Caution: This note is regularly updated to the latest status. Therefore always download the latest version from SAP Service Marketplace!
You may have to carry out a SPAM/SAINT update before you can import a certain Support Package. In turn, a SPAM/SAINT update may require a certain R3trans or tp version to be installed in your system. This note also tells you if a SPAM/SAINT update, R3trans or tp is required.
Note also that, due to the Support Package stack concept, dependencies can be defined between the different Support Package types (for example, BW Support Package SAPKW71001 requires Basis and ABA Support Packages SAPKB71001 and SAPKA71001). You will find details about the Support Package stack concept and previously defined Support Package stacks on SAP Service Marketplace at http://service.sap.com/sp-stacks.
Basis Support Packages may also require SAP kernels with a minimum patch level. No dependencies have been defined as yet.

Other terms
OCS, SPAM, SPAM/SAINT UPATE, CONFLICT RESOLUTION TRANSPORT, SUPPORT PACKAGE, CRT, LOAD_PROGRAM_LOST, SAPSQL_SELECT_WA_TOO_SMALL, SAPSQL_WA_TOO_SMALL, XPRA_EXECUTION, TP_FAILURE, TESTIMPORT, DDIC ACTIVATION

Change history
- 16.12.2008: Error in the DDIC activation program – see Note 1283197
- 16.12.2008: SAPKB71004: Termination during DDIC activation
- 16.12.2008: Test import errors that you can ignore are no longer listed in this note because, as ofSPAM/SAINT Version 0032, the system recognizes and ignores these automatically during the import. As ofSAPM/SAINT Version 0032, if the system reports test import errors, youcannot ignorethese and youmustexamine them.
- 15.12.2008: SQL Server 2008 database: Import error if dbsl-lib- is obsolete
- 18.07.2008: When you import SAP_BW Support Packages, the BI Content is no longer available.
- 18.07.2008: Implementation of Notes 1086728 and 1142128 to prevent problems in SPAU
- 18.08.2008: Database DB2/DB6: SQL error -107 in the phase IMPORT_PROPER
- 18.07.2008: Long runtime of the import phase CLEAR_OLD_REPORTS
- 04.03.2008: To avoid DDIC activation errors, implement the corrections contained in Note 1113868.
- 04.03.2008: SPAM/SAINT Version 0026: Long running background job when you import Support Packages
- 04.03.2008: General note about errors in the phase XPRA_EXECUTION
- 04.03.2008: SAPKB71003, SAPKB71004: Test import error in SAPKB71004
- 04.03.2008: SAPKNA7106: Error in the phase ABAP_GENERATION
- 29.11.2007: SAPKB71002, SAPKB71003: Termination in phase XPRA_EXECUTION
- 29.11.2007: SAPKB71003: Administrative activities in the Web service configuration must be carried out.
- 29.11.2007: SAPKW71002, SAPKW71003: Test import error in SAPKW71003
- 25.05.2007: SAPK-10003INA1SABAP: Termination in XPRA_EXECUTION phase
- 04.04.2007: SAPKNA7101: Termination in XPRA_EXECUTION phase
- 04.04.2007: Note was created again
SAP recommendation
We strongly recommend that you always import the latest version of the SPAM/SAINT update before you import any other Support Packages.
We recommend that you download the latest versions of the tp and R3trans executables from SAP Service Marketplace (see Note 19466).
V3 update entries:Process your V3 update entries before you import Support Packages. Otherwise, there is a risk that you will no longer be able to update the update entries if changes in the interface structures of the V3 update modules are delivered by Support Packages. As of SPAM/SAINT Version 0026, the Support Package Manager checks whether there are any open orders and you are then informed of this.
If you are using several application servers, make sure that profile parameterrdisp/bufrefmodeis set tosendon,exeauto, and if you are using only one application server, make sure that the profile parameter is set tosendoff,exeauto. Otherwise, you only have the option of executing the “/$sync” command to make the Support Package changes become effective.

Reason and Prerequisites
The problem is generally caused by a program error or the Support Package type.

Solution
1.SPAM/SAINT updatesSymptom: When you import the SPAM/SAINT update, a range of different runtime errors may occur:LOAD_PROGRAM_LOSTLOAD_TEXTPOOL_LOSTSAPSQL_SELECT_WA_TOO_SMALLSAPSQL_SELECT_TAB_TOO_SMALLSAPSQL_WA_TOO_SMALLDDIC_STRUCLENG_INCONSISTENTRUNT_ILLEGAL_SWITCH
These errors occur because the source code of the Support Package Manager is modified by the import during the run. LOAD_PROGRAM_LOST and LOAD_TEXTPOOL_LOST occur if the ABAP load or text elements are to be loaded back into the local buffer and there is a different version in the database.
However, SAPSQL_SELECT_WA_TOO_SMALL, SAPSQL_SELECT_TAB_TOO_SMALL, SAPSQL_WA_TOO_SMALL, DDIC_STRUCLENG_INCONSISTENT and RUNT_ILLEGAL_SWITCH occur if changes are made on the SPAM/SAINT data structures with the SPAM/SAINT update.
Solution: None of these errors will occur again if you restart the Support Package Manager (transaction SPAM) and continue to import the SPAM/SAINT update.SPAM/SAINT Version 0026:
Symptom: When you import Support Packages with SPAM/SAINT Version 0026, the system schedules an unnecessarily long background job (SAPRUPGM). If you import several Support Package queues in succession, deadlocks may occur that block all background processes.
Solution: Implement Notes 1132422 and 1138351 to ensure an optimized runtime of the background job SAPRUPGM and avoid deadlocks.2.All Support PackagesAvoiding DDIC activation errors when importing Support Packages
To avoid DDIC activation errors when you import Support Package queues (especially long queues), you must implement the following note BEFORE you implement the corrections.
1113868″Activation error due to an object that does not exist”
Alternatively, check whether you have already implemented this notes as part of a Basis Support Package.An error in the DDIC activation program causes cluster tables to be converted.
Symptom: When you activate DDIC objects, information in runtime objects may be lost in certain circumstances. As a result, cluster tables are converted. This is incorrect.
Solution: See Note1283197and implement the correction instructions specified in it before you import Support Packages.Procedure for termination in the phase XPRA_EXECUTION
Symptom: The importing of Support Packages terminates in the phase XPRA_EXECUTION with return code 0012. In the related import log, you are referred to the job log of the XPRA job, in which runtime errors (for example, SYNTAX_ERROR) are listed as the cause of the termination.
Solution: It is possible that the errors are caused by note corrections that were implemented before you imported the Support Packages and that were partially deimplemented when you imported the Support Package queue. You can correct such problems by performing a modification adjustment and by implementing the notes that are still valid (yellow or green traffic light in SPAU) again. The modification adjustment is already prepared at this point and it can be called easily in the Support Package Manager by choosing the menu path ‘Extras’->’Modification Adjustment’.
To avoid such problems when you subsequently import in the production system, you can include the modification adjustment transports that were created in the development system in the Support Package queue. For more information, see the online documentation of the Support Package Manager (’i’ button).Changes that are contained in obsolete notes are completely removed.
Symptom: After you import Support Packages, changes to Web Dynpro objects and enhancement objects are removed when you perform the modification adjustment.
Solution: Before you import Support Packages, implement the corrections from Notes 1086728 and 1142128 in your system.
If you already are in the process of performing the modification adjustment and the system offers Web Dynpro objects or enhancement objects for removal, cancel this process and open a problem message under the component BC-UPG-NA.Database DB2/DB6: Termination with SQL error -107 in IMPORT_PROPER
On DB2/DB6, you can install systems that are based on SAP NetWeaver 7.1 with the options “Row Compression” and “Deferred Table Creation”. In systems that have been installed with these two options, you must implement the corrections that are contained in Note 1126127 before you import Support Packages. Otherwise, terminations may occur in the phase IMPORT_PROPER due to SQL error -107.Long runtime of the phase CLEAR_OLD_REPORTS
Symptom: When you use the downtime-minimized import mode, the phase CLEAR_OLD_REPORTS has a long runtime.
Solution: In transaction SE11, create a non-unique index (for the table REPOSRC) with the name SPM across the fields R3STATE and PROGNAME (in this sequence). By default, this index is delivered with Basis Support Package SAPKB71006 (see Note 1137503).SQL Server 2008 database: Import error if dbsl-lib- is obsolete
Symptom: For more information, see Note 1260968.
Solution: To avoid import errors in SQL Server 2008, you must upgrade the status of dbsl-lib to at least the status described in Note 1152240 before you import Support Packages. Dbsl-lib is available on SAP Service Marketplace and has the description lib_dbsl_<patch>-<xxxxxx>.sar. Note 19466 contains information on downloading kernel patches.
3.Basis Support Packages (SAP_BASIS component)Database DB2-z/OS: Termination with SQL error -670 in IMPORT_PROPER
The activation of the table PRTTEST fails in the phase IMPORT_PROPER with SQL error -670.
Solution: Before you import Support Packages in systems with the source level SAPKB71002 or SAPKB71003 you must implement the corrections in Note 1239921.SAPKB71002 – SAPKB71003
Symptom: If you import the Basis Support Packages SAPKB71002 and SAPKB71003 in a queue, the import terminates in the phase XPRA_EXECUTION with a return code 0008. The log of Support Package SAPKB70003 contains the following error message:
Data Object “AC0A8B89F4447942B5DFEE753F9420C0″ does not exist
Errors occurred during post-handling “SMMW_BEADP_AFTER_IMPORT”
“SMMW_BEADP_AFTER_IMPORT” belongs to package “S_MMW_GBE_ADAPTER”
The errors affect the following components:
“BC-MOB-DOE-BEI” (”Data Orchestration Engine – Back-End Integration”)
Solution: The solution with an allow file for ignoring the problem is described in Note 1082073.SAPKB71003
Note: Support Package SAPKB71003 provides new functions in the areas Web service runtime, Web service configuration, and Web service monitoring. To use these new functions, you must carry out several administrative activities. More information is available at:
http://help.sap.com -> SAP NetWeaver -> SAP Netweaver 7.1 -> Support Package Stack 03 -> System Administration -> Technical Operations Manual -> Administration of SAP NetWeaver IT Scenarios -> Enabling Enterprise Services
The information is also available in the document attached to this note.SAPKB71003 – SAPKB71004
Symptom: If the Support Packages SAPKB71003 and SAPKB71004 are imported together in a queue, an error occurs in the TEST_IMPORT step in Support Package SAPKB71004. The following error message is displayed in the test import log:
Function TREX_EXT_PROCESS_NLI_SEARCH (TREX_EXT_NLI 02) does not fit
into the existing function group ((TREX_EXT_TM 17))
Solution: You can ignore this error by choosing ‘Extras’->’Ignore test-import error’. The error will not occur during the later import.SAPKB71004
Symptom: When you import the Support Package SAPKB71004, DDIC activation terminates. The system displays the following error message in the activation log:
SEEF_BASE 003: Internal error: Enhancement
tool not found.
Solution: To avoid the error, implement the corrections contained in Note 1254808 before you import the Support Package.
If the error has already occurred, contact SAP Support under the component BC-DWB-TOO-ENH.
Recommended queues:
Based on the remarks above, we recommend the following Basis Support Package queues:
SAPKB71001 – SAPKB700.. (highest available Basis Support Package).
You can define shorter queues but you must pay attention to the split points.
These recommended queues only apply if you have not installed any add-ons or do not need to incorporate any CRTs into the queue. Otherwise, you need instructions on optimal or permitted queues from those people who produce the add-ons or CRTs used.
4.ABA Support Packages (SAP_ABA component)
5.BW Support Packages (component SAP_BW)All SAP_BW Support Packages
Symptom: After you import SAP_BW Support Packages, all transformations of SAP BI Content are no longer available.
Solution: Implement the corrections from Note 1171293.
If the problem has already occurred in your system, create a problem message under the component BW-WHM-DST-TRF.SAPKW71002 – SAPKW71003
Symptom: If you import the BW Support Packages SAPKW71002 and SAPKW71003 together in a queue, an error occurs in the step TEST_IMPORT for Support Package SAPKW71003. The test import log of Support Package SAPKW71003 contains the following error message:
Function RSDDTREX_INDEX_CHECK (RSDDTREX_CHECK 01) does not fit
into the existing function group ((RSDDTREX 06))
Solution: You can ignore this error by choosing ‘Extras’->’Ignore test-import error’. The error will not occur during the later import.
Recommended queues:
Based on the remarks above, we recommend the following Basis Support Package queues:
SAPKW71001 – SAPKW710.. (highest available BW Support Package)
You can define shorter queues but you must pay attention to the split points.
These recommended queues only apply if you have not installed any add-ons or do not need to incorporate any CRTs into the queue. Otherwise, you need instructions on optimal or permitted queues from those people who produce the add-ons or CRTs used.
6.Support Packages for SAP_APSAPKNA7101:
Symptom: When you import the SAP_AP Support Package SAPKNA7101 (and other Support Packages for A1S-relevant components), the import terminates in the XPRA_EXECUTION phase with a return code 0012. The log shows the following error message:
Program terminated (job: RDDEXECL, no.: …)
See job log
The job log of the RDDEXECL batch job shows:
Incorrect call of RSTG
Job cancelled
or only:
Job also cancelled due to process termination. See the
system log
Solution: Kernel 7.10 patch number 13 corrects this problem.
To prevent this problem, install the corrected kernel before you import the Support Package.
If the problem has already occurred, you may be able to correct it by installing the corrected kernel version. Alternatively, as a workaround, you can set therdisp/bufrefmodeprofile parameter to the valuesendoff/exeauto(when you change the parameter, you will have to restart the system). In an ABAP system that only has one instance, this parameter is recommended. In an ABAP system that has several instances, you should reset this parameter after you import the Support Package (tosendon/exeauto). In this case, you must also shut down all of the instances except for the central instance, since the system no longer writes any synchronization records. This may lead to inconsistencies in between the instances.SAPKNA7106
Symptom: The importing of SAP_AP Support Package SAPKNA7106 terminates in the phase ABAP_GENERATION. The following error message is displayed in the log:
Program /ISPCD/CL_CHANGE_DOCUMENT_PRX=CP, Include /ISPCD/CL_CHANGE_DOCUMENT_PRX=CM001: Syntax error in line 000064
Solution: Note 1097691 explains the reasons for this error. You can ignore the error by choosing ‘Extras’ -> ‘Ignore generation error’. You can then continue the implementation.7.Support Packages for A1S_ABAPSAPK-10003INA1SABAP
Symptom: When you import the SAPK-10003INA1SABAP Support Package, the import terminates in the XPRA_EXECUTION phase with a return code 0012. The log shows the following error message:
Program terminated (job: RDDEXECL, no.: …)
See job log
In turn, the job log of the RDDEXECL shows that the termination was caused by the SYSTEM_NO_ROLL runtime error.
Reason: This runtime error is caused by a very high memory consumption, which, in turn, was caused by a kernel error.
Solution: As long as no corrected kernel version is yet available, use the RSMEMORY report (see also Note 177226) to increase the limits on memory usage. Call the RSMEMORY report in transaction SE38 or SA38 and enter the following values:
- In the third frame (”Other parameters”)
abap/heap_area_nondia: 4000000000
abap/heap_area_total: 6999999488
- in the second frame (”Quota batch/update/spool”)
in line 4 (column “Memory class” = 2) maintain the
“Size” column as 4000000000
Use ‘Copy’ to copy these values.
You can then start to import the Support Package. Note that these changes to the memory parameters are only temporary and the parameters will be reset when you restart the system. If you want to make these settings permanent, enter the profile parameters abap/heap_area_nondia and abap/heap_area_total in the instance profile.