3377476 - Problems in SUM phase PREP_GENCHECKS/NTACT_CHK, etc.

Your SUM upgrade stops in phase PREP_GENCHECKS/NTACT_CHK or another similar phase attempting database operations via the transport program (tp).

Some other example phases where you may face similar problems include:

• MAIN_SHDPREPUT/NTACT_ALTNT_PRE
• MAIN_SHDRUN/ALTNTAB_FILL
• etc.

Checking the upgrade tracing from <DIR_PUT>/log you may notice tracing similar to the following:

PHASE_NTACT.ELG (.ELG file name will differ based on problem phase)

#==============================================================================================#
# Find the detailed information in log '<check ID>_NTACT_CHK.<SID>':
#==============================================================================================#

pid 6708 on <application server host> (<sid>adm)
<NO EXIT CODE FOUND - PROGRAM ABORTED?>

#==============================================================================================#
# Find the detailed information in log '<check ID>_NTACT_CHK.<SID>':
#==============================================================================================#

3 ETP000 completed nt read: (T/F : L/J)
3 ETP000Xread nt "<nametab name>":
3 ETP000 completed nt read: (T/F : J/J)
3 ETP000X --------------- DB-COMMIT() ---------------
2 ETP000  --------------- DB-ROLLBACK() ---------------
2AETP344 sqlerror "-10807" occured at location "LOC089"    (object "DDNTT")
1 ETP111 exit code           : "12"

TP.<number>

SAPup> Starting subprocess with PID 28608 in phase 'NTACT_CHK' at 20230825200107
...
EXECUTING <DIR_PUT>/exe/tp ntaction ntop=CHKANT <SID> pf=<DIR_PUT>/var/DEFAULT.TPP intdel=YES -Dntact_timecmp=no protyear=71 protsuffix=NTACT_CHK fromtabname=OIB_CONV_UOM totabname=P02_ZVB_TYPE_WORKED_15
This is tp version 381.491.14 (release 789, unicode enabled)
tp finished with return code: 12
meaning:
  A tool used by tp aborted
SAPup> Process with PID 28608 terminated with status 12 at 20230825200500!

---

If you follow 777565 > 3. Activating and controlling the tp trace to create file tp_trc_desc with contents level:4 in the runtime directory of tp (<DIR_PUT>/tmp), then you may see tracing similar to the following:

<DIR_PUT>/tmp/dev_trc_<trace number>

[     dev trc,00000]    sql> FETCH_CURSOR {rows=10922}
                             &R/3&&10922&10&
[     dev trc,00000]      CURSOR C_0010 FETCH (xcnt=10922) on connection 0
[     dev trc,00000]      next() of C_0010, rc=0
[     dev trc,00000]    Tue Sep 19 19:42:07 2023
[     dev trc,00000]      fetch() of C_0010, #rec=32, rc=1, rcSQL=-10807
[     dev trc,00000]      2: proc=0, cpu=0, mem=0
[     dev trc,00000]      SERVER_PROCESSING_TIME of C_0010 = 0
[     dev trc,00000]      SERVER_CPU_TIME of C_0010 = 0
[     dev trc,00000]      SERVER_MEMORY of C_0010 = 3511932
[     dev trc,00000]      STATEMENT HASH of C_0010 = c016ef31646cc802f6853be89d67cbad
[dbsdbsql.cpp,00000]    *** ERROR =>   fetch() of C_0010, #rec=32, rc=1, rcSQL=-10807
[     dev trc,00000]     -> SetSdbDbslCA(errcode=-10807)
[     dev trc,00000]    sql> LEAVE_SQL_STMT {rows=0}
                             &R/3&0&-10807&32&c016ef31646cc802f6853be89d67cbad&
[dbslsdb.cpp ,00000]    *** ERROR => FETCH C_0010 on connection 0, rc=-10807
[     dev trc,00000]    SQLCODE    : -10807
[     dev trc,00000]    SQLERRTEXT : Connection down: [89006] System call 'recv' failed, rc=110:Connection timed out {10.201.16.14:40414 \
[     dev trc,00000]                 -> 10.201.16.41:30298}
[     dev trc,00000]     -> SetSdbDbslCA(errcode=-10807)
[     dev trc,00000]     -> deactivate_stmt(C_0010,da_p=5627dba52260,rc=99)
[     dev trc,00000]    sc_p=5627ddb21628,no=10,idc_p=(nil),con=0,hit=3,cnt=4,act=1,slen=145,smax=256,#vars=3,stmt=5627de016688,#tabs=0,tables=
[     dev trc,00000]    prepared=0,lastPrepareTime=20230919193818,nativeSQL=0,ignoreStmtId=0
[     dev trc,00000]    statementHash=c016ef31646cc802f6853be89d67cbad
[     dev trc,00000]    SELECT "TABNAME" , "CRTIMESTMP" , "TABTYPE" , "TABFORM" FROM "DDNTT~" WHERE "TABNAME" > ? AND "TABNA\
[     dev trc,00000]    ME" < ? AND "TABNAME" >= ? ORDER BY "TABNAME";
[     dev trc,00000]     -> StmtCacheFree(DBSL:C_0010)
[     dev trc,00000]      CURSOR C_0010 CLOSE all resultsets on connection 0
[     dev trc,00000]    sql> CLOSE_CURSOR
                             &R/3&&10&

---

If your database platform is SAP HANA, you may see indexserver service tracing similar to the following:

[9120]{-1}[-1/-1] 2023-09-24 07:13:45.352823 w Basis            LttImportProvider.cpp(00490) : Real time jump was detected (1168758150). HANA timer will try to adjust its time gradually. Inconsistent timing may lead to subtle problems in HANA (such as unexpected timeouts or potential deadlocks). Old timestamp: {m 4426715963789100, r 1695557621858419500, t 4426715963789100@0, td 200}; new timestamp: {m 4426716963826450, r 1695557624027215000, t 4426716963826450@0, td 100}.

Important Notes: 

• Depending on the nature of the timing issue, the above tracing examples may or may not be present; please see the Cause section for more information.
• Depending on the nature of the timing issue, the affected SUM phase(s) may proceed after repeated phase attempts.
  • SAP recommends that you investigate your landscape for timing inconsistencies and rectify any misconfiguration. Do not ignore the issue and proceed with the SUM upgrade.

• SAP NetWeaver
• Software Update Manager (SUM)

tp, SUM, ntaction, nametab, tmp, NTACT_CHK, NTP, network time protocol , KBA , BC-UPG-TLS-TLA , Upgrade tools for ABAP , HAN-DB , SAP HANA Database , BC-CTS-TLS , Transport Tools , Problem