19 Replies Latest reply: Nov 11, 2011 1:21 PM by Msoro Msororaji RSS

Unable to Release change requests after configuring TMS

Msoro Msororaji
Currently Being Moderated

HI

 

I'm unable to release change requests. I've deleted the TMS configuration & reconfigured thrice but I'm still getting no where  . I've also scheduled RDDNEWPP & RDDTUPP as user DDIC in client 000 and other clients

 

Below are some of the errors I encounter when attempting to release

 

Kindly assist

 

-


 

Release Started        Cancelled releases can be repeated

 

Import steps not specific to transport request

-


Log File:                /usr/sap/trans/log/DEVE922552.DEV

 

 

           ######################################

           Main export

           Transport request   : DEVK922552

           System              : DEV

           tp path             : tp

           Version and release: 372.04.08 700

 

           creation of R3trans (R3trans) process failed: No such file or directory

           Main export

           End date and time : 20111107215445

           Ended with return code:  ===> 230 <===

           ######################################

-


 

TMS monitor -> alert viewer give the result below

 

07.11.11   20:05:50   TMSADM         TMS_PS_READ_PROFILE_FROM_DISK     READ_PROFILE_FAILED    DEV      000

07.11.11   20:04:09   TMSADM         TMS_PS_READ_PROFILE_FROM_DISK     READ_PROFILE_FAILED    DEV      000

 

 

-


/usr/sap/trans/log/SLOG1145.DEV

 

 

2EETP000 fcode:      NT_RDTDESCR

2EETP000 tabname:    TPSTAT

2EETP000 len (char): 6

2EETP000 key:        TPSTAT

2EETP000 retcode:    1

1AETP000 exit in function texitnow

ERROR: EXIT(16) -> process ID is: 8060982

1AETP000 Internal error: EXITNOW doesn't call my_exit()

ERROR: EXIT(16) -> process ID is: 8060982

ERROR: No entry for DEVK922552 in E070 or error during access.

ERROR DEVK922552           DEV E 0230 20111107220120 XXX594      XXX594      DEV 20111107220115     

ERROR: stopping on error 230 during MAIN EXPORT

2EETP000 sap_dext called with msgnr "1":

2EETP000 -


db call info -


2EETP000 function:   db_ntab

2EETP000 fcode:      NT_RDTDESCR

2EETP000 tabname:    TPSTAT

2EETP000 len (char): 6

2EETP000 key:        TPSTAT

2EETP000 retcode:    1

1AETP000 exit in function texitnow

ERROR: EXIT(16) -> process ID is: 7602350

1AETP000 Internal error: EXITNOW doesn't call my_exit()

ERROR: EXIT(16) -> process ID is: 7602350

  • Re: Unable to Release change requests after configuring TMS
    Orkun Gedik
    Currently Being Moderated

    Hi,

     

    Check TPPARAM exist and accessible by <sid>adm user, under /usr/sap/trans/bin. To get detailed information, execute RSTPTEST program and paste the output here.

     

    Best regards,

     

    Orkun Gedik

    • Re: Unable to Release change requests after configuring TMS
      Msoro Msororaji
      Currently Being Moderated

      Thanks for your response

       

      The file TPPARAM  is  non existent thou I'm meant to understand TPPARAM was replaced by TP_DOMAIN_<SAPSID>.PFL after SAP 4.7. 

       

      My transport directory is shared from QAS system via NFS. All the permissions are OK. DEV system is the transport domain controller

      1. su - devadm

      [YOU HAVE NEW MAIL]: No match.

      DEV:devadm 1> ls -ltr /usr/sap/trans/bin

      total 0

      -rw-rw----    1 205      sapsys           34 Nov 08 01:00 TMS_TEST.QAS

      -rw-rw----    1 devadm   sapsys           34 Nov 08 01:02 TMS_TEST.PRD

      -rwxrwxrwx    1 devadm   sapsys         1346 Nov 08 01:13 TP_DOMAIN_DEV.PFL

      -rw-rw----    1 devadm   sapsys         1274 Nov 08 01:13 TP_DOMAIN_DEV.BAK

      -rwxrwxrwx    1 devadm   sapsys          692 Nov 08 01:13 DOMAIN.CFG

      DEV:devadm 2>

       

      1. su - qasadm

      [YOU HAVE NEW MAIL]: No match.

      QAS:qasadm 1> ls -ltr /usr/sap/trans/bin

      total 40

      -rw-rw----    1 qasadm   sapsys           34 Nov  8 01:00 TMS_TEST.QAS

      -rw-rw----    1 smnadm   sapsys           34 Nov  8 01:02 TMS_TEST.PRD

      -rwxrwxrwx    1 smnadm   sapsys         1346 Nov  8 01:13 TP_DOMAIN_DEV.PFL

      -rw-rw----    1 smnadm   sapsys         1274 Nov  8 01:13 TP_DOMAIN_DEV.BAK

      -rwxrwxrwx    1 smnadm   sapsys          692 Nov  8 01:13 DOMAIN.CFG

      QAS:qasadm 2>

      QAS:qasadm 2>

      QAS:qasadm 2> find /usr/sap/trans -type f -name TPPARAM

      QAS:qasadm 3> 

      -


      the ouput of program RSTPTEST from SA38 & SE38  gives me no error( I get green ticks) meaning it is OK

       

      Check Transport Tool                                       08.11.2011  07:05:19

       

             DEV System DEV

       

                 tp Interface

       

                     Host Name             DEV

                     Version               1.80

                     Transport Directory   /usr/sap/trans

                     Logging               On (TPLOG contains 42839 entries)

       

                 Transport Profile

       

                     Path                  /usr/sap/trans/bin/TP_DOMAIN_DEV.PFL

                     Profile               TP_DOMAIN_DEV.PFL is readable

                     Version               Version 0003 (domain DOMAIN_DEV)

       

                 RFC Destination

       

                     Destination           CALLTP_AIX

                     tp Path               /usr/sap/DEV/DVEBMGS01/exe/tp

                     tp Executable         Size: 13.406.585 bytes

                     RFC Ping              Link setup: 126 msec

       

                 tp Call

       

                     RFC Link              tp was started successfully

                     tp Version            372.04.08 (n .ow.unkn)

                     DB Connect            Link to database successful

                     Offline Call          tp started in background

      -


       

      tail -900f /usr/sap/trans/log/DEVE922530.DEV

       

      3 ETP203 Buffer "/usr/sap/trans/buffer/QAS" is writeable

      1 ETP182 CHECK WRITEABILITY OF BUFFERS

      1 ETP110 end date and time   : "20111108060659"

      1 ETP111 exit code           : "0"

      1 ETP199 ######################################

      1 ETP199X######################################

      1 ETP183 EXPORT PREPARATION

      1 ETP101 transport order     : "DEVK922530"

      1 ETP102 system              : "DEV"

      1 ETP108 tp path             : "tp"

      1 ETP109 version and release : "372.04.08" "700"

      1 ETP198

      2 EPU230XExecution of the export pre-processing methods for request "DEVK922530"

      4 EPU111    on the application server: "DEV"

      4 EPU138    in client                            : "260"

      2 EPU235XStart: Version creation of the objects of the request "DEVK922530"

      3 EPU237 Version creation started as update request

      2 EPU236 End: Version creation of the objects of the request "DEVK922530"

      2 EPU231XStart: Adjusting the object directory for the objects of the request "DEVK922530"

      2 EPU232 End:  Adapting the object directory for the objects of the request "DEVK922530"

      2 ETN085 "Adding component vector" " " " " " "

      2 ETN085 "Finished." " " " " " "

      4WETO087 Attribute "EXPORT_TIMESTAMP" can only be assigned once per request

      1 ETP183 EXPORT PREPARATION

      1 ETP110 end date and time   : "20111108060705"

      1 ETP111 exit code           : "4"

      1 ETP199 ######################################

      1 ETP199X######################################

      1 ETP150 MAIN EXPORT

      1 ETP101 transport order     : "DEVK922530"

      1 ETP102 system              : "DEV"

      1 ETP108 tp path             : "tp"

      1 ETP109 version and release : "372.04.08" "700"

      1 ETP198

      1AETP000 creation of R3trans (R3trans) process failed: No such file or directory

      2EETP200 Export with errors, request will not be imported

      1 ETP150 MAIN EXPORT

      1 ETP110 end date and time   : "20111108060710"

      1 ETP111 exit code           : "230"

      1 ETP199 ######################################

       

      Edited by: Msororaji on Nov 8, 2011 9:18 AM

      • Re: Unable to Release change requests after configuring TMS
        Msoro Msororaji
        Currently Being Moderated

        This is what I get when I try to release the change request

        -


        CODE

         

        Log Overview for DEVK922552

         

        DEVK922552              test transports

         

        DEV        System DEV

         

        Checks at Operating System Level         07.11.2011 21:54:38    (0) Successfully Completed

        Pre-Export Methods                       07.11.2011 21:54:40    (0) Successfully Completed

        Export                                   07.11.2011 21:54:45  (230) Canceled

        Checks at Operating System Level         07.11.2011 22:01:12    (0) Successfully Completed

        Pre-Export Methods                       07.11.2011 22:01:15    (4) Ended with Warning

        Export                                   07.11.2011 22:01:20  (230) Canceled

        Checks at Operating System Level         07.11.2011 22:17:59    (0) Successfully Completed

        Pre-Export Methods                       07.11.2011 22:18:01    (4) Ended with Warning

        Export                                   07.11.2011 22:18:06  (230) Canceled

        Checks at Operating System Level         08.11.2011 08:10:29    (0) Successfully Completed

        Export                                   08.11.2011 08:10:31 In process: Requires update

        Pre-Export Methods                       08.11.2011 08:10:31    (4) Ended with Warning

      • Re: Unable to Release change requests after configuring TMS
        Markus Doehr
        Currently Being Moderated

        > DEV:devadm 1> ls -ltr /usr/sap/trans/bin

        > total 0

        > -rw-rw----    1 205      sapsys           34 Nov 08 01:00 TMS_TEST.QAS

        > -rw-rw----    1 devadm   sapsys           34 Nov 08 01:02 TMS_TEST.PRD

        > -rwxrwxrwx    1 devadm   sapsys         1346 Nov 08 01:13 TP_DOMAIN_DEV.PFL

        > -rw-rw----    1 devadm   sapsys         1274 Nov 08 01:13 TP_DOMAIN_DEV.BAK

        > -rwxrwxrwx    1 devadm   sapsys          692 Nov 08 01:13 DOMAIN.CFG

         

        > # su - qasadm

        > [YOU HAVE NEW MAIL]: No match.

        > QAS:qasadm 1> ls -ltr /usr/sap/trans/bin

        > total 40

        > -rw-rw----    1 qasadm   sapsys           34 Nov  8 01:00 TMS_TEST.QAS

        > -rw-rw----    1 smnadm   sapsys           34 Nov  8 01:02 TMS_TEST.PRD

        > -rwxrwxrwx    1 smnadm   sapsys         1346 Nov  8 01:13 TP_DOMAIN_DEV.PFL

        > -rw-rw----    1 smnadm   sapsys         1274 Nov  8 01:13 TP_DOMAIN_DEV.BAK

        > -rwxrwxrwx    1 smnadm   sapsys          692 Nov  8 01:13 DOMAIN.CFG

         

        To me this seems a user ID mismatch. DEV resolves the id to "devadm" whereas QAS resolves the ID of the user to smnadm. 

         

         

         

        Markus

        • Re: Unable to Release change requests after configuring TMS
          Msoro Msororaji
          Currently Being Moderated

          Markus

           

          My QAS & SMN (Solution manager) systems share one host.

          • Re: Unable to Release change requests after configuring TMS
            Markus Doehr
            Currently Being Moderated

            > My QAS & SMN (Solution manager) systems share one host.

             

            Yes - but you're using the SAME user IDs on a shared directory for two different systems?!

             

             

             

            Markus

            • Re: Unable to Release change requests after configuring TMS
              Msoro Msororaji
              Currently Being Moderated

              I have no idea how the host decides which user ID owns the files. For example I've just realised when I changed the transport domain, the new file TP_DOMAIN_PRD.PFL is owned by SMN user smnadm

               

              What is your advice on this ?

              • Re: Unable to Release change requests after configuring TMS
                Markus Doehr
                Currently Being Moderated

                > I have no idea how the host decides which user ID owns the files.

                 

                The host doesn't decide, it's done by you (or by whoever installed the systems) during the installation of the systems using sapinst. If you don't specify the IDs the fist available is taken. If this is done on all systems like this you will run into trouble if you use NFS because depending on which system is looking on the NFS share it will see different owners.

                 

                > What is your advice on this ?

                 

                According to the installation guide the user must be unique in a transport landscape. However, technically it's possible to handle if you make sure, the shared files have a group read and write permission (sapsys) - which should be unqiue across all systems (look like). If you have a chance at some point I'd do a system copy and make sure the IDs are unique.

                 

                To your actual problem: it seems that the DEV system is not finding the transport in table E070.

                 

                Was this working before? If yes, what happened?

                 

                 

                 

                Markus

                • Re: Unable to Release change requests after configuring TMS
                  Msoro Msororaji
                  Currently Being Moderated

                  The TMS was working before. The problem started when another host (similar name with DEV but different IP address) was introduced to the network. It was removed immediately we realised it was the source of our  problem. Since then our transports have never worked

                  • Re: Unable to Release change requests after configuring TMS
                    Markus Doehr
                    Currently Being Moderated

                    I would try the following:

                     

                    - delete all TMS configurations of all systems

                    - choose a domain controller and set it up

                    - add both systems to the domain

                    - create a transport route

                    - create a new test transport and try to release it

                     

                     

                     

                    Markus

                    • Re: Unable to Release change requests after configuring TMS
                      Msoro Msororaji
                      Currently Being Moderated
                      Markus Doehr wrote:

                       

                      I would try the following:

                      >

                      > - delete all TMS configurations of all systems

                      > - choose a domain controller and set it up

                      > - add both systems to the domain

                      > - create a transport route

                      > - create a new test transport and try to release it

                      >

                      >

                      >

                      > Markus

                       

                      Good Morning Markus

                       

                      I've done everything as per your instructions.

                      The issue of failing to release change requests in DEV is no longer there . But importing the same change requests to QAS is stillaa problem.

                       

                      In fact I've just realised when I do a  check for critical objects for the QAS import queue I get this error:

                       

                      -


                      TMS Alert Viewer: Error Message

                       

                      System   QAS              Command  TMS_MGR_GET_TR_OBJECT_LIST

                      Client   000              Service  Transport Service

                      User     TMSADM           Start    Online

                      Date     10.11.2011       Function TMS_TP_GET_OBJECT_LIST

                      Time     11:47:37         Message  TP_REPORTED_ERROR

                       

                       

                          Transport control program tp ended with error code 0230

                          Errors: Cant create any process

                      -


                      Checks for consistency & transport tool for QAS import queue do not return errors

                      • Re: Unable to Release change requests after configuring TMS
                        Markus Doehr
                        Currently Being Moderated

                        > -


                        > TMS Alert Viewer: Error Message

                        >

                        > System   QAS              Command  TMS_MGR_GET_TR_OBJECT_LIST

                        > Client   000              Service  Transport Service

                        > User     TMSADM           Start    Online

                        > Date     10.11.2011       Function TMS_TP_GET_OBJECT_LIST

                        > Time     11:47:37         Message  TP_REPORTED_ERROR

                        >

                        >

                        >     Transport control program tp ended with error code 0230

                        >     Errors: Cant create any process

                        > -


                         

                        Looks to me that you're running into some operating system limits.

                         

                        Any information in the dev_w* traces?

                         

                         

                         

                        Markus

                        • Re: Unable to Release change requests after configuring TMS
                          Msoro Msororaji
                          Currently Being Moderated

                          I included the two parameters below in the DEFAULT profile of QAS as per note 449270

                          SAPEVTPATH                     /usr/sap/QAS/DVEBMGS03/exe/sapevt

                          SYSTEM_PF                          /usr/sap/QAS/SYS/profile/DEFAULT.PFL

                           

                          there was some progress because I managed to import some requests to QAS system. infact the error below dissappeared & was replaced by some oracle errors (see further below)

                           

                          -


                          WARNING: System QAS. Warning.        20111110161630 :

                          ERROR:       The following call returned with exit code 127:

                          ERROR:         sapevt SAP_TRIGGER_RDDIMPDP -t name=QAS pf=/usr/sap/QAS/SYS/profile/DEFAULT.PFL

                          ERROR:       Background jobs cannot be started.

                          ERROR:       Please check trace file dev_evt.

                          WARNING:       (This warning is harmless if no further warnings follow.)

                           

                          -


                          2EETP000 function:   db_setget

                          2EETP000 fcode:      RT_GET (0)

                          2EETP000 tabname:    TRBAT

                          2EETP000 len (char): 0

                          2EETP000 key:

                          2EETP000 ok fetches: 0

                          2EETP000 last entry:

                          2EETP000 retcode:    1

                          1AETP000 exit in function texitnow

                          ERROR: EXIT(16) -> process ID is: 16777234

                          STOP  imp single           QAS   0016 20111110163755              KPC3594      QAS 20111110154324

                          START imp single           QAS        20111110164122              KPC3594      QAS 20111110164122

                          INFO  TBATG CONVERSION OF  QAS N      not needed                  KPC3594      QAS 20111110164122

                          START tp_getprots          QAS P      20111110164122              KPC3594      QAS 20111110164122

                          STOP  tp_getprots          QAS P      20111110164338              KPC3594      QAS 20111110164122

                          START MOVE NAMETABS        QAS 6      20111110164338              KPC3594      QAS 20111110164122

                          START tp_getprots          QAS P      20111110164338              KPC3594      QAS 20111110164122

                          STOP  tp_getprots          QAS P      20111110164339              KPC3594      QAS 20111110164122

                          STOP  MOVE NAMETABS        QAS 6      20111110164339              KPC3594      QAS 20111110164122

                          START MAIN IMPORT          QAS I      20111110164339              KPC3594      QAS 20111110164122

                          HALT 20111110164339

                          ERROR: uncaught internal error: ORA-24371: data would not fit in current prefetch buffer

                          ERROR: EXIT(16) -> process ID is: 14221508

                          STOP  imp single           QAS   0016 20111110164339              KPC3594      QAS 20111110164122

                          START imp single           QAS        20111110164553              KPC3594      QAS 20111110164552

                           

                          ERROR: uncaught internal error: ORA-03114: not connected to ORACLE

                          ERROR: EXIT(16) -> process ID is: 17432610

                          STOP  imp single           QAS   0016 20111110174233              KPC3594      QAS 20111110174232     

                          START imp single           QAS        20111110175614              KPC3594      QAS 20111110175614     

                          INFO  TBATG CONVERSION OF  QAS N      not needed                  KPC3594      QAS 20111110175614     

                          START MOVE NAMETABS        QAS 6      20111110175614              KPC3594      QAS 20111110175614     

                          START tp_getprots          QAS P      20111110175614              KPC3594      QAS 20111110175614     

                          STOP  tp_getprots          QAS P      20111110175618              KPC3594      QAS 20111110175614     

                          STOP  MOVE NAMETABS        QAS 6      20111110175618              KPC3594      QAS 20111110175614     

                          START MAIN IMPORT          QAS I      20111110175618              KPC3594      QAS 20111110175614     

                          HALT 20111110183551

                          ERROR: uncaught internal error: ORA-03114: not connected to ORACLE

                          ERROR: EXIT(16) -> process ID is: 14090430

                          HALT 20111110183551

                          ERROR: uncaught internal error: ORA-03114: not connected to ORACLE

                          ERROR: EXIT(16) -> process ID is: 14090430

                          STOP  imp single           QAS   0016 20111110183551              KPC3594      QAS 20111110175614     

                          STOP  imp single           QAS   0016 20111110183551              KPC3594      QAS 20111110175614     

                          START imp single           QAS        20111110184713              KPC3594      QAS 20111110184712     

                          INFO  TBATG CONVERSION OF  QAS N      not needed                  KPC3594      QAS 20111110184712     

                          START MOVE NAMETABS        QAS 6      20111110184713              KPC3594      QAS 20111110184712     

                          START tp_getprots          QAS P      20111110184713              KPC3594      QAS 20111110184712     

                          STOP  tp_getprots          QAS P      20111110184716              KPC3594      QAS 20111110184712     

                          STOP  MOVE NAMETABS        QAS 6      20111110184716              KPC3594      QAS 20111110184712     

                          START MAIN IMPORT          QAS I      20111110184716              KPC3594      QAS 20111110184712     

                          HALT 20111110184716

                          ERROR: uncaught internal error: ORA-03114: not connected to ORACLE

                          ERROR: EXIT(16) -> process ID is: 9306204

                          STOP  imp single           QAS   0016 20111110184716              KPC3594      QAS 20111110184712     

                          HALT 20111110184716

                          ERROR: uncaught internal error: ORA-03113: end-of-file on communication channel

                          ERROR: EXIT(16) -> process ID is: 9306204

                          STOP  imp single           QAS   0016 20111110184716              KPC3594      QAS 20111110184712

            • Re: Unable to Release change requests after configuring TMS
              Msoro Msororaji
              Currently Being Moderated

              Markus

               

              SAP Note 449270 did the trick. I only applied part of the changes because most of them ( rdisp/ssserv, rdisp/mshost, SAPSYSTEM  & sapms<SID>  36XX in /etc/services )were already in the three systems after instalation when TMS was working fine

               

               

              This problem was overcome after iincluding the parameters below   (in bold ) to QAS & PRD system. This was done from  the transport domain controller (DEV system) which updated file TP_DOMAIN_DEV.PFL &  distributed the changes to the systems in the landscape .

               

              What perplexed me is the fact that  until a week ago our, TMS has been working fine without these parameters

               

              1. more TP_DOMAIN_DEV.PFL

               

              #----


              #Caution !

              #This file was generated by the Transport Management System.

              #Do not change this file using a text editor.

              #For further information please see the online documentation of

              #transaction STMS.

              #If this file was destroyed, it can be regenerated in the TMS.

              #To do this, log on to the domain controller (system DEV) and call

              #Transaction STMS. In the System Overview, you can distribute the TMS

              #configuration. This regenerates the file.

              #STMS -> Overview -> Systems -> Extras -> Distribute TMS Configuration

              #----


              #

              #

              TRANSDIR            = /usr/sap/trans

              #

              DEV/DBHOST          = DEV

              DEV/DBLIBPATH       = /usr/sap/DEV/DVEBMGS01/exe

              DEV/DBNAME          = DEV

              DEV/DBTYPE          = ora

              DEV/NBUFFORM        = 1

              DEV/TP_VERSION      = 266

              #

              PRD/DBHOST          = PRD

              PRD/DBLIBPATH       = /usr/sap/PRD/DVEBMGS14/exe

              PRD/DBNAME          = PRD

              PRD/DBTYPE          = ora

              PRD/NBUFFORM        = 1

              PRD/R3TRANSPATH     = /usr/sap/PRD/SYS/exe/run/R3trans

              PRD/SAPEVTPATH      = /usr/sap/PRD/SYS/exe/run/sapevt

              PRD/SYSTEM_NR       = 14

              PRD/SYSTEM_PF       = /usr/sap/PRD/SYS/profile/DEFAULT.PFL

              PRD/TP_VERSION      = 266

              #

              QAS/DBHOST          = QAS

              QAS/DBLIBPATH       = /usr/sap/QAS/DVEBMGS03/exe

              QAS/DBNAME          = QAS

              QAS/DBTYPE          = ora

              QAS/NBUFFORM        = 1

              QAS/R3TRANSPATH     = /usr/sap/QAS/SYS/exe/run/R3trans

              QAS/SAPEVTPATH      = /usr/sap/QAS/SYS/exe/run/sapevt

              QAS/SYSTEM_NR       = 03

              QAS/SYSTEM_PF       = /usr/sap/QAS/SYS/profile/DEFAULT.PFL

              QAS/TP_VERSION      = 266

              #

  • Re: Unable to Release change requests after configuring TMS
    Marius Burger
    Currently Being Moderated

    good day,

     

    is the vaule for TRANSDIR correct ?

     

    kind regards

    marius

Actions