SPAM update struck in IMPORT_PROPER phase

Hello gurus,
we are importing SAPKB70030, SAPKB70030 and SAPKA70030 into our LEH. LEH is a HCM developer system running on zLinux with database DB2 on zOS.
The update is stuck at the "move nametab" on the table TTONFTVZZBEPP. This table is a lock, which can currently not be resolved.
Because it is an empty table, we would like to skip this action. There is a possibility?
Thank you for your efforts.
Regards
Hartmut Wagner

Matt,
After we unlock the tables, we were able to continue the SPAM. Thank you for the tip.
Regards,
Hartmut

Similar Messages

SPAM version 36 is struck in import_proper phase of Prologue for crm rel700

Hi Gurus,
While updating the spam version to 36 in crm 700, its throughing the below message. I checked tp tool, consistency check, everything seems fine.
any idea what may casue this problem, as my spam is struck in import_proper phase of Prologue
The installation was stopped, since an error occurred during the phase
IMPORT_PROPER, which the Add-On Installation Tool is unable to resolve
without your input.
After you have corrected the cause of the error, continue with the
import by choosing Continue in the queue display.
The following details help you to analyze the problem:
 - 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
 to be continued

In this phase the system imports the Repository objects and the table
 entries. The following are reasons why this phase may fail:
 o TP_INTERFACE_FAILURE: The tp interface could not be called.
 o TP_FAILURE: The tp program could not be executed. For more
 information on this, see the SLOG or ALOG log file.
 o TP_STEP_FAILURE: A tp step could not be executed. To find the cause
 of the error, see the appropriate log, such as the import log.
 If a tp step 6, N, or S is specified in the termination message, it
 is a step that is independent of the transport request. You can vie
 these logs in the log overview by choosing Import Steps Not Specifi
 to Transport Request.
 Alternatively, see the logs in the following files in the log
 subdirectory of your transport directory (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>
 To display these files, use the report RSPUTPRT or transaction AL11.
The Add-On Installation Tool requires that the Change and Transport
 System (CTS) be configured correctly. For more detailed information,
 read the online documentation available from Help -> SAP Library ->
 mySAP Technology Components -> SAP Web Application Server -> BC 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.
Regards - Munish

SPAM Update stuck in EPILOGUE phase

Hi,
We were trying to update the SPAM level from 40 to 45 of our R/3 4.6C system. After the SPAM update, we saw an information text saying " The current progam has been modified while running" and then just restarted transaction SPAM. The SPAM level has been updated to 45 but the status got stuck in the EPILOGUE phase with a red traffic light. We checked import/action/tp logs but did not find any errors. We can't find any OSS note as well describing this issue. Can anyone help us with this issue? We cannot proceed with our Support pack upgrade =(
Thanks and God Bless.

Hi Rekka ,
you logoff and login again and run spam again .if still getting same error then lock all users and run the spam .This problem occures while run the spam same time some user working on same program.
please check and give thereward for this.

SPAM Update stuck in IMPORT_PROPER

Hi,
I was updating SPAM update 26 for WAS 7.00. It got stuck and the job was going on and on. When I stopped the transaction and restarted SPAM, the SPAM version was shown as 26 but the status was red in IMPORT_PROPER. I tried restarting many times but it is continuously running. I checked the logs and there is no error in the action logs as well as in the detailed logs. The version is updated but it did not get completed. What can be the issue?
Please help!
Regards,
Abhishek Jain

Hello,
I hope you had a backup of your system before you started updating SPAM and/or support packs.
Also, after ensuring you have backup.
Please follow the instructions given in SAP Note 684564 - Re-importing a SPAM/SAINT update
Regards,
Siddhesh
Edited by: Siddhesh Ghag on Apr 9, 2008 11:11 AM

SPAM update in IMPORT_PROPER phase

Dear All,
I have installed SAP Web Neweaver 04s as ABAP on MSSQL database windows
OS and upgraded kernel 640 patch 175.
But now when i go to import SPAM /SAINT from level 17 to 23 ie.
SAPKD64023 then its running in IMPORT_PROPER Phase since last 5-6 hrs.
PLEASE SUGGEST how to speed up my process??
Log is as below:
Log Overview for SAPKD64023
SAPKD64023 SPAM/SAINT Update - Version 640/0023
BPW System BPW
Generate Transport Information File 02.01.2008 13:41:45 (0)
Successfully Completed
Test Import 02.01.2008 13:41:46 (0) Successfully Completed
Import Request Piece List 02.01.2008 13:41:47 (4) Ended with Warning
Import ABAP Dictionary Objects 02.01.2008 13:41:52 (4) Ended with
Warning
02.01.2008 10:54:46 (4) Ended with Warning
02.01.2008 13:41:52 (4) Ended with Warning
ABAP Dictionary Activation 02.01.2008 14:13:28 (4) Ended with Warning
Import steps not specific to transport request
ABAP Dictionary Distribution 02.01.2008 14:23:31 (4) Ended with Warning
pls help me ASAP.
Regards & Thanks,
Ankita.

Hi Ankita,
I advice you to leave it for the moment and wait until it finishe that particular stage and check for the workporcess overview which report its executing at the back.Dont stop the process forcefully as it might cause inconsistency.
Regards,
Iqbal

SPAM IMPORT_PROPER Phase delay

Hi all,
I have SOLMAN 7 EHP1 SP 24. in a windows host, with Oracle database.
I just update my spam to latest version 7.01/0041
then i need to updatethe component "ST-ICO 150_700" my actual SP is 24, i need get updated to patch 0025.
I add to the queue only this ST-ICO component.
In sm37 I see the job running without errors.
Job Spool Job Doc Job CreatedB Status Start date Start time Duration(sec.) Delay (sec.)
OCS_QUEUE_IMPORT 71360900 Active 19.01.2011 16:21:02 55.578 0
In spam in action log see that all previous phases was successfully finished, for example the latest phase was Import phase 'DDIC_ACTIVATION' .
but in IMPORT_PROPER Phase is taking more than 16 hours right now.
If is just a ST-iCO component why this take so long? Is normal this behaviour?
Where can i see detailed log of actions, or how can i ensure me that all is running ok?
Thanks a lot
update: in tp system log i see so many lines with this:
WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17060), I'm waiting 2 sec (20110120064823). My nam
WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17070), I'm waiting 2 sec (20110120064853). My nam
WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17080), I'm waiting 4 sec (20110120064921). My nam
WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17090), I'm waiting 2 sec (20110120064952). My nam
WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17100), I'm waiting 1 sec (20110120065010). My nam
WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17110), I'm waiting 3 sec (20110120065038). My nam
WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17120), I'm waiting 5 sec (20110120065117). My nam
WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17130), I'm waiting 1 sec (20110120065153). My nam
WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17140), I'm waiting 4 sec (20110120065222). My nam
WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17150), I'm waiting 1 sec (20110120065259). My nam
WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17160), I'm waiting 2 sec (20110120065332). My nam
WARNING: \\solman\sapmnt\trans\tmp\SAPKK-1507PINSTPL.SSM is already in use (17170), I'm waiting 3 sec (20110120065404). My nam
I wiil try restart the import .
Edited by: Manfred Kaufmann on Jan 20, 2011 1:55 PM

Thanks for the tip. This seemed to resolve my issue.

SPAM update during prepare phase

Hi all,
I am doing an upgrade from 40B to 4.7 and finished my preparation before Prepare phase.
Initialization phase is also completed successfully during prepare phase.
Unfortunately i forgot to upgrade my SPAM to the latest and now i am unable to continue with Prepare
phase because it is asking me to upgrade SPAm.
And when i am performing SPAM update , it is giving warning and unable to continue further
as " Caution: Upgrade is still running. Patches may be lost.
Message no. TN 153 "
Please let me know the way out , as i have also restarted my SAP and database but same warning still appear.
Regards,
RR

I suggest to cancel PREPARE, apply SPAM update and after that start PREPARE from scratch.
Cheers

Error in IMPORT_PROPER phase

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

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
*0000
I
BSVK900675 | | |0000 | | |0000 | |
*0000
*0000
I
BSVK900677 | | |0000 | | |0000 | |
*0000
*0000
I
BSVK900678 | | |0000 | | |0000 | |
*0000
*0004
I
BSVK900657 | | |0000 | | |0000 | |
*0000
*0000
I
BSVK900659 | | |0000 | | |0000 | |
*0000
*0000
I
BSVK900655 | | |0000 | | |0000 | |
*0000
*0000
I
BSVK900661 | | |0000 | | |0000 | |
*0000
*0004
I
BSVK900663 | | |0000 | | |0000 | |
*0000
*0004
I
BSVK900665 | | |0000 | | |0000 | |
*0000
*0000
I
BSVK900680 | | |0000 | | |0000 | |
*0000
*0000
I
BSVK900681 | | |0000 | | |0000 | |
*0000
*0000
I
BSVK900685 | | |0000 | | |0000 | |
*0000
*0000
I
BSVK900687 | | |0000 | | |0000 | |
*0000
*0000
I
BSVK900688 | | |0000 | | |0000 | |
*0000
*0000
I
BSVK900690 | | |0000 | | |0000 | |
*0000
*0000
I
BSVK900691 | | |0000 | | |0000 | |
*0000
*0000
I
BSVK900692 | | |0000 | | |0000 | |
*0000
*0000
I
BSVK900695 | | |0000 | | |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

SAPKB70012 patch struck in IMPORT_PROPER

Hi All,
I have a SAP SCM 5.0 system with BI.
I applied one single SAP Basis Support Package (SAPKB70012) overnight. In the morning saw that its struck in IMPORT_PROPER. The current action showing is QUEUE IMPORT. I started the SP again from that point and its continuing with "imp_all" for the last two days.
I am sure, the installation is not happening but the SPAM status shows "imp_all". I stopped and started again..But again its in that phase "imp all" still going on.
The Transport log show return code 12.
Please see the Transport Log below
REP System REP
 Generate Transport Information File 15.12.2008 20:43:02 (0) Successfully Comple
 Import Request Piece List 15.12.2008 20:44:48 (4) Ended with Warning
 Test Import 15.12.2008 20:46:42 (4) Ended with Warning
 Import ABAP Dictionary Objects 15.12.2008 21:07:17 (4) Ended with Warning
 ABAP Dictionary Activation 15.12.2008 21:28:02 (4) Ended with Warning
 Import 15.12.2008 22:29:10 (12) Canceled
 Import steps not specific to transport request
Please see the Error Log also
Main import
Tansport request : SAPKB70012
System : REP
tp path : tp
Version and release: 370.00.01 700
sap_dext called with msgnr 1:
db call info -
function: db_setget
fcode: RT_GET
tabname: ALMONISETS
len (char): 28
key: MSSAP CCMS Monitor Templates
ok fetches: 0
last entry:
retcode: 1
SQL error 3106 accessing : ORA-03106: fatal two-task communication protocol e
Main import
End date and time : 20081215222910
Ended with return code: ===> 12 <===
Please advice what to do?
Regards,
Jitender

Venu,
I have checked the note (822379 - Known problems with Support Packages in SAP NW 7.0x AS ABAP) also. Nothing there.
The problem which I can see in the SLOG
WARNING: Background job RDDIMPDP could not be started or terminated abnormally.
 Please check that the R/3 system is running.
 Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
sapretail:repadm>
Can I schedule RDDIMPDP at OS level. Reason, it gives dump when i try to open se37.
Moreover SAP Suggested me to upgrade the database to 10.2.0.2 and apply the interim patch which solves the ORA 3601 problem. But after this also. I am not able to apply the patch
Regards,
Jitender
Edited by: Jitender Dugar on Jan 2, 2009 5:37 PM

Spam update

hi
when i am trying to uddate spam from 18-29 it gives me following error
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_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 table entries are imported. This
phase can terminate due to the following reasons:
o TP_INTERFACE_FAILURE: The tp interface could not be called.
o TP_FAILURE: The program tp could not be executed. For more
 information on this, see the SLOG or ALOG log file.
o TP_STEP_FAILURE: A tp step could not be executed. To find the cause
 of the error, see the appropriate log, such as the import log.
 If the cancelation message contains 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 request
 in the log overview.
 Alternatively, you can find these logs in the following files in the logs under the node Import steps not specific to transport request
 in the log overview.
 Alternatively, you can find these logs in the following files in t
 log directory of your transport directory (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 callin
 transaction AL11.
 A 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 .
ours is ecc5.0,oracle datebase
i searched for this error on net after reading several posts i tried to reimport several times but still it gives me the same error
plz help asap
regards

Hi Subash,
Please do the below steps to resolve the issue. Defintely it will works.
1) stop R/3 through MMC
2) put the following environment variables:
2.1) setenv SHLIB_PATH /usr/sap/BSP/sys/exe/run
2.2) setenv dbms_type ora ( if your DB is oracle)
3) start sap through MMC (to take new values of these environment variables)
4) Restart SPAM update.
I guess it will resolve with the NEW environment variable "dbms_type".
Please do that and let me know if still error persists.
Thanks
Kishore

SPAM update Error for patch level 42 on 7.01

Hi all,
While applying SPAM update 42 for 7.01, we received the error below. We also tried to apply a lower version with the same results. Your help is appreciated.
Class CL_OCS_RT_ANALYSIS,Method GET_XML
The row type of the table "ME->T_PATRTVERS" is not compatible with
field symbol type "<FS_PATRTVERS>".
from ST22:
Runtime Errors SYNTAX_ERROR
Date and Time 10/10/2011 05:16:00
Short text
Syntax error in program "CL_OCS_RT_ANALYSIS============CP ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSPAM" had to be terminated because
it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"CL_OCS_RT_ANALYSIS============CP " in include
"CL_OCS_RT_ANALYSIS============CM002 " in
line 67:
"The row type of the table "ME->T_PATRTVERS" is not compatible
with fie"
"ld symbol type "<FS_PATRTVERS>"."
Thanks,
Domenick

Dear Domenick,
This issue you are facing is most probably because of a force reset of SPAM queue in IMPORT_PROPER phase.
You might have reset the queue forcibly which has created inconsistency in the system and has destoyed SPAM transaction
related program sources.
Now in order to resolve this you can try out a small fix.
You can pick up the class/interface CL_OCS_RT_ANALYSIS============CP from a system which has already been patched with SAPKD70142. You can transport this class to the affected system.
Once done, try to do the SPAM import. If the SPAM import is successfull it is fine.
If it not successfull, there is no other way apart from restoring the sytem since the SPAM sources are corrupt.
Best Regards,
Abhishek

IDES ERP 2005 / open ABAP dictionary conversion during SPAM Update

Dear all,
First of all, I'm currently busy implementing a educational enviroment for our company, we are using IDES MySAP ERP 2005 SR1 MSSQL.
At the moment we are trying to upgrade the SPAM version from version 20 to 22.
However, during the requirement checks the following error occurred :
Open conversions in the data dictionary
Phase CHECK_REQUIREMENTS: Explanation of Errors
Some open conversion requests still exist in the ABAP Data Dictionary
for the following ABAP Dictionary objects. To avoid inconsistencies and
loss of data, you must process these conversions first.
Proceed as follows:
- Open a new session.
- Start the Database Utility (transaction SE14).
- Correct the inconsistencies for the specified objects.
- Repeat the import phase. If no more inconsistencies are found, the
import continues.
Phase CHECK_REQUIREMENTS: Open ABAP Dictionary Conversions
Object Type Object Name
Table Index LXE_WRK_4 ~ STA
 SC2T327F363DFA4T ~ ESI
 SC2T327F363DFA4T ~ KYS

It seems that the indexes mentioned above are missing or doesn't exist!!!! i've tried looking for a sap note or a solution on SDN. However, haven't found a solution at all, or I'm looking at the wrong spot.
Is there a note or can somebody provide me what's in the indexes, so i can create it in our IDES system.
Regards,
Yam-Lang Lee

Hi Kiran,
Thank you very much. I managed to create the first index.
However not the indexes on table SC2T327F363DFA4T. Can't find any information for the indexes for this table. Did found note 959811. There it state that de indexes were deleted. But still stuck in the check_requirements of the SPAM Update!
Greetings,
Yammie

SAP_APPL(SAPKH60012)-eroor during Import_Proper phase

Hello All,
I has an ECC 6.0 sytem and was applying SAPKH60012-SAPKH60013 together.
During the TEST-IMPORT i got the following error for both the support package
"R3TRMSAGME was repaired in this system".
I had ignored the error during TEST_IMPORT.
But now i am stuck with this in my IMPORT_PROPER phase.
Please suggest, I did not find any SAP Notes for this error.
Also the main error
Error in phase :IMPORT_PROPER
Reason of the ERROR:TP_STEP_FAILUER
Return Code: 0008
Error Message :OCS Package SAPKH60012 , tp step "I",return Code 0008
Also i found in the log this error
Start import LIMUDOCUNAME818
R3TRMSAGME was repaired in this system
LIMUDOCUNAME818
Regards
Anthony
Edited by: Anthony D'souza on Mar 6, 2009 11:11 PM

Hi,
For this error "R3TRMSAGME was repaired in this system". You need to reset the repair fag by using tcode se03.
Also this error "TP_STEP_FAILUER" says that tp failed. If you have upgraded kernel level before sp upgrade then check current tp's version. If you have not upgraed tp.exe then download latest tp.exe & put it in your kernel path & restart the sp upgrade.
Please check ksap note for known problem in Support packs for your SAP release
Also check below threads. It will help you
Re: spam error in IMPORT_PORPER
tp
Thanks,
Sushil

Error Patch IMPORT_PROPER phase

Dear support,
We were applying patches on Netweaver 2004s Oracle 10.2.0.2 Windows platform server. Basis patch 12 and it was successfull in Test mode , but during standard mode suddenly machine got restarted because of power problem.
Now database and SAP is up and running , but i am unable to proceed with any of transactions ( like SPAM ) as i get syntax_error. Patch is in IMPORT_PROPER phase so i cannot reset until i do some database work.
What i am just aware i need to check entries in PAT01 , PAT02 , PAT03 and TRBAT tables and delete entries from PAT01 there to reset the queue and run patch again.
I can login to database with user SAPSR3 and there are entries for Basis patch 12 in table PAT01.Can anyone tell me further actions and querry which need to be executed to delete entry in detail , as i am having one week old backup which is not usefull for me.Please let me know safest way out of this issue.
Please help me at earliest.
Best Regards,
AjitR

praveen ,
I havent deleted any entry from tables , please find below
SQL> select PATCH,STEPCOND,RET_CODE,MESSAGE from PAT01;
PATCH STE RET_CODE
MESSAGE
SAPKB70012 ?
SQL> SELECT * FROM PAT02;
no rows selected
SQL> SELECT COUNT(*) FROM PAT03;
COUNT(*)
 33
SQL> SELECT COUNT(*) FROM PAT10;
COUNT(*)
 1
SQL> SELECT PATCH,STATUS,IMPL_MANDT from PAT10;
PATCH STA IMPL_MAND
SAPKB70012 R 000
SQL> SELECT RETCODE,CLIENT,ARGUMENT FROM TRBAT;
RETCODE CLIENT ARGUMENT
F
logs are as below
Transport request ; SAPKB70012
SQL error 1089 accessing : ORA-01089 immediate shutdown in progress - no ope
Main import
Ended with Return code 12
could you throw some light on the same.

Support Pack General Question:- IMPORT_PROPER phase

Hi All,
Is there any command at OS level to complete IMPORT_PROPER phase of SPAM transaction (support pack import)?

Hi ,
Is there any command at OS level to complete IMPORT_PROPER phase of SPAM transaction (support pack import) in My QAS system............. ?
I tried the following command in my DEV & QAS System.but not solved.
C:\>tp cleanbuffer qas pf=myprofile.pfl
This is tp version 320.56.89 (release 620)
E-myprofile.pfl could not be opened.
EXIT
Error in myprofile.pfl: transdir not set.
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0208
tp finished with return code: 208
meaning:
error in transportprofil (param missing, unknown,...)

SPAM update struck in IMPORT_PROPER phase

Similar Messages

Maybe you are looking for