cancel
Showing results for 
Search instead for 
Did you mean: 

Transports Stopped importing with error - 2EETP000 sap_dext called with msgnr "2":

0 Kudos

Hi Sap Gurus

Hopefully someone has experienced this before

We have a problem importing transports to our DEV/QAS systems. When we try to import the TMS Lorry appears for a split second then goes back to green.  We have tried the command prompt also without success.

It suggest removing a lock but the lock does not exist so we have created the file to see it helps without success

Thanks in advance

Col

the following entry in the SLOG and when importing via

the OS.

  

R:\>tp import DVPK941502 QAS

Client=500

pf=\\PFxxSAPxxxx\sapmnt\trans\bin\TP_DOMAIN_DVP.PFL

This is tp

version 380.29.37 (release 741, unicode enabled)

2EETP000 sap_dext called

with msgnr "2":

2EETP000 ---- db call info ----

2EETP000 function:

db_rtab

2EETP000 fcode: RT_INSERT

2EETP000 tabname: TRBAT

2EETP000 len

(char): 307

2EETP000 key: TPLOCK J

2EETP000 retcode: 2

1AETP000

exit in function texitnow

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

Cannot

remove \\PFxxSAPxxxx\sapmnt\trans\tmp\SLOG1510.QAS.LOC: The

system cannot

find the file specified.

tpunlock_file: Cannot

remove

\\PFxxSAPxxxx\sapmnt\trans\tmp\SLOG1510.QAS.LOC : The system

cannot

find the file specified.

tp returncode

summary:

TOOLS: Highest return code of single steps was: 16

ERRORS:

Highest tp internal error was: 0200

tp finished with return code:

200

meaning:

ERROR: see tp's stdout (Standard Out may not be available)

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Thanks for all your replies - we have resolved the issue as follows..

We had an original message saying too many tables - SAP advise...

An SAP system contains a high percentage of
empty tables. We recommend that you use virtual tables (see SAP Note 1151343).
As a result,empty tables are not created as database tables, which means that they do not
contribute to the number of objects in a tablespace. You can also

convert empty tables to virtual tables later on using the DBA Cockpit. We did this and ran into the TMS issue...

 

Looking at the logs supplied to SAP the system couldn’t create TRBAT. The TRBAT is a virtual table. We attempted to force the creation of TRBAT but it complained the
tablespace PRD#ES620D did not exist.

              
We have added the tablespace PRD#ES620D as a temporary measure into the
database and the system has imported the transport

              
We need to investigate why the TADB6 tablespace allocation references
PRD#ES620D and not the upgrade correct tablespaces PRD#ES740D

Answers (3)

Answers (3)

former_member182657
Active Contributor
0 Kudos

Hi Colin,


ERRORS:

Highest tp internal error was: 0200

tp finished with return code:

200

Error code arises when tp cannot establish connection with the database.So here i suggest you to

download a new version of the database library from the SAP Service Marketplace & check again.

Hope this will help you.

Regards,

Gaurav

manumohandas82
Active Contributor
0 Kudos

Hi Colin

Go to TXN STMS_IMPORT and click on the Import Monitor .

Delete any entries there

Log out of transaction and kill any tp process running under OS .

Check for any file .LOC in the /trans/tmp directory  . If present rename it to .OLD

Then try once again

Thanks ,

Manu

0 Kudos

Thanks Manu

yeah tried that also and no joy - these are also what we have tried..

Checked transport settings.

 

Rescheduled Standard SAP import jobs.

 

Checked transport table TRBAT and TRJOB - no entries - as expected. Including TRLOCKR – no
entries

 

Checked for LOC/LOB files as per the SAP call request – none found.

 

Checked Transport tool test- ok  - program RSTPTEST

 

Check DB connection test - ok (R3trans –d)

 

Attempted to manually trigger the next transport step ( SM64 trigger RDD* jobs – job
reported no transport to import)

 

Upgraded R3trans and tp to latest version.

Restarted the System.

 

Retried a different transport same error.

Sriram2009
Active Contributor
0 Kudos

Hi Colin

Just do the full system restart and then try the same

BR

SS

0 Kudos

Thanks SS - tried but still issue.  Also tried restarting the TP Domain controller and still the same prob. The strange thing is nothing has changed!