SUM tp error in phase TR_CMDIMPORT_FDTASKS

[Former Member]

We are upgrading NW 700 to NW 731 with SUM tool on V7R1.  During step 5.3 Configuration we get this error, which is strange because several earlier transport steps were successful.

EXECUTING /usr/sap/PMD/SUM/abap/exe/tp  pf=/usr/sap/PMD/SUM/abap/var/PCMDIMP.TPP r3i all PMD

This is tp version 380.05.18 (release 721, unicode enabled)

INFO:  XDNLevelTraceSetLocation: Trace set to: XDNTrace.244865.*

This is /usr/sap/PMD/SUM/abap/exe/R3trans version 6.24 (release 720 - 08.07.13 - 20:13:05 ).

unicode enabled version

2EETW169 no connect possible: "maybe someone set invalid values for DIR_LIBRARY ('/usr/sap/PMD/SUM/abap/exe') or dbms_type ('db4')"

/usr/sap/PMD/SUM/abap/exe/R3trans finished (0012).

ERROR: stopping on error 12 during MAIN IMPORT

stopping on error 12 during MAIN IMPORT

Here is the entire TP.ECO log:

SAPup> Starting subprocess with PID 244864 in phase 'TR_CMDIMPORT_FDTASKS' at 20130903092027
    ENV: DIR_LIBRARY=/usr/sap/PMD/SUM/abap/exe
    ENV: ILE_PATH=/usr/sap/PMD/SUM/abap/exe:/usr/sap/PMD/SYS/exe/run:/usr/bin:.
    ENV: LIBPATH=/usr/sap/PMD/SUM/abap/exe:/usr/sap/PMD/SUM/jvm/jre/lib/ppc64/server:/usr/sap/PMD/SUM/jvm/jre/lib/ppc64:/usr/sap/PMD/SUM/jvm/jre/../lib/ppc64:/usr/sap/PMD/SUM/jvm/jre/lib/ppc64/jli:/usr/sap/PMD/SUM/jvm/jre/../lib/ppc64/jli:/usr/sap/PMD/SYS/exe/run:/usr/sap/PMD/hdbclient:/sapdb/clients/PMD/lib/lib64:/sapdb/clients/PMD/lib:/sapdb/programs/lib/lib64:/sapdb/programs/lib
    ENV: PASE_LANG=en_US
    ENV: PASE_LC__FASTMSG=true
    ENV: PASE_LIBPATH=/usr/sap/PMD/SUM/abap/exe:/usr/sap/PMD/SYS/exe/run:/usr/sap/PMD/hdbclient:/sapdb/clients/PMD/lib/lib64:/sapdb/clients/PMD/lib:/sapdb/programs/lib/lib64:/sapdb/programs/lib
    ENV: PASE_LOCPATH=/usr/lib/nls/loc
    ENV: PASE_NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat:/usr/lib/nls/msg/en_US/%N:/usr/lib/nls/msg/en_US/%N.cat
    ENV: PASE_PATH=/usr/sap/PMD/SUM/abap/exe:/usr/sap/PMD/SYS/exe/run:/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:/usr/bin:.:/usr/sap/PMD/hdbclient:/sapdb/clients/PMD/bin:/sapdb/programs/bin
    ENV: PASE_STDIO_ISATTY=N
    ENV: PASE_THREAD_ATTACH=Y
    ENV: PASE_TZ=<EST>5<EDT>,M3.2.0,M11.1.0
    ENV: PASE_USRGRP_LIMITED=
    ENV: PATH=/usr/sap/PMD/SUM/abap/exe:/usr/sap/PMD/SYS/exe/run:/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:/usr/bin:.:/usr/sap/PMD/hdbclient:/sapdb/clients/PMD/bin:/sapdb/programs/bin
    ENV: SAPSYSTEMNAME=PMD
    ENV: dbms_type=db4
    ENV: dbs_db4_schema=R3PMDDATA
    ENV: ILE_DIR_LIBRARY=/usr/sap/PMD/SUM/abap/exe
    ENV: PASE_DIR_LIBRARY=/usr/sap/PMD/SUM/abap/exe
    ENV: DIR_LIBRARY_RMT=/usr/sap/PMD/SUM/abap/exe
    ENV: ILE_DIR_LIBRARY_RMT=/usr/sap/PMD/SUM/abap/exe
    ENV: PASE_DIR_LIBRARY_RMT=/usr/sap/PMD/SUM/abap/exe
    ENV: ILE_LIBPATH=/usr/sap/PMD/SUM/abap/exe

EXECUTING /usr/sap/PMD/SUM/abap/exe/tp  pf=/usr/sap/PMD/SUM/abap/var/PCMDIMP.TPP setsyncmark SAPK-731BHINSAPBASIS buffer=PCMDIMPFD.BUF
This is tp version 380.05.18 (release 721, unicode enabled)
tp finished with return code: 0
meaning:
  Everything OK
SAPup> Starting subprocess with PID 244865 in phase 'TR_CMDIMPORT_FDTASKS' at 20130903092028
    ENV: DIR_LIBRARY=/usr/sap/PMD/SUM/abap/exe
    ENV: ILE_PATH=/usr/sap/PMD/SUM/abap/exe:/usr/sap/PMD/SYS/exe/run:/usr/bin:.
    ENV: LIBPATH=/usr/sap/PMD/SUM/abap/exe:/usr/sap/PMD/SUM/jvm/jre/lib/ppc64/server:/usr/sap/PMD/SUM/jvm/jre/lib/ppc64:/usr/sap/PMD/SUM/jvm/jre/../lib/ppc64:/usr/sap/PMD/SUM/jvm/jre/lib/ppc64/jli:/usr/sap/PMD/SUM/jvm/jre/../lib/ppc64/jli:/usr/sap/PMD/SYS/exe/run:/usr/sap/PMD/hdbclient:/sapdb/clients/PMD/lib/lib64:/sapdb/clients/PMD/lib:/sapdb/programs/lib/lib64:/sapdb/programs/lib
    ENV: PASE_LANG=en_US
    ENV: PASE_LC__FASTMSG=true
    ENV: PASE_LIBPATH=/usr/sap/PMD/SUM/abap/exe:/usr/sap/PMD/SYS/exe/run:/usr/sap/PMD/hdbclient:/sapdb/clients/PMD/lib/lib64:/sapdb/clients/PMD/lib:/sapdb/programs/lib/lib64:/sapdb/programs/lib
    ENV: PASE_LOCPATH=/usr/lib/nls/loc
    ENV: PASE_NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat:/usr/lib/nls/msg/en_US/%N:/usr/lib/nls/msg/en_US/%N.cat
    ENV: PASE_PATH=/usr/sap/PMD/SUM/abap/exe:/usr/sap/PMD/SYS/exe/run:/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:/usr/bin:.:/usr/sap/PMD/hdbclient:/sapdb/clients/PMD/bin:/sapdb/programs/bin
    ENV: PASE_STDIO_ISATTY=N
    ENV: PASE_THREAD_ATTACH=Y
    ENV: PASE_TZ=<EST>5<EDT>,M3.2.0,M11.1.0
    ENV: PASE_USRGRP_LIMITED=
    ENV: PATH=/usr/sap/PMD/SUM/abap/exe:/usr/sap/PMD/SYS/exe/run:/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:/usr/bin:.:/usr/sap/PMD/hdbclient:/sapdb/clients/PMD/bin:/sapdb/programs/bin
    ENV: SAPSYSTEMNAME=PMD
    ENV: dbms_type=db4
    ENV: dbs_db4_schema=R3PMDDATA
    ENV: ILE_DIR_LIBRARY=/usr/sap/PMD/SUM/abap/exe
    ENV: PASE_DIR_LIBRARY=/usr/sap/PMD/SUM/abap/exe
    ENV: DIR_LIBRARY_RMT=/usr/sap/PMD/SUM/abap/exe
    ENV: ILE_DIR_LIBRARY_RMT=/usr/sap/PMD/SUM/abap/exe
    ENV: PASE_DIR_LIBRARY_RMT=/usr/sap/PMD/SUM/abap/exe
    ENV: ILE_LIBPATH=/usr/sap/PMD/SUM/abap/exe

EXECUTING /usr/sap/PMD/SUM/abap/exe/tp  pf=/usr/sap/PMD/SUM/abap/var/PCMDIMP.TPP r3i all PMD
This is tp version 380.05.18 (release 721, unicode enabled)
INFO:  XDNLevelTraceSetLocation: Trace set to: XDNTrace.244865.*
This is /usr/sap/PMD/SUM/abap/exe/R3trans version 6.24 (release 720 - 08.07.13 - 20:13:05 ).
unicode enabled version
2EETW169 no connect possible: "maybe someone set invalid values for DIR_LIBRARY ('/usr/sap/PMD/SUM/abap/exe') or dbms_type ('db4')"
/usr/sap/PMD/SUM/abap/exe/R3trans finished (0012).
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
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
  A tool used by tp aborted
SAPup> Process with PID 244865 terminated with status 12 at 20130903092030!

Thank you,

Margie

[thomas_obermeier · Accepted solution]

Hi Margie,

I've seen cases where this happened due to a mixup of EXT and non EXT executables. Are you sure the executables in SUM/abap/exe are consistent in this respect? Maybe you added an R3trans or tp patch...

HTH

Thomas

[Former Member · Accepted solution]

Hi Thomas - you are exactly correct and it was an R3trans patch.  Interesting thing - the APYSIDKRN allowed me to put on the non-EXT R3trans patch to an EXT kernel, but when I tried to run it again to apply the correct EXT R3trans, it said putting an EXT patch on a non-EXT kernel was not allowed...

Ended up using APSIDKRN with *FULLY option to revert to my original saved kernel and start over with the correct patch.  Wish it would have stopped me from putting the non-EXT patch on the first place.

Thank you,

Margie