Skip to end of metadata
Go to start of metadata
   

Purpose

The purpose of this page is to provide information for troubleshooting of issues during TABIM_UPG import phase in an upgrade.

 

Always verify the most up-to-date procedures by checking the  SUM Guide. Always have it on hand while performing the upgrade.

Overview

During the TABIM (table import) phase, additional data is loaded in tables that belong to the SAP name range. All SAP table classes S, W, E, C and G are affected by row insertions, modifications and deletions - except for class A, which is protected against row modifications, where only insertions are allowed. The TABIM phase is run through tp and R3trans.


Technical Flow

 


Performance considerations

The number of parallel R3trans processes is a factor that must be considered to speed up theses phases. This feature is named parallelism. Please refer to the following KBAs in order to understand how parallelism works and how to analyse performance bottlenecks on both phases:

#161640 1: Understanding parallelism during the Upgrades, EhPs and Support Packages implementations

#1945399 : Performance analysis for SHADOW_IMPORT_INC and TABIM_UPG phase

Preventive activity on Windows 2012 (R) with Windows Failover cluster :

Apply the Windows Hotfix as described in the SAP note 1823833  - Accessing shares via SMB3.0 can result in long waiting times

Note

Any time during the update procedure, you can increase or decrease the limits that have been specified for the different types of parallel processes.
For some phases, these changes will have an immediate effect.
For example, changing the values for R3trans processes during downtime will influence the phase TABIM_UPG immediately.

For other phases, you have to carry out the change before the corresponding phase is running. For example, the values for parallel background processes during uptime have to be set before the profiles for the shadow system are created and take effect.

In the browser, enter the following internet address: http://<hostname>:1128/lmsl/sumabap/<SID>/set/procpar
Access via Command Line Interface
To access the command line interface in scroll mode (for example, using telnet), enter the following commands :
cd <update directory>/abap/bin
SAPup set procpar gt=scroll

 

Troubleshooting

Logs overview:

Logfiles of SAPup:
TP.ECO or SAPup.ECO
*.ELG                    collected error lines from transport logs.
Logfiles of tp:
ULOG...                tp call inclusive used transport profile,
ALOG<rel>          finished steps (request, return code),
SLOG<rel>          details of tp call.
Logfiles of R3trans:
SAPI*                  (main) import logs,
SAPH*                dictionary import logs.

Main log file of TABIM_UPG:    TABIMUPG.ELG   

Please check the  error message listed and search for solutions in SAP notes and KBAs. 

Symptoms and solutions

 

SUM displayed error or Error in log file
Log file
Solution

Environment: Upgrade to Solution manager 7.2 or CRM 7.0 EHP1,EHP2,EHP3

MAIN IMPORT ERRORS and RETURN CODE in SAPI-702BRINBBPCRM.SID
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3 ETW674Xstart import of "R3TRATTR80215ADE55241DDF8CE636D957DE4033" ...
...
4 ETW000 no shadow table for COMC_ATTRIBUTE
...
2EETW000 Update and insert sequence failed due to conflicting unique indexes on table COMC_ATTRIBUTE (please read OSS note 626915 for details)
or

2EETW000 Update and insert sequence failed due to conflicting unique indexes on table DSYS_PHHEAD_ECD2 (please read OSS note 626915 for details)

1 ETP111 exit code : "8"

 <update_directory>/log/SAPI*.SID

 Please follow the
Regarding table COMC_ATTRIBUTE please follow the
SAP KBA 1872729 - CRM Upgrade fails with error "Update and insert sequence failed due to conflicting unique indexes on table COMC_ATTRIBUTE"

and

 

SAP KBA 2276722 Upgrade fails in SHADOW_IMPORT_INC due to conflicting unique indexes on table C


Regarding table DSYS_PHHEAD_ECD2 please follow the
SAP KBA 1848603 - DSYS_PHHEAD_ECD2 index error during upgrade

Environment: Windows 2012 (R) with Windows Failover cluster

TABIM_UPG phase is running much longer then on earlier upgraded system without cluster
Analysis shows, that the file system access is slower 

<update_directory>/tmp/SAPI* 

Apply the Windows Hotfix as described in the SAP note 1823833 - Accessing shares via SMB3.0 can result in long waiting times

  • 2EETW109 table "/POSDW/LPA_EXDET" does not exist in nametab.
  • The affected object(s) start with /POSDW/.

<update_directory>/log/TABIMUPG.ELG       

SAP KBA 1966709 - Error. Checks after phase MAIN_NEWBAS/TABIM_UPG were negative !

MAIN IMPORT ERRORS and RETURN CODE in SAPICDC731.<SID>
4 ETW000 end of log fragment of child 00008913046
...
4 ETW000 SAPKCDC731           touched.
4 ETW690 COMMIT "128" "4076"
4 ETW000 40261752 bytes read.
4 ETW000 Transport overhead 22.0 %.
4 ETW000 Duration: 11 sec (3660159 bytes/sec).
1AETW064 EOF record is missing. Data file is destroyed.
2EETW000 Please contact the SAP support.
4 ETW000 End of Transport (0016).
4 ETW000 date&time: 15.10.2013 - 14:16:52

UNIX: <update_directory>/log/TABIMUPG.ELG   

SAP note   1927413   : data file corrupt in phase MAIN_NEWBAS/TABIM_UPG
  • Environment:
  • IBM DB2 for Linux, UNIX, and Windows (DB6) version 9.7 or higher
  • Database configuration parameter AUTO_REVAL is set to DEFERRED 
  • Error:
  • The SAP upgrade of your SAP system fails in phase MAIN_NEWBAS/TABIM_UPG with SQL error SQL0727N and the following error text:
    ‘An error occurred during implicit system action type “3”. Information returned for the error includes SQLCODE “-204”, SQLSTATE "42704" and message tokens "<SCHEMA>.<TABLE_NAME>".’
  • The table referenced in the SQL error SQL0727N is the staging table of an ADMIN_MOVE_TABLE operation.
  • For the staging table of an ADMIN_MOVE_TABLE call, the following naming convention applies:
    <TABLE_NAME><HASH_KEY><POSTFIX>
    The <POSTFIX> has to be “s”.  For example: “COMC_CRD_GEN_BWDACwNmUs”  
UNIX: <update_directory>/log/ TABIMUPG.ELG   SAP note 2120907 - SAP Upgrade Fails in Phase MAIN_NEWBAS/TABIM_UPG with SQL0727N, Action Type "3" and SQLCODE "-204"

FAQ (Frequently asked questions) 

 

Related SAP Notes/KBAs 

SAP KBA 2276722 Upgrade fails in SHADOW_IMPORT_INC due to conflicting unique indexes on table C

SAP KBA 1848603 - DSYS_PHHEAD_ECD2 index error during upgrade

SAP KBA 1872729 - CRM Upgrade fails with error "Update and insert sequence failed due to conflicting unique indexes on table COMC_ATTRIBUTE"

SAP note 1823833  - Accessing shares via SMB3.0 can result in long waiting times

SAP KBA 1966709   - Error. Checks after phase MAIN_NEWBAS/TABIM_UPG were negative !

SAP note   1927413   : data file corrupt in phase MAIN_NEWBAS/TABIM_UPG

SAP note 2120907   - SAP Upgrade Fails in Phase MAIN_NEWBAS/TABIM_UPG with SQL0727N, Action Type "3" and SQLCODE "-204"