Online Tutorials & Training Materials | STechies.com
Register Login

Add on installation Stops in IMPORT_PROPER phase via SPAM or SAINT

|| 0

Add on installation Stops in IMPORT_PROPER phase via SPAM or SAINT
Stechies

Support Package Applying via SPAM or SAINT Error in IMPORT_PROPER Phase

Not able to overcome when one is applying Support Packages via SPAM or installing an Add-On via SAINT and it stops with an error in phase IMPORT_PROPER (also known as MAIN_IMPORT).

Points for Consideration for Background:

  • SPAM (Support Package Manager) and SAINT (Add-On Installation Tool) are ABAP tools used to import support packages and add-ons respectively.
  • They contain up to 31 phases, listed below (you can also run report RSSPAM10 in SE38 to view this list).
  • The main log files used to investigate actions in SPAM and SAINT are the SLOG (system log), ALOG (action log) and ULOG (user log).
  • In phase IMPORT_PROPER all the repository objects and table entries (not already imported during INACTIVE_IMPORT) are imported. This action is preceded by actions such as table activations and activations of the nametabs (DDIC_ACTIVATION).

There are four sub-steps in phase IMPORT_PROPER:

  • Distribution
  • Conversion
  • Move nametabs
  • Main Import

Distribution: After activation and running logical checks for the new directory structures, the distribution program decides what actions are required to bring the new objects into the running SAP system. Log file: S9.

Conversion: If necessary, changes are made to table structures. Log file: N9.

Move nametabs: The new ABAP runtime objects are put into the active runtime environment, database structures are adjusted if necessary. Log file:69.. Transport tool: pgmvtab.

Main Import: All data is imported. Log file: I9.. Transport tool: R3trans.

Important Points to Be Considered While Resolving Errors:

  • Never manually handle the buffer file located in ../trans/buffer/ location!
  • Never use manual tp commands on the OS level to try to fix or import Support Packages! (for example "tp R3I ..." or "tp IMPORT ...")
  • Don't import regular change requests while SPAM or SAINT are running!
  • If possible, please import packages during off business hours, to avoid conflicts in system objects being locked by end users!
  • Always have tp and R3trans tools up-to-date!
    websmp208.sap-ag.de/swdc
    Support Packages and Patches (on the left menu)
    Browse our Download Catalog
    Additional Components
    SAP Kernel
    #Database independent
    --> get the latest tp and R3trans patches
  • Always have your database patched and tuned according to its documentation!
  • Don't run the RDD* jobs manually! (see the 'Resolution' section, point #2, for problems of this nature)

Steps to Solve Various Error Messages while applying Support Packages via SPAM or installing an Add-On via SAINT:

  • The analysis should always start on the tool itself (SPAM or SAINT), where you'll find the main error information. For example: (there are many other "Reason for error" messages, different return codes (usually 8 or 12) and different "Error message").
  • The next step is to check the system log (SLOG), action log (ALOG) and the user log (ULOG) for the root cause of the error. (please find the relevant logs from all SPAM/SAINT phases listed in #1846111).
  • The SLOG is the main log file. A normal import should log entries similar to this.
  • The same behavior is expected on the ALOG ( the "I" for the action, meaning the MAIN_IMPORT step)

Additional LOG files information:

When errors take place, they're logged on these files with different messages. Please find below common errors logged on SLOG file and their solution:

WARNING: TA not found via index, reading whole buffer.
WARNING: TA SAPK-113AGINDMIS not found via index, reading whole buffer.

Reason: The buffer file was modified during the import by some reason. Hence SPAM/SAINT cannot find the packages on the expected location.

Solution: The manipulation of the buffer is not possible anymore, as this is a file automatically built when handling packages and change requests using the usual SAP tools. The solution is to restore the system from backup to a point in time before importing the queue.

Syntax Errors with object CL_OCS_RT_ANALYSIS

START MAIN IMPORT SOL I 20140411130035 DDIC INHYDSAP027 20140411125755263
Category: ABAP Programming Error
Runtime Errors: SYNTAX_ERROR

ABAP Program:

CL_OCS_RT_ANALYSIS============CP
Application Component BC-UPG-OCS
Date and Time 15.04.2014 12:45:10 Short text

Syntax error in program "CL_OCS_RT_ANALYSIS============CP ".

Error in the ABAP Application Program

The current ABAP program "SAPLSPAM" had to be terminated because it has come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program

"CL_OCS_RT_ANALYSIS============CP " in include
"CL_OCS_RT_ANALYSIS============CM002 " in
line 13:
"Type "OCSRT_TOOL" is unknown"
" "
" "
Class CL_OCS_RT_ANALYSIS,Method GET_XML
Type "OCSRT_TOOL" is unknown

Reason: This syntax error happens during SPAM/SAINT tool update (package SAPKD, like SAPKD73054) because its new code was already updated, but the process was aborted due to some error. Upon restarting SPAM/SAINT update, it fails with this SYNTAX_ERROR dump. that the error is not exclusive to CL_OCS_RT_ANALYS, but it can also happen to other objects like SAPLSTRD, SAPLOCS_ALV_UI, SAPMSPAM, SAPLOCS_EXTIF, among others.

Solution: There are 2 ways to resolve the problem: either transport the object from another system of the landscape that is already on the target SPAM/SAINT level; or restore the system from backup, to a point in time before the error.

Errors related to the background jobs

ERROR: The following call returned with exit code 7:

ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=PRD

ERROR: Background jobs cannot be started.

ERROR: Please check trace file dev_evt.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System PRD. Warning. 20130313163157 :

ERROR: The following call returned with exit code 7:

ERROR: sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=PRD

ERROR: Background jobs cannot be started.

ERROR: Please check trace file dev_evt.

WARNING: (This warning is harmless if no further warnings follow.)

Reason: The system is unable to trigger the batch jobs due to one or more misconfigured system parameters used by sapevt (SAP Event Trigger).

Solution: Please ensure your TMS configuration is fully consistent, by checking all points. After that, repeat the SPAM/SAINT import again.

Temporary File not Accessible related Errors

ERROR: RFC function TRINT_PROGRESS_INDICATOR error: SYSTEM_FAILURE

ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
STOP MAIN IMPORT ABE I 20131115093315 BASIS
V173I239E 20131111153500023
START tp_getprots ABE Y 20131115093315 BASIS
V173I239E 20131111153500023

ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
STOP tp_getprots ABE Y 20131115093316 BASIS V173I239E 20131111153500023

WARNING: 'V173IAA9EsapmnttranstmpN131115.AIE' : cant open (tpfsnam.c:521)

WARNING: 'V173IAA9EsapmnttranstmpN131114.AIE' : cant open (tpfsnam.c:552)

WARNING: 'V173IAA9EsapmnttranstmpN131113.AIE' : cant open (tpfsnam.c:552)

WARNING: 'V173IAA9EsapmnttranstmpN131112.AIE' : cant open (tpfsnam.c:552)

WARNING: 'V173IAA9EsapmnttranstmpN131111.AIE' : cant open (tpfsnam.c:552)
START TBATG CREATION OF EN AIE n 20131115093316 BASIS
V173IAA9E 20131111153500023

ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18

Reason: The transport tools lots momentarily access to the transport directory; or the file system is full; or an intermitent network problem hampers the access to the mountedtrans directory.

Solution: The remote TRANS_DIR (DIR_TRANS) directory should be fully accessible on a non-stop basis. The error above indicate a problem to reach that location - even the smallest of the network hick-ups can cause that. Please make sure the remote NFS mounted /trans directory is permanently accessible to the system where the packages are being imported.

Data File Destroyed

1AETW042 unexpected EOF after "13004675" bytes.
2EETW000 Please contact the SAP support.
4 ETW000 End of Transport (0016).
4 ETW000 date&time: 07.07.2013 - 19:00:35
4 ETW000 2 errors occured.
1 ETP154 MAIN IMPORT
1 ETP110 end date and time : "20130707190035"
1 ETP111 exit code : "16"
1 ETP199 ######################################

Reason: The datafile from a particular package is damaged or corrupted, and R3trans is no longer able to read it. In particular, the error message "unexpected EOF after ... bytes" occurs if the file was transferred incompletely.

Solution: Please go first to transaction SEPS -> menu Inbox -> mark the corresponding package for deletion. Check if that datafile was deleted from ..sapmnttransdata. Then download again the package from SAP Market Place, or transfer it again from another server using a different transfer method. Then goto SPAM/SAINT, menu Packages -> Load Packages -> From Application Server, to reload the package just downloaded/transferred. Lastly, goto menu Utilities -> Disassemblr Support Package -> . This way the new datafile will be made available for import, and you should be able to repeat the phase successfully.

Out of Space on the File System

START MAIN IMPORT QAS I 20120127111557

WARNING: TA SAPKGS6020 not found via index, reading whole buffer

WARNING: /usr/sap/trans/memsr300/log/SAPIE60066.QAS : cant close No space left on device

WARNING: /usr/sap/trans/memsr300/log/SAPIE60067.QAS : cant close No space left on device

ERROR: SAPKE60067 QAS I 0014 20120127132638 SAPUSER
STOP MAIN IMPORT QAS I 20120127132642

ERROR: stopping on error 14 during MAIN IMPORT
START INFORM SAP-SYSTEM OF QAS Q 20120127132642

Reason: The DIR_TRANS location has no space left.

Solution: Free up space on the location. Repeat the phase afterwards.

TP Semaphore File Holding the Import

WARNING: /usr/sap/trans/tmp/SAPKKW70016.BWQ is already in use (180), I'm waiting 2 sec (20130727080344). My name: pid 29393 on sapbwqa1 (bwqadm)

WARNING: /usr/sap/trans/tmp/SAPKKW70016.BWQ is already in use (190), I'm waiting 5 sec (20130727080408). My name: pid 29393 on sapbwqa1 (bwqadm)

Reason: The temporary transport file used by tp was not removed properly on the previous run. TP needs to freely create and handle the file every time tp is called by SPAM or SAINT. Its presence in /tmp directory prevents this.

Solution: Follow the solution described in #12746. That is, to stop SPAM/SAINT, kill any tp and R3trans processes running on the OS level (beware that no ordinary change requests should be being transported in the meantime!), move or delete the file (SAPKKW70016.BWQ on the example above) and then repeat SPAM/SAINT.

Database-related Errors during the Import

For example: as found on this SAPIB70014. log file:

ERROR: stopping on error 12 during MAIN IMPORT stopping on error 12 during MAIN IMPORT tp returncode summary:

TOOLS: Highest return code of single steps was: 12

WARNINGS: Highest tp internal warning was: 0118 standard output from tp and from tools called by tp:
This is R3trans version 6.14
unicode enabled version
2EETW000 sap_dext called with msgnr "1":
2EETW000 db call info
2EETW000 function: db_setget
2EETW000 fcode: RT_GET (0)
2EETW000 tabname: ALMONISETS
2EETW000 len (char): 44
2EETW000 key: MSSAP CRM Monitor Templates for 6.20
2EETW000 ok fetches: 0
2EETW000 last entry:
2EETW000 retcode: 1
2EETW125 SQL error "3106" during "" access: "ORA-03106:
fatal two-task communication protocol error" R3trans finished (0012).

Reason: Database-related error. The main import log file contains the details of the database error. Each database has also its own action log file, which contains more details about the error itself. ORACLE: alert.log; MSSQL: error.log; MaxDB: Knldiag.err for version <= 7.6 or KnlMsgArchive for version >=7.7; HANA: indexserver, nameserverand statisticsserver; DB2: db2diag.log

Solution: Please search on SAP knowledge base, and on the database vendor side for the corresponding error and solution. Repeat MAIN IMPORT phase afterwards.

Error during the conversion of DD Objects

Import phase 'IMPORT_PROPER' (22.03.2014, 10:16:58) Error during executing the tp command 'tp IMPORT all CCD ...' tp return code: '0008' , tp message: 'A tool used by tp produced errors'

tp output: This is tp version 380.16.71 ( 702)

ERROR: stopping on error 8 during TBATG CONVERSION OF DD-OBJECTS stopping on error 8 during TBATG CONVERSION OF DD-OBJECTS tp returncode summary:

TOOLS: Highest return code of single steps was: 8

WARNS: Highest tp internal warning was: 0118

Standard output from tp and from tools called by tp: Details of the error situation can also be found in the import logs Interrupt the import due to an error situation (22.03.2014, 10:16:58) Display detailed informations concerning the error in phase 'IMPORT_PROPER' Abort the import due to an error situation.

Reason: The step to convert a dictionary object (usually a table) stopped due to problems with one of its indexes.

Solution: Check the conversion background jog log N.. There should be an error message similar to 2EEDA128 Index "BBP_PDIGP~SOC" already exists in the database followed by 2EEGT082 "Indice" "BBP_PDIGP-SOC" could not be created". In order to resolve it, go to transaction SE14 --> Object name --> menu DB Request --> Created with Import --> delete the extra index entry. Repeat the phase afterwards. If you then get the error 2EETW104 "" was repaired in this system and must not be imported.

DIR_TRANS/log directory is big and SPAM/SAINT can't write to it type od0np-uax007sapmnttranslogSLOG1436.CRD HALT 20140904105415

ERROR: od0np-uax007sapmnttranslogCRDE909286.CRD : cant close Invalid argument

ERROR: EXIT(16) -> process ID is: 231688

Reason: The /log directory contains so many log files that the tools have problems in indexing and reading it. The same problem can happen with ordinary change requests.

Solution: Please free up some space by moving or deleting old log files. The /log directory is a very important one, and in most of the cases shared between all transport and upgrade tools.

Read Here for More SAP ABAP Tutorials