cancel
Showing results for 
Search instead for 
Did you mean: 

Issue in Support package upgrade

Former Member
0 Kudos

Dear all,

When i upgrade SAP_ABA component level 16. i got import_Proper error.

I am not able to proceed the upgrade.

please give some possible solutions on this..

Regards,

Mohankumar.G

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Sorry for the mis understand..

Here you go for the log file content...

please suggest some possible solutions.

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

1 ETP152 TESTIMPORT

1 ETP101 transport order : "SAPKA70016"

1 ETP102 system : "BW7"

1 ETP108 tp path : "tp"

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

1 ETP198

4 ETW000 R3trans.exe version 6.14 (release 700 - 24.04.08 - 14:09:00).

4 ETW000 unicode enabled version

4 ETW000 ===============================================

4 ETW000

4 ETW000 date&time : 08.10.2008 - 17:05:26

4 ETW000 control file: D:\usr\sap\trans\tmp\SAPKKA70016.BW7

4 ETW000 > #pid 7172 on blrkecesbibw (SYSTEM)

4 ETW000 > testimport

4 ETW000 > file='D:\usr\sap\trans\data\RA70016.SAP'

4 ETW000 > buffersync=no

4 ETW000 >

4 ETW000 R3trans was called as follows: R3trans.exe -w D:\usr\sap\trans\tmp\SAPPA70016.BW7 -u 1 D:\usr\sap\trans\tmp\SAPKKA70016.BW7

4 ETW000 active unconditional modes: 1

4 ETW000 Connected to DBMS = MSSQL --- SERVER = 'blrkecesbibw' DBNAME = 'BW7' --- SYSTEM = 'BW7'.

4 ETW690 COMMIT "0" "0"

4 ETW000 trace at level 1 opened for a given file pointer

4 ETW000

4 ETW000 ================== STEP 1 =====================

4 ETW000 date&time : 08.10.2008 - 17:05:26

4 ETW000 function : TESTIMPORT

4 ETW000 data file : D:\usr\sap\trans\data\RA70016.SAP

4 ETW000 buffersync : NO

4 ETW000 clients : as exported

4 ETW000 l.s.m. : VECTOR

4 ETW000 commit : 100000

4 ETW000 table cache : dynamic

4 ETW000

4 ETW000 Character set on this machine : 2 byte unicode little endian.

4 ETW000 Character set on the data file: 2 byte unicode big endian.

4 ETW000 Data file is compressed with algorithm 'L'.

4 ETW000 Export was executed on 27.05.2008 at 12:01:47 by k7badm

3 ETW709 "700 "

4 ETW000 with R3trans version: 14.02.08 - 14:55:00

4 ETW000 Source System = Solaris on SPARCV9 CPU on DBMS = DB6 --- DB2DBDFT = 'K7B' --- SYSTEM = 'K7B'.

4 ETW000

4 ETW000 language vector during export: 1234568ABCDEFGHIJKLMNOPQRSTUVWcd

4 ETW000 language vector during export: 1234568ABCDEFGHIJKLMNOPQRSTUVWcd (ISO-ZHTHKOROSLHRUKARHECSDEENFRELHUITJADAPLZFNLNOPTSKRUESTRFISVBGCASH)

4 ETW000 lsm during export: ALL

4 ETW000 datafile was created with 'langdeletions=no'.

4 ETW000 trfunction = D (patch transport)

3 ETW708 "000"

4 ETW000 switching to selective language import

4 ETW000 the following languages will be imported: DE

4 ETW000 Used Commandfile SAPKA70016 (SAPUSER/2500)

4 ETW000 0 entries for E070 imported (SAPKA70016).

4 ETW000 0 entries for E071 imported (SAPKA70016 *).

4 ETW690 COMMIT "0" "0"

4 ETW690 COMMIT "0" "0"

4 ETW000 12681184 bytes read.

4 ETW000 Transport overhead 18.0 %.

4 ETW000 Data compressed to 7.3 %.

4 ETW000 Duration: 6 sec (2113530 bytes/sec).

3 ETW710 "0" "0"

4 ETW000 [dev trc ,00000] Wed Oct 08 17:05:32 2008 6053124 6.053124

4 ETW000 [dev trc ,00000] Disconnecting from ALL connections: 22 6.053146

4 ETW000 [dev trc ,00000] Disconnected from connection 0 1636 6.054782

4 ETW000 [dev trc ,00000] statistics db_con_commit (com_total=3, com_tx=2)

4 ETW000 40 6.054822

4 ETW000 [dev trc ,00000] statistics db_con_rollback (roll_total=0, roll_tx=0)

4 ETW000 34 6.054856

4 ETW000 Disconnected from database.

4 ETW000 End of Transport (0000).

4 ETW000 date&time: 08.10.2008 - 17:05:32

1 ETP152 TESTIMPORT

1 ETP110 end date and time : "20081008170532"

1 ETP111 exit code : "0"

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

Former Member
0 Kudos

Hello

I am late in reply due to different time zones.

Can you please check any other log files updated during patch application. If it is not possible to copy and paste , You can send me in my e-mail.

regards,

Payal

Answers (4)

Answers (4)

Former Member
0 Kudos

There are four log files

SAPAB70013, HB and PB, LB..

which log file i need to copy here.. plz let me know..

Regards,

Mohankumar.G

Former Member
0 Kudos

Hello,

Can you please copy the log file from /usr/sap/trans/log?

regards,

Payal

Former Member
0 Kudos

Please find below for the ERROR TEXT

Error in Phase: IMPORT_PROPER

Reason for error : TP_STEP_FAILURE

Return code : 0008

Error message : OCS Package ALL, tp step "6", return code 0008

Notes on phase IMPORT_PROPER

in this phase repository objects and talbe entries are imported. This phase can terminate due to the following reasons.

1. TP_INTERFACE_FAILURE : The tp interface could not be called.

2. TP_FAILURE : the program tp could not executed. for more information on this see the SLOG or ALOG log file.

3. TP_STEP_FAILURE : A tp step could not be exeucted. to find the cause of the error, see the appropriate log, such as the import log. if the cancelation message a tp step 6, N or S, the step in question is independent of the transport request. You can find these logs under the node Import steps not specific to transport reqeust in the log overview

Alternatively, you can find these logs in the follwoing files in the log director of your transport directly (usually: /usr/sap/trans/log):

- tp Step 6 : P<YY><MM><DD>.<SID>

- tp Step N : N<YY><MM><DD>.<SID>

- tp Step S : DS<YY><MM><DD>.<SID>

you can display these files using the report RSPUTPRT or by calling transaction AL11.

At prerequisite of the support package manager is that the change and

Transport System(CTS) is configured correctly. For more detailed information, read the online documentation available from Help -> SAP Library -> mySAP Technology Components -> SAP web Application Server -> Change and Transport System.

A list of the most important SAP Notes for Online Correction Support

(OCS) is available in SAP Note 97620, which is updated regularly.

ChandranGanesan
Active Contributor
0 Kudos

Hello,

Please give the details of the error as this is a common error during upgrade.

Thanks

Chandran