SAINT error in phase DISASSEMBLE

Hi,
I am performing Delta-upgrade of component ST-SER from 700_2007_1 to 700_2008_1 via SAINT on our Solution Manager 4.0 system. (Windows server 2003 / MS SQL)
The SAR archive (KITLONB.SAR) is of 141 MB.
while trying to uncar i get following message:
SAPCAR: processing archive D:\SPS17\ST-SER_2008\Inst\KITLONB.SAR (version 2.01)
x EPS/in/CSR0120031469_0029513.ATT
x EPS/in/CSR0120031469_0029513.PAT
SAPCAR: error reading from D:\SPS17\ST-SER_2008\Inst\KITLONB.SAR
But the EPS files have been loaded in the system & visible in the queue as well.
The import fails in phase DISASSEMBLE with following error:
Error in phase - DISASSEMBLE
Reason for error - PATCH_FILE_READ_ERROR
Return code - 12
Error message - OCS Package : SAPKITLONB
File has Full Control given to groups Administrator, SAP_LocalAdmin and SYSTEM.
What could be the reason?

Check your SAPCAR executable.
File hasn't been uncared properly. You may uncar on your desktop and then transfer to server.
Other option is to load from SAINT tool > Load > Package from Application Server > Give location and it will uncar at right place.
Thanks,
Digesh
Edited by: digeshjoshi on Aug 14, 2009 5:01 PM

Similar Messages

Error in phase: DISASSEMBLE Reason for error: PATCH_FILE_READ_ERROR

Hello All
I am applying support Package: SAPKB70009 on SAP ECC 6.0 for component SAP_BASIS with release 700.
I am getting following error
The import was stopped, since an error occurred during the phase
DISASSEMBLE, 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: DISASSEMBLE
     -   Reason for error: PATCH_FILE_READ_ERROR
     -   Return code: 12
     -   Error message: OCS Package: SAPKB70009
Guys can you please shed some light on how to solve this issue.

Hi,
There might be 2 reaons for the error.
1) corrupted files in EPS/in or improper CAR of the files.
2) the file permissions in EPS/in check whether the files are having proper permssions like 775 with owner <SID>adm
-Srini

SAINT Error in Phase CHECK_REQUIREMENTS

Hi.Experts,
In a new SAP component installation with "t-cd:SAINT", an error occurred.
ERROR MESSAGE
=============================================
Phase CHECK_REQUIREMENTS: Explanation of Errors
Open conversion requests still exist in the ABAP 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.
=============================================
I have already checked 4 things of below
1.SE14－－＞BSEG
I can see the message below on the screen.
Request:"Adjust"　Error in step2 -see object log and analysis
2.SPAU
The contents related to BSEG are already modified (Green)
3.SPDD
The contents related to BSEG are already modified (Green)
4.SE10
There is no modifiable request related BSEG.
Could someone tell me about how to deal this error?
Best Regards,
Naomi

Hi Naomi
Could you check this SAP Note about your issue
1839881 - SPAM/SAINT error during CHECK_REQUIREMENTS regarding open conversion request still existing
BR
SS

Error in Import phase DISASSEMBLE when implementing KB70022

I'm trying to implement XI/PI netweaver 7.00 SAPKB70022 patch:
Always stays in the 'DISASSEMBLE' phase, the following log shows:
Saving the current Queue OCS (17.09.2010, 13: 34: 16)
001: SAPKB70022 - Support Package for SAP_BASIS Release 700
Import of the current Queue OCS (17.09.2010, 13: 34: 24)
The import is done with the standard scenario
The current OCS Queue consists of:
001: SAPKB70022
Import phase 'PROLOGUE' (17.09.2010, 13: 34: 26)
Import phase 'PROLOGUE' was successfully finished (17.09.2010, 13: 34: 26)
Import phase 'CHECK_REQUIREMENTS' (17.09.2010, 13: 34: 26)
Import phase 'CHECK_REQUIREMENTS' was successfully finished (17.09.2010, 13: 34: 28)
Import phase 'DISASSEMBLE' (17.09.2010, 13: 34: 28)
Ever happens here so if done in dialogue in bakcground.
In dialogue always appears in message bar 'tp user check1 and so remains indefinitely until I have to kill the process.
As background, BGD process runs on hold indefinitely...
I also tried to make 'Disassemble support Package' from the menu the SPAM Utilities also runs in the same State and must kill the process.
Decompressing support Package with single sapcar you extract the file:
CSR0120031469_0044188.PAT and never extracts the file .ATT
I several times what I downloaded SAP downloads site and never brings me the file. ATT.
I can not continue with the deployment of patches.
Thank you in advanced for your help.

Hi Fernando,
What SPAM/SAINT version do you have installed ?
Ensure it is the latest one.
If you are moving the files, check which method you are using.
Usually the transfer of files should be done with binary mode.
If you do get the data file and then get errors:
Please run the following command to check the datafiles consistency:
R3trans -l <datafile>
If you receive any return code different than 0, the datafile is indeed
corrupted, as the error message suggests (check-sum error in datafile).
Regards,
Paul

Error in PHASE ACT_UPG: Upgrade SAP R/3 4.7 to SAP ECC 6.0 EHP

Hello,
I'm facing an error in phase MAIN_SHDRUN/ACT_UPG (see errors below).
After searching for the errors I found postings with advice to change R3trans and tp to the newest version. Strangely system did not take the newest kernelpatch I stored in upgrade folder. So I changed the files in the /usr/sap/SID/abap/exe folder and repeated the phase.
But the error is still there.
A solution was to reset the queue, but this is only possible with help by sap.
Error in phase: DDIC_ACTIVATION
So I'm waiting for their reaction since two days, but nothing happens.
My questions are now:
what happens if I use the option "initialize phase ACT_UPG to restart it from beginning"? Will the new R3trans be used? Have we got to to the SPDD again?
What happens if I use the option "accept non severe errors and repeat phase ACT_UPG? Are these language errors "non-severe"?
Errors:
In error log ACTUPG.ELG I find logs like:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60016INERECRUIT.REX
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "8"
In error log SAPup.ECO I find:
EXECUTING /usr/sap/REX/upg/abap/exe/tp (/usr/sap/REX/upg/abap/exe/tp) pf=/usr/sap/REX/upg/abap/bin/ACTUPG.TPP put REX
This is /usr/sap/REX/upg/abap/exe/tp version 376.01.14 (release 701)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)
tp finished with return code: 8
meaning:
A tool used by tp produced errors
Process with ID 13163 terminated with status 8
In the last touched SP-File SAPAAAA701.SID I can find errors like:
"1EEDO545 "LANG" "DTEL" "*": Object information could not be imported"
Regards,
Julia

After pushing the message at SAP I got the following answer:
It is the problem from note 1417505. There is no guarantee that all objects where imported with the used R3trans. A rerun of phase will be unsuccessfully because error came up in DDIC_IMPORT.
A reset of the queue is only possible if SPAM/SAINT is used for importing support packages. In case of upgrade, like here, the upgrade has got to be resetted as described in upgrade guide.
After start between phase extraction and configuration the newest R3trans has got to be copied manually in /abap/exe folder.
Regards,
Julia

Saint Error - CHECK_REQUIREMENTS and QUEUE_NOT_EMPTY

Hi All,
I tried to install AAK pat file in a fresh system using the T-Code SAINT and I couldn't proceed forward as it is throwing error as shown below.In the attachment you can see the screen shots for the errors. I re-started and Re-stored the service twice and still it is reacting same. Could you please update me with the necessary steps to follow.
Appreciate your help.
Error in phase: CHECK_REQUIREMENTS
Reason for error: QUEUE_NOT_EMPTY
Thanks,
Nag.

Hi,
This is SAP Business one forum add-on. Please find correct forum and repost your discussion to get quick assistance.
Please close this thread here with helpful answer.
Thanks & Regards,
Nagarajan

Upgrading EA-PS 600 to 603 By Using SAINT Error in SAINT DDIC_ACTIVATION

Hello Team,
In our Production System We have ECC 6.0 Ehp-4,but for my public sector comp[onent i have EA-PS 600,i need to upgrade it to EA-PS 604, For that i need to upgrade to EA-PS 603 and then EHP-4,First im gng for EA-PS 603 ,by using SAINT Tool im dng this task,but in ddic_activation phase im facing the following problem
The installation was stopped, since an error occurred during the phase
DDIC_ACTIVATION, 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: DDIC_ACTIVATION
    -   Reason for error: TP_STEP_FAILURE
    -   Return code: 0012
    -   Error message: OCS Package SAPK-603DDINEAPS, tp step A, return
        code 0012...
Can any one please help me out to solve this issue,
immediate response appriciated...
Regards,
Syed.

Hi,
why you are upgrading it first to EHP3 and then to EHP4 ?
I will suggest you to directly upgrade it to EHP4, for this you just need to download stack xml file from solution manager and provide that in SAINT transaction so that it will upgrade to component to 604 in one step rather than 603 and then 604.
Thanks
Sunny

Error in phase: CHECK_REQUIREMENTS?

Hi,
I'm trying to loading a   BI_CONT 703 Installation: Meta-Commandfile (Delta Task) ( SAPKIIBH ) in SAINT but the system give me Error in phase: CHECK_REQUIREMENTS
Reason for error: TP_CANNOT_CONNECT_SYSTEM
Return code: 0208
Can some one help me
Babu

Hi,
Are you using latest tp/R3trans version ?
    Please check the TPPARAM file if the sapevtpath and transdir
variable has been set correctly.
It would usually be something like :
<SID>/sapevtpath          = /usr/sap/<SID>/SYS/exe/run/sapevt
TRANSDIR = /usr/sap/trans
cheers,
Vincent

Error in phase XPRAS_AIMMRG for Upgrade from 4.7 to ERP6 ehp5 sps5

Hi All,
We are in process in upgrading our sandbox system from 4.7 to ERP6.0
EHP5 SPS5.
During the downtime step we are facing an error in phase XPRAS_AIMMRG
Upon investigation we found that there are short dumps in the system
due to this error.
Below is the extract of the short dumps generated by the job RDDEXECL
Category Internal Kernel Error
Runtime Errors DDIC_TYPE_INCONSISTENCY
Application Component BC-ABA-LA
Date and Time 05.12.2011 08:58:48
Short text
Inconsistency in the dictionary for the structure "KOMG".
What happened?
Error in the SAP kernel.
The current ABAP "SAPLF82V" program had to be terminated because
the
ABAP processor detected an internal system error.
Also, We I try to check the Table KOMG in SE11 is get the below messages.
Check table KOMG (DDIC/05.12.11/10:00)
Append structure OILKOMG appended to table KOMG
Append structure OIUKOMG appended to table KOMG
No customer or SAP include SI_KOMK_CM exists
No customer or SAP include SI_KOMP_CM exists
No customer or SAP include CI_PRS_CPILS_2 exists
Enhancement category 3 possible, but include or subty. not
yet classified
Field LGORT in table KOMG is specified twice. Please check
KOMG-ZZMVGR4: Table TVM1T in search help attachment differs
from table of search field
Check on table KOMG resulted in errors
Has anyone received the below message in XPRAS phase during the upggrade.
Any suggestion would be most welcome.
Regards,
Nilesh Jagtap

Dear Nilesh,
The reason for this issue is that the component 'LGORT' is indeed specified twice in structure KOMG on your system.
It might be definied in the standard include as well as in your customer include.
Please bear in mind, that if you append customer own structures to SAP standad structures, that the component names should start with 'Z' or even better 'ZZ'.
That prevents the case which might have happened here, that the field you have added on customer side has also been delivered as part of an SAP standard include.
So you should change your structure accordingly.
Note 531835 describes how to add an own field to such structures. It might also be helpful for you.
After you have repaired your structure you can activate the structure KOMG and the issue should be solved.
Best Regards,
Abhishek

Error in phase: ADD_TO_BUFFER in SPAM during import of SAPKB70017 and 18

Hello
What is problem in this case? During import of SAPKB70017 and SAPKB70018 I get following error(there is no SLOG file in /usr/sap/trans/log):
The import was stopped, since an error occurred during the phase
ADD_TO_BUFFER, 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: ADD_TO_BUFFER
    -   Reason for error:
    -   Return code: 0211
    -   Error message:
Notes on phase ADD_TO_BUFFER
In this phase the queue is placed in the transport buffer of your
system. This phases can terminate due to the following reasons:
o   TP_INTERFACE_FAILURE: The tp interface could not be called. There is
     an RFC error.
o   CANNOT_ADD_PATCH_TO_BUFFER: A Support Package could not be included
     in the transport buffer. The program tp is trying to open a file in
     the file system. For more information, refer to the SLOG log file in
     the directory /usr/sap/trans/log.
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 .
A list of the most important SAP Notes for Online Correction Support
(OCS) is available in SAP Note 97620, which is updated regularly.

Hi Jan,
First, check whether your STMS is configured properly. Next check the transport directory and the transport tool from within STMS (system -> check in menu options).
If these 2 are ok, then you might check from within the OS layer by manually adding to buffer (tp add to buffer <Request No> <SID>).
Also, I am assuming you are doing this from client 000 with a non-standard user having proper authorizations.
I believe this to be an issue of permissions at the OS layer.
Regards
Siva

Error in phase MAIN_SHDRUN/SUBMOD_FDC_RUN/PARMVNT_FDC - EHP3 upgrade

Hello all,
Using SUM while running SCM 7.0 EHP3 upgrade I am getting error in phase MAIN_SHDRUN/SUBMOD_FDC_RUN/PARMVNT_FDC:
Checks after phase MAIN_SHDRUN/SUBMOD_FDC_RUN/PARMVNT_FDC were negative!
Last error code set: Single errors (code > 8) found in logfile 'MVNTFDC.ELG'<br/> 1 tp processes returned errors. View latest 'TP*.ECO' files in log-directory for details
ERROR: Detected the following errors:
# D:\SUM\abap\log\PD000203.SCD:
3 ETP000 NOT NULL )
3 ETP000 ON [/BIC/FZT_DEL_C1_PSCH000]
3 ETP000 WITH ( DATA_COMPRESSION = PAGE )
3 ETP000
2WETP000 11:10:14: Retcode 1: error in DDL statement for "/1CRR/TG00003781 " - repeat
2EETP345 11:10:26: Retcode 1: SQL-error "2726-Partition function '/BIC/FZT_DEL_C1_PFUN000' uses 1 c
2EETP345 olumns which does not match with the number of partition columns used to partition the tab
2EETP345 le or index." in DDL statement for "/1CRR/TG00003781 "
2 ETP000 --------------- DB-ROLLBACK() ---------------
2EETP334 11:10:26: error in DDL, nametab for "/1CRR/TG00003781" not activated
3 ETP000 NOT NULL )
3 ETP000 ON [/BIC/FZT_DEL_C2_PSCH000]
3 ETP000 WITH ( DATA_COMPRESSION = PAGE )
...skipped 18 more lines. Please see MVNTFDC.html for more information.
I checked some other log files:
MVNTFDC
1 ETQ201 Entering upgrade-phase "MAIN_SHDRUN/SUBMOD_FDC_RUN/PARMVNT_FDC" ("20150203110951")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '00', GwService = 'sapgw00' Client = '000'
1 ETQ206 Executing pre-phase DB specific actions.
1 ETQ200 Executing actual phase 'MAIN_SHDRUN/SUBMOD_FDC_RUN/PARMVNT_FDC'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = 'TP_MOVENTABS_SHD'
2 ETQ399 Arg[1] = 'INTDEL;INTACT;NOBUFFRESET;SHADOW_ONLY'
2 ETQ399 Arg[2] = 'MF=F,STEP=T,RANGE-TS'
2 ETQ399 Arg[3] = 'MVNTFDC.TP0'
1 ETQ399 Using error summary log 'MVNTFDC.ELG'.
1 ETQ399 Using 8 parallel processes
2 ETQ399 Empty putsteps - configuring at least parallel batches and main import processes.
2 ETQ399 Distribute 8 parallel processes to 2 tp and 4 R3trans.
4 ETQ380 computing toolpath for request "TP_MOVENTABS_SHD"
4 ETQ381 request "TP_MOVENTABS_SHD" means "tp mvntabs for shadow tables"
4 ETQ382 translates to group "R3UP_TOOL_GROUP_SHD"
4 ETQ399 Requirement for tp maps to 'exe'
4 ETQ383 translates to path "D:\SUM\abap\exe"
2 ETQ399 Starting 8 tp processes:
4 ETQ010 Starting: tp ddlntabs operation
3 ETQ121 20150203110952: PID 7444 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" "seltsize=0" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP00.ECO'.
2 ETQ399 Started tp ddlntabs with pid 7444
4 ETQ010 Starting: tp ddlntabs operation
3 ETQ121 20150203110952: PID 4888 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=01" "seltsize=1" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP01.ECO'.
2 ETQ399 Started tp ddlntabs with pid 4888
4 ETQ010 Starting: tp ddlntabs operation
3 ETQ121 20150203110952: PID 9100 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=02" "seltsize=2" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP02.ECO'.
2 ETQ399 Started tp ddlntabs with pid 9100
4 ETQ010 Starting: tp ddlntabs operation
3 ETQ121 20150203110952: PID 736 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=03" "seltsize=3" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP03.ECO'.
2 ETQ399 Started tp ddlntabs with pid 736
4 ETQ010 Starting: tp ddlntabs operation
3 ETQ121 20150203110952: PID 8864 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=04" "seltsize=4" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP04.ECO'.
2 ETQ399 Started tp ddlntabs with pid 8864
4 ETQ010 Starting: tp ddlntabs operation
3 ETQ121 20150203110952: PID 9264 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=05" "seltsize=5" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP05.ECO'.
2 ETQ399 Started tp ddlntabs with pid 9264
4 ETQ010 Starting: tp ddlntabs operation
3 ETQ121 20150203110952: PID 9732 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=06" "seltsize=6" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP06.ECO'.
2 ETQ399 Started tp ddlntabs with pid 9732
4 ETQ010 Starting: tp ddlntabs operation
3 ETQ121 20150203110952: PID 11492 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=07" "seltsize=7" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP07.ECO'.
2 ETQ399 Started tp ddlntabs with pid 11492
3 ETQ123 20150203110954: PID 9264 exited with status 0 (time 0.000 real)
2 ETQ399 tp ddlntabs finished with exit code 0.
3 ETQ123 20150203110954: PID 7444 exited with status 0 (time 0.000 real)
2 ETQ399 tp ddlntabs finished with exit code 0.
3 ETQ123 20150203110954: PID 4888 exited with status 0 (time 0.000 real)
2 ETQ399 tp ddlntabs finished with exit code 0.
3 ETQ123 20150203110954: PID 736 exited with status 0 (time 0.000 real)
2 ETQ399 tp ddlntabs finished with exit code 0.
3 ETQ123 20150203110954: PID 9732 exited with status 0 (time 0.000 real)
2 ETQ399 tp ddlntabs finished with exit code 0.
3 ETQ123 20150203110956: PID 11492 exited with status 0 (time 0.000 real)
2 ETQ399 tp ddlntabs finished with exit code 0.
3 ETQ123 20150203110956: PID 9100 exited with status 0 (time 0.000 real)
2 ETQ399 tp ddlntabs finished with exit code 0.
3 ETQ123 20150203110956: PID 8864 exited with status 0 (time 0.000 real)
2 ETQ399 tp ddlntabs finished with exit code 0.
2 ETQ399 Looking for pattern 'PD00....\.SCD'
2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD000203.SCD'.
1 ETQ124 Scanned file 'log\PD000203.SCD' from offset 9525 to 12695 for errors.
2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD00....\.SCD'
2 ETQ399 Looking for pattern 'PD01....\.SCD'
2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD010203.SCD'.
1 ETQ124 Scanned file 'log\PD010203.SCD' from offset 3394 to 6564 for errors.
2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD01....\.SCD'
2 ETQ399 Looking for pattern 'PD02....\.SCD'
2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD020203.SCD'.
1 ETQ124 Scanned file 'log\PD020203.SCD' from offset 3394 to 6564 for errors.
2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD02....\.SCD'
2 ETQ399 Looking for pattern 'PD03....\.SCD'
2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD030203.SCD'.
1 ETQ124 Scanned file 'log\PD030203.SCD' from offset 3394 to 6564 for errors.
2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD03....\.SCD'
2 ETQ399 Looking for pattern 'PD04....\.SCD'
2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD040203.SCD'.
1 ETQ124 Scanned file 'log\PD040203.SCD' from offset 3394 to 6564 for errors.
2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD04....\.SCD'
2 ETQ399 Looking for pattern 'PD05....\.SCD'
2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD050203.SCD'.
1 ETQ124 Scanned file 'log\PD050203.SCD' from offset 3394 to 6564 for errors.
2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD05....\.SCD'
2 ETQ399 Looking for pattern 'PD06....\.SCD'
2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD060203.SCD'.
1 ETQ124 Scanned file 'log\PD060203.SCD' from offset 3394 to 6564 for errors.
2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD06....\.SCD'
2 ETQ399 Looking for pattern 'PD07....\.SCD'
2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD070203.SCD'.
1 ETQ124 Scanned file 'log\PD070203.SCD' from offset 3394 to 6564 for errors.
2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD07....\.SCD'
2 ETQ399 Starting 1 tp processes:
4 ETQ010 Starting: tp ddlntabs operation
3 ETQ121 20150203111013: PID 8692 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP00.ECO'.
2 ETQ399 Started tp ddlntabs with pid 8692
3 ETQ123 20150203111050: PID 8692 exited with status 8 (time 0.000 real)
2EETQ399 tp ddlntabs failed with exit code 8.
2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD00....\.SCD'
1 ETQ124 Scanned file 'log\PD000203.SCD' from offset 12805 to 18826 for errors.
4 ETQ399 html file conversion from 'D:\SUM\abap\log\MVNTFDC.ELG' to 'MVNTFDC.html' succeeded.
4 ETQ010 Date & Time: 20150203111051
1EETQ399 Last error code set is: Single errors (code > 8) found in logfile 'MVNTFDC.ELG'
1 tp processes returned errors. View latest 'TP*.ECO' files in log-directory for details
1EETQ203 Upgrade phase "PARMVNT_FDC" aborted with errors ("20150203111051")
TP00.ECO
SAPup> Starting subprocess in phase 'TP_ACTION_CP2SINI' at 20150202112054
    ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
    ENV: PATH=D:\SUM\abap\exe;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;D:\Program Files\Microsoft SQL Server\100\Tools\Binn;D:\usr\sap\SCD\SYS\exe\uc\NTAMD64
    ENV: SAPSYSTEMNAME=SCD
    ENV: dbms_type=mss
    ENV: dbs_mss_schema=scd
    PWD: D:\SUM\abap\tmp
EXECUTING D:\SUM\abap\exe\tp.EXE "pf=D:\SUM\abap\var\CP2SHDI.TPP" r3e SAPKBBF740 -s SCD u18
This is D:\SUM\abap\exe\tp.EXE version 380.27.37 (release 741, unicode enabled)
This is D:\SUM\abap\exe\R3trans.exe version 6.24 (release 741 - 11.08.14 - 17:21:00).
unicode enabled version
D:\SUM\abap\exe\R3trans.exe finished (0004).
INFO: No client specified on command line. Taking client 0 from E070C.
tp finished with return code: 4
meaning:
A tool used by tp produced warnings
SAPup> Process with PID 7592 terminated with status 4 at 20150202112055!
SAPup> Starting subprocess in phase 'PARMVNT_FDC' at 20150202213004
    ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
    ENV: PATH=D:\SUM\abap\exe;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;D:\Program Files\Microsoft SQL Server\100\Tools\Binn;D:\usr\sap\SCD\SYS\exe\uc\NTAMD64
    ENV: SAPSYSTEMNAME=SCD
    ENV: dbms_type=mss
    ENV: dbs_mss_schema=scd
    PWD: D:\SUM\abap\tmp
EXECUTING D:\SUM\abap\exe\tp.EXE "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" "seltsize=0" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"
This is D:\SUM\abap\exe\tp.EXE version 380.27.37 (release 741, unicode enabled)
tp finished with return code: 0
meaning:
Everything OK
SAPup> Starting subprocess in phase 'PARMVNT_FDC' at 20150202213118
    ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
    ENV: PATH=D:\SUM\abap\exe;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;D:\Program Files\Microsoft SQL Server\100\Tools\Binn;D:\usr\sap\SCD\SYS\exe\uc\NTAMD64
    ENV: SAPSYSTEMNAME=SCD
    ENV: dbms_type=mss
    ENV: dbs_mss_schema=scd
    PWD: D:\SUM\abap\tmp
EXECUTING D:\SUM\abap\exe\tp.EXE "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"
This is D:\SUM\abap\exe\tp.EXE version 380.27.37 (release 741, unicode enabled)
tp finished with return code: 8
meaning:
A tool used by tp produced errors
SAPup> Process with PID 5336 terminated with status 8 at 20150202213638!
SAPup> Starting subprocess in phase 'PARMVNT_FDC' at 20150203102328
    ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
    ENV: PATH=D:\SUM\abap\exe;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;D:\Program Files\Microsoft SQL Server\100\Tools\Binn;D:\usr\sap\SCD\SYS\exe\uc\NTAMD64
    ENV: SAPSYSTEMNAME=SCD
    ENV: dbms_type=mss
    ENV: dbs_mss_schema=scd
    PWD: D:\SUM\abap\tmp
EXECUTING D:\SUM\abap\exe\tp.EXE "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" "seltsize=0" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"
This is D:\SUM\abap\exe\tp.EXE version 380.27.37 (release 741, unicode enabled)
tp finished with return code: 0
meaning:
Everything OK
SAPup> Starting subprocess in phase 'PARMVNT_FDC' at 20150203102350
    ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
    ENV: PATH=D:\SUM\abap\exe;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;D:\Program Files\Microsoft SQL Server\100\Tools\Binn;D:\usr\sap\SCD\SYS\exe\uc\NTAMD64
    ENV: SAPSYSTEMNAME=SCD
    ENV: dbms_type=mss
    ENV: dbs_mss_schema=scd
    PWD: D:\SUM\abap\tmp
EXECUTING D:\SUM\abap\exe\tp.EXE "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"
This is D:\SUM\abap\exe\tp.EXE version 380.27.37 (release 741, unicode enabled)
tp finished with return code: 8
meaning:
A tool used by tp produced errors
SAPup> Process with PID 10396 terminated with status 8 at 20150203102427!
SAPup> Starting subprocess in phase 'PARMVNT_FDC' at 20150203110952
    ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
    ENV: PATH=D:\SUM\abap\exe;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;D:\Program Files\Microsoft SQL Server\100\Tools\Binn;D:\usr\sap\SCD\SYS\exe\uc\NTAMD64
    ENV: SAPSYSTEMNAME=SCD
    ENV: dbms_type=mss
    ENV: dbs_mss_schema=scd
    PWD: D:\SUM\abap\tmp
EXECUTING D:\SUM\abap\exe\tp.EXE "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" "seltsize=0" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"
This is D:\SUM\abap\exe\tp.EXE version 380.27.37 (release 741, unicode enabled)
tp finished with return code: 0
meaning:
Everything OK
SAPup> Starting subprocess in phase 'PARMVNT_FDC' at 20150203111013
    ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
    ENV: PATH=D:\SUM\abap\exe;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;D:\Program Files\Microsoft SQL Server\100\Tools\Binn;D:\usr\sap\SCD\SYS\exe\uc\NTAMD64
    ENV: SAPSYSTEMNAME=SCD
    ENV: dbms_type=mss
    ENV: dbs_mss_schema=scd
    PWD: D:\SUM\abap\tmp
EXECUTING D:\SUM\abap\exe\tp.EXE "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"
This is D:\SUM\abap\exe\tp.EXE version 380.27.37 (release 741, unicode enabled)
tp finished with return code: 8
meaning:
A tool used by tp produced errors
SAPup> Process with PID 8692 terminated with status 8 at 20150203111050!
Can someone please help ?

Hi Pankaj,
did you get any solution for this issue ? I am also facing the same error in my BW upgrade to EHP3.
Please share the solution if you get any.
Regards,

Error in phase XPRA_EXECUTION while updating the SAP_BASIS patch !4

Hi ,
I am trying to update the sap_basis patch from level 13 to 14 . While updating I am getting
Error in phase: XPRA_EXECUTION
Reason for error: TP_STEP_FAILURE
Return code: 0012
Error message: OCS Package SAPKB70014, tp step R, return code
0012
In ST22 It says Syntax error in program "CL_CLS_ATTR_VALUE_ASSIGNMENT==CP
any help would be appreciated..
Regards,
Pradeep

This is what I get in the import log
The Syntax Error is given below
Execution of programs after import (XPRA)
Transport request   : SAPKB70014
System              : DEV
tp path             : tp
Version and release: 372.04.59 700
Program terminated (job: RDDEXECL, no.: 17163300)
    See job log
Execution of programs after import (XPRA)
End date and time : 20090518171648
Ended with return code: ===> 12 <===
untime Errors         SYNTAX_ERROR
Date and Time          18.05.2009 17:16:34
Short text
Syntax error in program "CL_CLS_ATTR_VALUE_ASSIGNMENT==CP ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLCLS_AFTER_IMPORT" had to be terminated because it
has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"CL_CLS_ATTR_VALUE_ASSIGNMENT==CP " in include
"CL_CLS_ATTR_VALUE_ASSIGNMENT==CM00D " in
line 1:
"Method "GET_DETAILS_OF_ASSIGNMENT" does not exist. The following simil"
"arly-named methods do exist: "GET_DESCRIPTION_OF_ASSIGNMENT", "GET_PAC"
"KAGES_OF_ASSIGNMENTS" and "GET_CLIENT_ASSIGNMENTS"."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "SAPLCLS_AFTER_IMPORT" had to be terminated because it
has
come across a statement that unfortunately cannot be executed.
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "CL_CLS_ATTR_VALUE_ASSIGNMENT==CP
You can also perform the syntax check from the ABAP Editor.
If the problem persists, proceed as follows:
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
The following syntax error was found in the program
CL_CLS_ATTR_VALUE_ASSIGNMENT==CP :
"Method "GET_DETAILS_OF_ASSIGNMENT" does not exist. The following simil"
"arly-named methods do exist: "GET_DESCRIPTION_OF_ASSIGNMENT", "GET_PAC"
"KAGES_OF_ASSIGNMENTS" and "GET_CLIENT_ASSIGNMENTS"."
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.

EHP4 upgrade: Error in Phase ACT_UPG

Hi All,
While upgrading to EHP4 on ECC 6 system, we got error in phase MAIN_SHDRUN/ACT_UPG
Checks after phase MAIN_SHDRUN/ACT_UPG were negative!
Last error code set: Unresolved requests in buffer RH4 Check logfiles 'ACTUPG.ELG' and '/sapdump/SAPehpi/EHPI/abap/log/SAPehpi.ECO'
ACT_UPG log:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-604DMINISPSCA.RH4
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code           : "12"
Log of SAPA-604DMINISPSCA.RH4
1 ETP155 ACTIVATION OF DD-OBJECTS
1 ETP101 transport order     : "SAPK-604DMINISPSCA"
1 ETP102 system              : "RH4"
1 ETP108 tp path             : "/sapdump/SAPehpi/EHPI/abap/exe/tp"
1 ETP109 version and release : "372.04.70" "700"
1 ETP198
3 EPU324 See log for request "/sapdump/SAPehpi/EHPI/abap/tmp/SAPAB70015.RH4" (timestamp "01:26:08", system "RH4")
1AETR012XProgram terminated (job: "RDDMASGL", no.: "01260600")
1AEPU320 See job log"RDDMASGL""01260600""RH4"
1 ETP155 ACTIVATION OF DD-OBJECTS
1 ETP110 end date and time   : "20091012033215"
1 ETP111 exit code           : "12"
1 ETP111 exit code           : "12"
Job RDDMASG log :
Job cancelled with following log
2.10.2009 01:26:07 Job started                                                               00           516          S
2.10.2009 01:26:07 Step 001 started (program RDDMASGL, variant IMPACTMRG, user ID DDIC)      00           550          S
2.10.2009 01:26:08 Start of mass activation 01:26:08                                         AD           010          S
when tried to log into shadow instance after getting error, it is giving error
RH4: system message
work process restarted; session terminated;
we restarted shadow system. There is no dumps in the shadow system.
Work process getting killed after 7800s
checked in work directory of Shadow system: devdisp log :_*
Mon Oct 12 04:49:46 2009
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c   1694]
***LOG Q0K=> DpMsAttach, mscon ( HW136799) [dpxxdisp.c   12639]
DpStartStopMsg: send start message (myname is >HW136799_RH4_22                         <)
DpStartStopMsg: start msg sent
Warning: Swap space is configured quite small with 20477 MB.
It should be configured with at least 20 GB on 64 bit systems.
See note 153641 for more information.
Warning: tmpfs at /dev/shm is configured quite small with 1972 MB!
Minimum value is 8192 MB.
Recommended size is 75 % of RAM + swap.
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
Mon Oct 12 04:49:47 2009
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1050]
DpMsgAdmin: Set patchno for this platform to 221
Release check o.K.
MBUF state ACTIVE
DpModState: change server state from STARTING to ACTIVE
Mon Oct 12 06:57:01 2009
ERROR => DpWPCheck: W8 (pid 9769) died (severity=0, status=7) [dpxxdisp.c   15776]
child (pid=9769) killed with signal 7
Mon Oct 12 06:57:43 2009
ERROR => DpWPCheck: W7 (pid 9768) died (severity=0, status=7) [dpxxdisp.c   15776]
child (pid=9768) killed with signal 7
Please let us know what needs to be cheked for the problem
Thanks,
Ramesh Ramagowni

Hi Markas and All,
Thanks for the information. /dev/shm was 100% full. now, the issue is solved after deleting its contents. and we have finished with EHP4 upgrade.
After upgrade, SAP_AP component still showing as 700
SAP_AP - 700 - 0015 - SAPKNA7015 -SAP Application Platform
Can we delete old tablespace PSAPSR3700, it is showing as 0% used in brspace at present.
Also while trying to move some datafiles using brtools after upgrade we are getting following error,
BR0280I BRTOOLS time stamp: 2009-10-20 01.45.52
BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort:
c
BR0280I BRTOOLS time stamp: 2009-10-20 01.45.54
BR0257I Your reply: 'c'
BR0259I Program execution will be continued...
BR0252E Function fopen() failed for '/oracle/RH4/sapbackup/.user.pas' at location BrToolCall-2
BR0253E errno 13: Permission denied
BR0669I Cannot continue due to previous warnings or errors - you can go back to repeat the last action
BR0280I BRTOOLS time stamp: 2009-10-20 01.45.54
BR0671I Enter 'b[ack]' to go back, 's[top]' to abort:
There is no file in the directory '/oracle/RH4/sapbackup/.user.pas'
Please suggest what needs to be for this issue..Do we need to upgrade BRTOOLS..
Thanks,
Ramesh R

Error in Phase 44/44 installing SM 4.0 SR3 on Windows 2003 64 bit Oracle 10

Hello All,
this is my first post here and I'm having issue installing SM 4.0 SR3. It stops with an error on Phase 44/44. here's the error log. I've tride searching for answer but no luck. can anybody please help?
Solution Manager 4.0 SR3 64 bit Installation
Windows 2003 R2 64 bit
Oracle Database 10g
Java 1.5.0_14 64 bit
INFO 2008-01-17 11:34:22.483
Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.8.xml'.
INFO 2008-01-17 11:34:22.530
Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.9.xml'.
INFO 2008-01-17 11:34:24.124
Execute step Component W2K_ServicePack_Check|ind|ind|ind|indPreprocess of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|0|0|W2K_ServicePack_Check|ind|ind|ind|ind|2|0.
INFO 2008-01-17 11:34:38.108
Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/keydb.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/keydb.5.xml'.
INFO 2008-01-17 11:34:38.342
Execute step callOfflineCTC of component |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|5|0|NW_Call_Offline_CTC|ind|ind|ind|ind|7|0.
INFO 2008-01-17 11:34:39.404
Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\LaunchOfflinectc.bat.log.
INFO 2008-01-17 11:34:39.436
Working directory changed to E:/usr/sap/S20/DVEBMGS00/j2ee/ctc.
INFO 2008-01-17 11:34:39.451
Working directory changed to C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS.
INFO 2008-01-17 11:34:39.467
Output of E:\usr\sap\S20\DVEBMGS00\j2ee\ctc\LaunchOfflinectc.bat is written to the logfile LaunchOfflinectc.bat.log.
WARNING 2008-01-17 11:34:42.107
Execution of the command "E:\usr\sap\S20\DVEBMGS00\j2ee\ctc\LaunchOfflinectc.bat" finished with return code 1. Output: 1 file(s) copied.java.io.BufferedInputStream@6686fe26Jan 17, 2008 11:34:39... ....tc.lm.ctc.OfflineTemplateImporterJAR [Thread[main,5,main]] Info: Start Execution of Offline CTC TemplatInstallerJan 17, 2008 11:34:39... ....tc.lm.ctc.OfflineTemplateImporterJAR [Thread[main,5,main]] Info: Looking for initial Properties in file '../../../config/usagetypes.properties'Jan 17, 2008 11:34:39... ....tc.lm.ctc.OfflineTemplateImporterJAR [Thread[main,5,main]] Info: Loading of initial Properties-File successful Jan 17, 2008 11:34:39... ....tc.lm.ctc.OfflineTemplateImporterJAR [Thread[main,5,main]] Info: Selected Usages:SolManager:SolManager JavaPerfTimes : loadNativeLayer: loading jperflib failed. no jperflib in java.library.pathJan 17, 2008 11:34:41... ...c.cul.cpi.exceptions.CPIBaseException [Thread[main,5,main]] Path: Exception : The proivder ConfigManagerProvider is not able to startupjava.lang.Exception at com.sap.exception.BaseExceptionInfo.traceAutomatically(BaseExceptionInfo.java:1141) at com.sap.exception.BaseExceptionInfo.<init>(BaseExceptionInfo.java:413) at com.sap.exception.BaseException.<init>(BaseException.java:302) at com.sap.tc.lm.ctc.cul.cpi.exceptions.CPIBaseException.<init>(CPIBaseException.java:63) at com.sap.tc.lm.ctc.provider.configurationmanager.exceptions.ConfigManagerProviderBaseException.<init>(ConfigManagerProviderBaseException.java:52) at com.sap.tc.lm.ctc.provider.configurationmanager.offline.ConfigurationManagerOfflineStartup.createProvider(ConfigurationManagerOfflineStartup.java:59) at com.sap.tc.lm.ctc.cul.offline.OfflineCTCFramework.startupSystem(OfflineCTCFramework.java:69) at com.sap.tc.lm.ctc.OfflineTemplateImporterJAR.executeWizard(OfflineTemplateImporterJAR.java:113) at com.sap.tc.lm.ctc.OfflineTemplateImporterJAR.main(OfflineTemplateImporterJAR.java:549) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)Caused by: com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB. at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:360) at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:125) at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38) at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149) at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236) at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49) at com.sap.tc.lm.ctc.provider.configurationmanager.offline.ConfigurationManagerOfflineStartup.createProvider(ConfigurationManagerOfflineStartup.java:57) at com.sap.tc.lm.ctc.cul.offline.OfflineCTCFramework.startupSystem(OfflineCTCFramework.java:69) at com.sap.tc.lm.ctc.OfflineTemplateImporterJAR.executeWizard(OfflineTemplateImporterJAR.java:113) at com.sap.tc.lm.ctc.OfflineTemplateImporterJAR.main(OfflineTemplateImporterJAR.java:549) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)Caused by: java.sql.SQLException: Io exception: The Network Adapter could not establish the connection at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:255) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:387) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:420) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801) at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215) at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608) at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285) at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:302) ... 14 more
ERROR 2008-01-17 11:34:42.139
CJS-00030 Assertion failed: in function NW_Call_Offline_CTC_ind_ind_ind_ind_SubComponentContainer_callOfflineCTC() { var nw = NWInstall.getSystem(context.get("sid")); var ctcDirFs = nw.getCI().getInstanceDir().concat("j2ee", "ctc"); var ctcExeFile = installer.onWindows() ? "LaunchOfflinectc.bat" : "LaunchOfflinectc.sh"; var ctcCall = ctcDirFs.concat(ctcExeFile); installer.writeTrace("CTC is in" + ctcCall); ASSERT(arguments.callee, ctcCall.isExisting(), "CTC executable cannot be found in " + ctcCall.toString()); var pmgt = new ProcessMgt(); var app = pmgt.createChildApplication(ctcCall, []); var userData = nw.getUsers().getAccountData(NWUsers.roles.SIDAdm); var user = (new AccountMgt()).getUser(userData.name); var env = pmgt.getProcessEnvironment(); if (installer.onUnix()) { env.setUser(user); } env.setWorkingDirectory(ctcDirFs.getNode()); env.setEnvironmentVariable(new Property("JAVA_HOME", nw.getJavaHome().toString())); installer.writeTrace("For the Offline CTC Call, JAVA_HOME is set to " + env.getEnvironmentVariable("JAVA_HOME")); app.setEnvironment(env); var retval = app.run([], true); ASSERT(arguments.callee, retval == 0, "CTC retval is not 0 but " + retval); installer.writeTrace("CTC has been called in Offline Mode.");}CTC retval is not 0 but 1
ERROR 2008-01-17 11:34:42.217
MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
ERROR 2008-01-17 11:34:42.264
FCO-00011 The step callOfflineCTC with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|5|0|NW_Call_Offline_CTC|ind|ind|ind|ind|7|0|callOfflineCTC was executed with status ERROR .

Uninstall Java 1.5 - it will not work.
You MUST use Java 1.4 for 64bit windows from note 941595 - Download J2SE 1.4.2 for the x64 platform
I suggest you start over with your installation since the wrong path is in quite a few locations.
Markus

Import ECC6 using DB2 9.5 in Windows 2003 server got error in Phase Insatlla database soft ware .

Hi Expert,
When i am going to import ECC6 in windows 2003 server using DB9.5 i got error in phase Install data base software like below.
Invalid command line argument. consult the windows installer SDK for detailed command line help.
Please help me for this error.
Thanks in Advance.
Thanks
J Jana

'invalid command line argument' - Most probably the SAPinst is not able to find the right path for the DB2 UDB DVD or the the argument is too long to interpret which is a very common problem during installations.
Check the path for db2 DVD, and keep it shorter - that means you have to reduce the number of folders where the DVD resides. Copy the DVD in a short path let's say C:\DB2\dvdname and re-try installation by giving the new path of dvd in SAPinst.
Thank you.

SAINT error in phase DISASSEMBLE

Similar Messages

Maybe you are looking for