Error in IMPORT_PROPER phase

Former Member · ‎01-12-2006

Hi guys,

I am trying to apply SP on my system 09-15

and I get and import_proper phase error below:

The import was stopped, since an error occurred during the phase

IMPORT_PROPER, which the Support Package Manager is unable to resolve

without your input.

After you have corrected the cause of the error, continue with the

import by choosing Support Package -> Import queue from the initial

screen of the Support Package Manager.

The following details help you to analyze the problem:

- Error in phase: IMPORT_PROPER

- Reason for error: TP_BUFFER_INCONSISTENCY

- Return code: 0008

- Error message: Pkgs. in queue don"t exist in the tp buffer (e.g.

SAPKB64010)

Tried the following:

Generated a new TP Parameter through STMS

Clear the log files

Tried to clear the buffer manually with S37 OCS_RESET_QUEUE getting an object locked message.

Updated the Kernel and SPAM/SAINT

Please Help

Thanks,

Damien

Private_Member_739866 · ‎09-22-2012

Hi, Damien

i am sorry but your command have to be corrected.

tp addtobuffer R5K1078 <sid> pf=<path>\profilename.pfl transdir=/usr/sap/trans

Regards,

Paramvirsinh Jetawat

IF it works fine for you please rate this.

Former Member · ‎08-23-2009

quick postcript to my last entry ... i have noticed some circumstances that appear to cause this situation. if you begin your saint import and then use stms to watch the progress, then the act of refreshing the import buffer display in stms seems to clobber all the buffer entries except the syncmark ones. very weird, but it has done this consistently and i kept having to repeat my tp addtobuffer script. if you stay well away from stms while saint is in progress, you don't seem to have any problems

Former Member · ‎08-23-2009

I experienced exactly the same problem when applying the SOLMAN EHP1 installation/upgrade despite meticulously following note 1169247. This was particularly annoying because we applied the packages to the DEV machine without any issues and then only encountered the problem in production. I still don't know what the root cause is, but this is what fixed it for me (thanks for the clues above)

The error I got was the good old "Pkgs. in queue don"t exist in the tp buffer".

1. I investigated the tp buffer by doing the following:

cd /usr/sap/trans/bin

tp show buffer SMP pf=TP_DOMAIN_SMP.PFL

The only things in the buffer were a whole lot of SYNCMARK entries and nothing else!

2. I scrubbed the contents of the buffer (after checking no tp processes were running):

rm /usr/sap/trans/buffer/SMP (alternatively do a tp cleanbuffer SID ...)

3. This is the important bit. You need to know what transports to add and IN WHAT ORDER

Start transaction SAINT

There is a [Logs] button on the front screen, press it

On the next screen, you will see something that says "Overview of transport logs"

For every transport (eg. SAPK-701DHINSAPBASIS) that you see in the list, you need to do the following:

tp ADDTOBUFFER <TPT No.> SMP U1 pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL tag=spam -DCTC=0 -Dtransdir=/usr/sap/trans

tp SETSYNCMARK <TPT No.> SMP U1 pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL tag=spam -DCTC=0 -Dtransdir=/usr/sap/trans

Once you have finished the entire list (I used a spreadsheet to generate the 150-odd entries I had to make), I restarted SAINT and it went in without issues. Hope this helps.

Former Member · ‎01-18-2008

Great help guys !!!

I avoid the format is works for me !!!

EricOud · ‎07-27-2007

Dear Damien,

Have you've checked the package assigned to the program?

If you use SE80, you can find it via the menu: Goto > Attbributes.

When you need to reassign to another package:

- Rightclick the object/programname

- More functions...

- Change package assignment

This worked for me with a simular error...

Regards,

Eric

Former Member · ‎08-08-2006

solution for this problem

tp ADDTOBUFFER <requestno> <SID> U1 pf="<path to your transpport profile and file> tag=spam -DCTC=0 -Dtransdir="<path to your transdir>"

Former Member · ‎03-22-2006

HI

AS I U SAID,,ME TOO HAVING THE SAME ERROR...I FOUND WE CANNOT ROLLBACK TO OLD STATUS AFTER ALL IT IS AFFECTED TO THE DATABASE......

Former Member · ‎02-02-2006

UP!

Former Member · ‎02-02-2006

Hi All!

I have a similar problem on my Netweaver'04 BW Productive Instance, STMS is on Stuck and no more transport are possible!!!

VERY BAD!!!

I have the SAME error and i checked all the possible but finding nothing interesting

Following a print screen from varous commands such as "TP SHOWPARAMS" "TP ADDTOBUFFER" etc..

Could you check again for me?

Thanks in advance...

G.R.

-

*0000

I

BSVK900675 | | |0000 | | |0000 | |

*0000

I

BSVK900677 | | |0000 | | |0000 | |

*0000

I

BSVK900678 | | |0000 | | |0000 | |

*0000

*0004

I

BSVK900657 | | |0000 | | |0000 | |

*0000

I

BSVK900659 | | |0000 | | |0000 | |

*0000

I

BSVK900655 | | |0000 | | |0000 | |

*0000

I

BSVK900661 | | |0000 | | |0000 | |

*0000

*0004

I

BSVK900663 | | |0000 | | |0000 | |

*0000

*0004

I

BSVK900665 | | |0000 | | |0000 | |

*0000

I

BSVK900680 | | |0000 | | |0000 | |

*0000

I

BSVK900681 | | |0000 | | |0000 | |

*0000

I

BSVK900685 | | |0000 | | |0000 | |

*0000

I

BSVK900687 | | |0000 | | |0000 | |

*0000

I

BSVK900688 | | |0000 | | |0000 | |

*0000

I

BSVK900690 | | |0000 | | |0000 | |

*0000

I

BSVK900691 | | |0000 | | |0000 | |

*0000

I

BSVK900692 | | |0000 | | |0000 | |

*0000

I

BSVK900695 | | |0000 | | |0000 | |

*0000

I

that makes 174 transports to be imported.

tp finished with return code: 0

meaning:

Everything OK

C:\Documents and Settings\bpradm>tp addtobuffer bsvk901395 bpr pf=d:\usr\sap\tra

ns\bin\tp_domain_bsv.pfl -Dtransdir=d:\usr\sap\trans

sapparam: sapargv( argc, argv) has not been called.

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

This is tp version 340.16.09 (release 640)

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBNAME is no longer used.

Addtobuffer failed for BSVK901395.

Neither datafile nor cofile exist (cofile may also be corrupted).

tp returncode summary:

TOOLS: Highest return code of single steps was: 0

ERRORS: Highest tp internal error was: 0247

tp finished with return code: 247

meaning:

addtobuffer has problems with data- and/or cofile

C:\Documents and Settings\bpradm>tp addtobuffer bsvk901395 bpr pf=d:\usr\sap\tra

ns\bin\tp_domain_bsv.pfl -Dtransdir=d:\usr\sap\trans

sapparam: sapargv( argc, argv) has not been called.

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

This is tp version 340.16.09 (release 640)

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBNAME is no longer used.

Addtobuffer failed for BSVK901395.

Neither datafile nor cofile exist (cofile may also be corrupted).

tp returncode summary:

TOOLS: Highest return code of single steps was: 0

ERRORS: Highest tp internal error was: 0247

tp finished with return code: 247

meaning:

addtobuffer has problems with data- and/or cofile

C:\Documents and Settings\bpradm>tp addtobuffer bsvk901396 bpr pf=d:\usr\sap\tra

ns\bin\tp_domain_bsv.pfl -Dtransdir=d:\usr\sap\trans

sapparam: sapargv( argc, argv) has not been called.

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

This is tp version 340.16.09 (release 640)

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBNAME is no longer used.

Addtobuffer failed for BSVK901396.

Neither datafile nor cofile exist (cofile may also be corrupted).

tp returncode summary:

TOOLS: Highest return code of single steps was: 0

ERRORS: Highest tp internal error was: 0247

tp finished with return code: 247

meaning:

addtobuffer has problems with data- and/or cofile

C:\Documents and Settings\bpradm>tp help

sapparam: sapargv( argc, argv) has not been called.

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

This is tp version 340.16.09 (release 640)

usage: tp <command> [argument(s)] [option(s)], where <command> may be one of:

-

----

----

Exporting I Buffer Actions I Disk Space

-

----

----

EXPORT I EXPWBO I ADDTOBUFFER I DELFROMBUFFERI CLEAROLD

R3E I VERSE I SETSYNCMARK I DELSYNCMARK I CHECK

SDE I I SETSTOPMARK I DELSTOPMARK I TESTOLD

TST I I MARK I UNMARK I

I I CLEANBUFFER I I

-

----

----

Importing I Special Functions I Information

-

----

----

PUT I I LOCKSYS I UNLOCKSYS I SHOWBUFFER

IMPORT I CHNTABS I LOCK_EU I UNLOCK_EU I COUNT

CMD I R3I I WRITELOG I GETPROTS I SHOWPARAMS

LIM I MEA I SAPSTART I SAPSTOP I GO

R3H I MVREPOS I GETTBATGENT I GETTRBATENT I CONNECT

ACT I MVKERNEL I GETDDXTTENT I GETDDXTFENT I CHECKIMPDP

TACOB I SDI I GETOPENCORR I CREATECOFILE I SHOWINFO

GENTB I GENT1 I PREPAREBUFFERI CREATEINFO I GETOBJLIST

GENT2 I GEN I CONTP I EXPCHK I EXTRDOCU

DIST I XPA I SHOWSEMAPHOREI SHOWSEMACLIENI GETCONVENT

MVNTABS I VERSI I SETSEMAPHORE I DELSEMACLIENTI EXPLAINRC

IMPSYNC I DELIVER I DELSEMAPHORE I GETTPSTATENT I

For more details call tp with the desired command (and no other parameters)

C:\Documents and Settings\bpradm>tp showparams bsvk901396 bpr pf=d:\usr\sap\tra

ns\bin\tp_domain_bsv.pfl -Dtransdir=d:\usr\sap\trans

sapparam: sapargv( argc, argv) has not been called.

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

This is tp version 340.16.09 (release 640)

ERROR: : parameter -Dtransdir=d:\usr\sap\trans has wrong length

Usage of command SHOWPARAMS:

tp SHOWPARAMS <SAPSID> [options ...]

Reads the parameter file and displays the current setting.

Options:

parname=<name> display the value of the parameter <name> only

pf=<TPPARAM> specify a transport parameter file

silent redirect stdout to dev_tp in current directory

-D"<entry>" specify a parameter for tp

-t<k> specify a trace level for tp

tf=<filename> specify the name of a trace file for tp

shdwtadir=<tabname> specify the name of a shadow TADIR

Description of arguments:

<TPPARAM> (complete) path of a transport parameter file

<entry> a parameter description as in a tp parameter file

<SAPSID> R/3 system's name, (target or source whatever is appropriate)

tp returncode summary:

TOOLS: Highest return code of single steps was: 0

ERRORS: Highest tp internal error was: 0206

tp finished with return code: 206

meaning:

parameter %s has wrong length

C:\Documents and Settings\bpradm>tp showparams bpr pf=d:\usr\sap\trans\bin\tp_do

main_bsv.pfl -Dtransdir=d:\usr\sap\trans

sapparam: sapargv( argc, argv) has not been called.

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

This is tp version 340.16.09 (release 640)

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBNAME is no longer used.

Parameters having their default value are displayed with a '>' as separator.

-

Global settings:

TRANSDIR : d:\usr\sap\trans\

ALLLOG : ALOG0605.BPR STOPONERROR > 9 SYSLOG : SLOG0605.BPR REPEATONERROR> 9

ABAPNTFMODE > t

TP_VERSION : 266

STOPIMMEDIATELY > 1 =TRUE

NEW_SAPNAMES > 1 =TRUE SQL_TRACE > 0 =FALSE

DUMMY > 0 =FALSE

CTC > 0 =FALSE NBUFFORM : 1 =TRUE

BUFFERFORMAT >

SSFKEYS >

SSFSIGNER >

SSFLIB >

SSFPAB >

ALLOW_RC4 > 1 =TRUE SID_LOG_FILES > 0 =FALSE

IMPMON_MODE > NORMAL IMPSMON_MODE > OFF

TRACE2SERVER > 0 =FALSE

-

DB-connection:

CONNECT_MODE > USE_ENV

MOD_ENV >

DBTYPE : ora

MSSQL_USEINTEGRATEDS >

MSSQL_SCHEMA >

DROPSTATISTICS > 1 =TRUE

DBS_DB2_PLANNAME >

RSDB_DB2PSLIBRARY >

-

Distribution of transports:

SYSTEM'S NAME : BPR VERS_AT_IMP > NEVER

SEPARATE_DELIVERY > 0 =FALSE

TESTSYSTEMS :

DELIVERYSYSTEMS :

SOURCESYSTEMS :

TARGETSYSTEMS :

SAPNAMES_LOGGING : ALL

VERS_AT_EXP > 1 =TRUE

CREATE_REPLIST > 0 =FALSE

-

R3trans:

R3TRANSPATH > R3trans.exe

R3TRANSSTAT >

LOCALR3TRANS > 0 =FALSE

CLIENTCASCADE > 0 =FALSE

RECCLIENT >

LANGUAGE >

LSM > NONE

SLI > -1

CHECKMASTERLANG > 0 =FALSE

RESTRICTLANG >

IMPORTSHADOW > 0 =FALSE

R3TRANSOPTIONS >

FILESPLIT > 0

ACC_IMPORT > 0 =FALSE

DDACTIVE > 0 =FALSE

SMODI > 1 =TRUE

PRESERVEMODINFO > 0 =FALSE

CHEATCLIENT000 > 0 =FALSE

LANGDELETIONS > 1 =TRUE

-

Transport daemon:

BATCHHOST >

SYSTEM_NR >

SYSTEM_PF >

SAPEVTPATH > sapevt.exe

-

Import in general:

MAINIMP_PROC > 1

> 0 =FALSE LOGICALIMPORT > 0 =FALSE

SETUNICODEFLAG > 0 =FALSE DDINACTIVE > 0 =FALSE

MAB > 1 =TRUE

R3UP > 0 =FALSELOCK_CHECK_WAIT_TIME > 0

EXP_CHECK_WAIT_TIME > 0 W_IMPORT > 1 =TRUE

W_NEVER > 0 =FALSE

K_IMPORT > 1 =TRUE K_NEVER > 0 =FALSE

T_IMPORT > 1 =TRUE T_NEVER > 0 =FALSE

C_IMPORT > 1 =TRUE C_NEVER > 0 =FALSE

BUFFERSNAPSHOT > 0 =FALSE

-

PUT:

PUTSTEPS > *=<Lw(H3A)dG

STARTSAP >

STOPSAP >

BUFFRESET > 1 =TRUE BUFREFTIME > 180

LOCK_EU > 1 =TRUE MC_ENQ_STEP > 1 =TRUE

GENERATION > 1 =TRUE RESET_TIMESTAMPS > 0 =FALSE

TATAF_TOLERANT > 0 =FALSE RESET_DBPOS > 0 =FALSE

NTACT_TIMECMP > 0 =FALSE

MVNTAB_LIST_FAILED > 1 =TRUE

-

Kernelmove:

KERNELMOVE > 0 =FALSE CLEANIPC > 0 =FALSE

EXELIST >

FROMDIR >

TODIR >

KERNELMOVEPATH >

CLEANIPCPATH >

-

Clearold:

DATALIFETIME > 200 OLDDATALIFETIME > 365

COFILELIFETIME > 365 LOGLIFETIME > 200

-

Properties:

SemaServer.Host : NULL

SemaServer.Port : NULL

tp.Semaphores : FILE

tp.ConnectTimeout : 10000

tp finished with return code: 0

meaning:

Everything OK

Former Member · ‎01-12-2006

Hi Damien,

Please check if your TMS is configured properly and working as supposed. You can create a dummy transport request and import it to the system you are trying to update.

Alternatively you can add your package to TP buffer manually (via "tp addtobuffer ..." command) but it will only work if TMS is configured.

Regards,

Mike

Error in IMPORT_PROPER phase

Accepted Solutions (0)

Answers (10)

Answers (10)

Re: Failed to commit objects to server : Undefined...

BTP Free Tier SAP Integration Suite (CPI) Cloud Fo...

Re: Filter on multiple criteria

Crystal Reports text clipping issue. PDF created b...

Re: Crystal Reports