2777760 - R3trans runs long on cluster environment - NetWeaver

• On Windows Server 2012, 2012 R2, 2016, or 2019 with enabled Failover Clustering feature, using R3trans or TP command may take long waiting time.
  
• Executables like R3Trans and TP are much slower when called from a server that has Failover Cluster installed than that from a server without Failover Cluster.
• When checking R3trans -x, it will take more than 60 seconds at the beginning of the trace. After this 60 seconds duration, it may finish in a second.
• trans.log
  -->
  4 ETW000 R3trans version 6.24 (release 721 - 02.10.18 - 20:18:10).
  4 ETW000 unicode enabled version
  4 ETW000 ===============================================
  4 ETW000
  4 ETW000 date&time : 01.04.2019 - 01:58:28
  4 ETW000 control file: <no ctrlfile>
  4 ETW000 R3trans was called as follows: R3trans -x -t4
  4 ETW000 trace at level 4 opened for a given file pointer
  4 ETW000 [ dev trc,00000] Tue Apr 01 01:59:31 2019
  
  ......
  4 ETW000 date&time: 01.04.2019 - 01:59:31

Read more...

Windows Server 2012, 2012 R2, 2016, or 2019 with Failover Clustering

SAP NetWeaver 2004 ; SAP NetWeaver 7.0 ; SAP NetWeaver 7.1 ; SAP NetWeaver 7.2 ; SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP enhancement package 1 for SAP NetWeaver 7.0 ; SAP enhancement package 1 for SAP NetWeaver 7.3 ; SAP enhancement package 2 for SAP NetWeaver 7.0 ; SAP enhancement package 3 for SAP NetWeaver 7.0

R3trans, tp, slow, windows, Failover Cluster , KBA , BC-DB-MSS , SQL Server in SAP NetWeaver Products , BC-OP-NT , Windows , Problem