Test Import Cancelled

[Former Member]

Hi :

I have imported one request in integration server . After import i went to SE10 and found transport log showing that Test import cancelled .

Test import

Transport request___:DVAK944267

System______________: GQA

tp path : tp

Version and Release: 270.00.34 45B

Test import

End date and time : 20050406124751

8N Ended with return code: ===> 12 <===

Can any one explain why it was happend and remedy for that .

Thanks in advance

Chimsi

[Former Member]

Try to expand the log to see more details of the error.

[Former Member]

Hi Chimsi,

Without analysing the log, it's not possible to exactly determine the problem.

But usually import will fail when one or more components are missing in the request.

Ex:

1) Tables is in the request but corresponding domain or dataelements not present in that request.

2) Function modules exists in one request and the Function groups exist in some other request that is not transported yet.

3) Some customizing request that needs to be transported first before the other workbench request is being transported.

Ultimately, make sure that you import the request in the correct order.

Hope this helps you.

Cheers,

Sam

[Former Member]

Hi Ajay :

This is the release status .

6A Log overview for DVAK944937

&#61493;&#61472; &#61472; DVAK944937 Auths-AR877797-ZEDI and ZEDI1

&#61493;&#61472; DVA System DVA

0P Oper. system checks 06/06/2005 11:00:07 (0) Ended OK

0P Export 06/06/2005 11:00:28 (0) Ended OK

&#61493;&#61472; GQA System GQA

17 Selection for import 06/06/2005 11:00:27 (0) Ended OK

0P Test import 06/06/2005 11:00:29 (12) <b>Cancelled</b>

0P Import 06/06/2005 11:21:11 (0) Ended OK

0P Check versions 06/06/2005 11:21:16 (0) Ended OK

0P Method execution 06/06/2005 11:21:30 (0) Ended OK

&#61493;&#61472; EPD GLOBAL Production Instance

17 Selection for import 06/06/2005 11:22:39 (0) Ended OK

0P Import 06/06/2005 11:23:50 (0) Ended OK

0P Check versions 06/06/2005 11:23:57 (0) Ended OK

0P Method execution 06/06/2005 11:24:14 (0) Ended OK

and also look into log

Test import

Transport request___: DVAK944937

System______________: GQA

tp path : tp

Version and Release: 270.00.34 45B

8O Connect is not possible: invalid values set for DIR_LIBRARY '/usr/sap/GQA/S

Test import

End date and time : 20050606110029

8N Ended with return code: ===> 12 <===

- Chimsi

[Former Member]

Hi,

You may be able to expand the log to another detailed level (check for the icons on the left of the messages). If so, it may point to the object which caused the error in import.

cheers,

[Former Member]

Hi Sam :

Please look into above log .

- Chimsi

[Former Member]

Hi Chimsi,

Please check whether all the object you have created or changed exists in the same request. I don't find this log to be a major issue. Everything seems to be fine except for a few objects that may not be included as well...

Kindly check the same.

Hope this helps.

Cheers,

Sam

[Former Member]

1. 12

: Fatal errors have occurred, such as errors while reading or writing a file or unexpected errors within the database interface, in particular database problems.

SO BETTER CHECK THAT NO DATA ELEMENTS ARE MISSING.FROM SE01 CHECK ALL THAT IS INCLUDED IN THE TRANSPORT.

[Former Member]

Hi :

Please check detail log and and request u to give me some clue .

Test import

Transport request___: DVAK944935

System______________: GQA

tp path : tp

Version and Release: 270.00.34 45B

R3trans version 6.05 (release 45B - 29.08.02 - 14:47:42).

===============================================

control file: /usr/sap/trans/tmp/DVAK4935.GQA

> #pid 25707 on phxgdv2 (dvaadm)

> testimport

> file='/usr/sap/trans/data/R944935.DVA'

> client=151

> buffersync=no

>

R3trans was called as follows: R3trans -w /usr/sap/trans/tmp/DVAP944935.GQA /usr/sap/trans/tmp/DVAK4935.GQA

date&time : 06.06.2005 - 08:28:19

8O Connect is not possible: invalid values set for DIR_LIBRARY '/usr/sap/GQA/S

Test import

End date and time : 20050606082819

8N Ended with return code: ===> 12 <===

- Chimsi

[Former Member]

and also this is happening some of the users frequently and for all the users .

-Chimsi

[Former Member]

It should not be a problem of this transport. It is likely that all transports on this system are failing with 12 error code.

R3trans is not able to connect to the DB hence this error. Possible causes could be

- Upgrade of kernel with some components missing (like upgraded dlls for connection to DB)

- Incorrect settings of environment variable (eg DIR_LIBRARY)

- etc..

You will find a number of notes on OSS on R3trans connection error. Most likely you will need to run 'r3trans -x' command on app server which will create a log file 'r3trans.log' which will likely have more info on the error. With this info you should be able to search the OSS and fix the error.

cheers,

[Former Member]

Hi Ajay :

It is happening for some of the users and that to be not all the times .

-Chimsi