SAP Knowledge Base Article - Preview

3204136 - Transport import error - sql error: 133 transaction rolled back by detected deadlock

Symptom

  • You are performing a transport import when it terminates with RC 12
  • There is following error in the import logs:

Log File /usr/sap/trans/log/XXXXXXXXXX.<SID>

I1 I2  ED Log Text

           ######################################
           Main import
           Transport request   : XXXXXXXXXX
           System              : <SID>
           tp path             : tp
           Version and release: 381.298.80 781

           sap_dext called with msgnr 1:
              db call info
           function:   db_repo
           fcode:      OPEN_LINE_UPDATE
           tabname:    SOURCE
           len (char): 42
           key:        IFUR_NW7_TEXTVIEW=============IU        AM
           retcode:    1
           sql error:  133 transaction rolled back by detected deadlock: TrexColumnUpdate failed on table 'SAPABAP1:REPOSRC' with error: trans
           action rolled back by detected deadlock: Deadlock detected: owner tid cycle=[(victim) 4757542954, 4757542818], rc=4616
           SQL error 133 accessing  : transaction rolled back by detected deadlock: Trex
           Main import
           End date and time : 20220510162644
           Ended with return code:  ===> 12 <===
           ######################################


Read more...

Product

SAP NetWeaver all versions

Keywords

Deadlock, rollback, autorepeat, REPOLOAD , KBA , BC-CTS-TLS , Transport Tools , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.