ERP - EHP5 upgrade - error in phase Preprocessing - MAIN_SHDRUN/DDIC_UPG
Dear SAP,
I have started my upgrade from ERP EHP4 to EHP5.
During phase PreProcessing - the phase MAIN_SHDRUN/DDIC_UPG fails for the following reason :
In TP.SAV, I have this error :
ERRORS: Highest tp internal error was: 0232
TRACE-INFO: 32: [ dev trc,00000] OCIServerAttach(OCI_DEFAULT) failed with SQL error 12537: 58 0.045050
TRACE-INFO: 35: [ dbsloci.,00000] *** ERROR => CONNECT failed with sql error '12537' 32 0.045096
TRACE-INFO: 36: [ dev trc,00000] set_ocica() -> SQL error code 12537 15 0.045111
TRACE-INFO: 38: [ dev trc,00000] OCIErrorGet -> SQL error code: 12537 51 0.045175
TRACE-INFO: 41: [ dev trc,00000] SAPUSER or connect error 99=DBSL_ERR_DB, oerr=12537. 28 0.045221
TRACE-INFO: 43: [ dblink ,00000] ***LOG BY2=>sql error 12537 performing CON 60 0.045304
ERRORS: Highest tp internal error was: 0232
I have already changed the R3trans and tp executable.
Any help is very welcome.
Best regards
SAP NetWeaver Admin
Hi,
The phase is stopped with the following error
ERROR => CONNECT failed with sql error '12537'
SAPUSER or connect error 99=DBSL_ERR_DB, oerr=12537.
***LOG BY2=>sql error 12537 performing CON
***LOG BY0=>ORA-12537: TNS:connection closed
1AETW000 ===> HALT: reconnect to DB failed Please contact the SAP support.
4 ETW000 End of Transport (0016)
This issue is caused by misconfigured parameters for Oracle. The main
ones are the parameters: PROCESSES and SESSIONS.
Please check SAPnote # 1431798 and correct/increase the parameters.
then repeat the phase to proceed further with the upgrade.
Thank You.
Regards,
Deepika
Similar Messages
-
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 RamagowniHi 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 -
ERP6.0 EHP7 Upgrade error in phase PARCONV_TRANS
Hello,
If you have any idea or information , I hope your help!!
I'm upgrading ERP6.0 to ERP6.0 EHP7.
I have encountered the error in MAIN_TRANSEXEC/PARCONV_TRANS.
The error mesaages is like this:
Detected the following errors:
# Y:\SUM\SUM\abap\log\NCONV00.Q4R:
4 EDA093 "DDL time(___2):" ".........1" milliseconds
2 EGT066 Request for "/BA1/F4_RELEASE" executed successfully
1 ED0327XProcess..................: "MKIGTT01_10_15604"
2 EGT052XRequest: Create "Index /BCV/D_SSHOTT-SID (DDIC/10.07.14/20:12)"
3WEGT122 Nametab of table "/BCV/D_SSHOTT" with status "A" does not exist
2EEDA127 Table "/BCV/D_SSHOTT" for index "/BCV/D_SSHOTT~SID" does not exist in the database
2EEGT082 "Index" "/BCV/D_SSHOTT-SID" could not be created
2 EGT067 Request for "/BCV/D_SSHOTT" could not be executed
1 ED0327XProcess..................: "MKIGTT01_10_15604"
2 EGT052XRequest: Create "Index /BOBF/DM_LTXT_C-PAR (DDIC/10.07.14/20:12)"
3WEGT122 Nametab of table "/BOBF/DM_LTXT_C" with status "A" does not exist
2EEDA127 Table "/BOBF/DM_LTXT_C" for index "/BOBF/DM_LTXT_C~PA" does not exist in the database
2EEGT082 "Index" "/BOBF/DM_LTXT_C-PAR" could not be created
2 EGT067 Request for "/BOBF/DM_LTXT_C" could not be executed
...skipped 4006 more lines.
Please see PARCONV.html for more information.
I checked the table status. There were no database tables.
This is my second upgrade of EHP7. At first time , I choosed 'Starard' mode.
At this time I choosed 'Single System'.
I activated one table(/BA1/F4_RELEASE) and repeated phase , then passed its table.
But there are almost 1,300 talbes.
Is this bug of 'Single System' mode ?
Or is there any solution?
My configuraion is
OS: WIndows 2008 R2
DB: SQL Server 2008 R2
CPU: 2
memory: 16GB
Best regards,
Naritoshi AOKIPlease don't use Single System mode for EHP7 Upgrade.
1926261 - Central Note - Software Update Manager 1.0 SP11 [lmt_007]
As per this note,
Part C: General Problems / Information
I/ Important General Information
a) General
--------------------< D024828 JUL/07/2014 >-----------------------------
No Single System mode for target release >= SAP_BASIS 740 SP5
The preconfiguration mode Single System cannot be used for systems with a SAP_BASIS target release 740 SP 05 or higher.
Best regards
ashish -
EhP4-Upgrade: error in phase PREP_INPUT/KX_CPYORG
Hi!
I try to execute a EHP4 upgrade for SAP ECC system with EhP Installer.
The programm stopps after several repeat attempts in the the phase PREP_INPUT/KX_CPYORG.
The error I get is:
CURRENTPHASE PREP_INPUT/KX_CPYORG
...started at 20090320163915
Using phase log file 'KX_CPYORG.LOG'.
Kernel is replicated from D:\usr\sap\GE6\SYS\exe\nuc\NTAMD64.
Error message set: 'File 'D:\usr\sap\GE6\SYS\exe\nuc\NTAMD64\##f' does not exist: The system cannot find the file specified.
...begin dialogue at 20090320164430
How can I solve this problem?
Thank you very much!
regards
Ju00FCrgenHi
Don't know if it is still relevant (or even the same issue) but I had a similar problem with a file ##f not found directly after a mention of "reading dbclient.lst" in the log, and I fixed it by opening dbclient.lst in notepad and saving it again as ANSI. The original was Unicode and I noticed some other .lst file was ANSI. Hope this helps.
Best regards
Mischa -
EHP4-Upgrade: Errors in phase "TEST-IMPORT"
Hi!
During the upgrade of SAP ECC 6.0 to EHP4 we have the following errors in the phase "TEST_IMPORT".
Software-Package u201ESAPKH60401u201C
Function SERIAL_COPY_HU_MM (IPW3|11) does not fit into the existing function group((IPW1|65))
Function SERNR_ADD_BAPI_MM (IPW3|25) does not fit into the existing function group((IPW1|50))
Function SERNR_ADD_TO_HU (IPW3|15) does not fit into the existing function group((IPW1|63))
Function SERNR_ADD_TO_LS (IPW3|16) does not fit into the existing function group((IPW1|53))
Software-Package u201ESAPKGPFD05u201C
Function FTI_LDB_GET_SWAP_DETAILS (FTI_LDB_RAPI|01) does not fit into the existing function group((FTI_LDB_GET_OTC_DETAILS|01))
Software-Package u201ESAPKGPDD04u201C
Function /ISDFPS/ME_PM_MNTREL (/ISDFPS/ME_CA_FE|10) does not fit into the existing function group((/ISDFPS/ME_PM_MNTREL|01))
Software-Package u201ESAPKGPDD05u201C
Function /ISDFPS/ME_MM_AUTH_INV_COMP (/ISDFPS/ME_CA_FE|25) does not fit into the existing function group((/ISDFPS/ME_MM_STOCK|02)
Question:
How to proceed with these errors?
Thank you very much!Hi!
This one part of the relevant log files:
1 ETP199X
1 ETP152 TESTIMPORT
1 ETP101 transport order : "SAPKH60401"
1 ETP102 system : "GTE"
1 ETP108 tp path : "tp"
1 ETP109 version and release : "372.04.57" "701"
1 ETP198
4 ETW000 R3trans.exe version 6.14 (release 701 - 05.03.09 - 08:28:00).
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time : 02.06.2009 - 10:51:00
4 ETW000 control file:
gsdnt18\sapmnt\trans\tmp\SAPKKH60401.GTE
4 ETW000 > #pid 10328 on gsdnt38 (APServiceGTE)
4 ETW000 > testimport
4 ETW000 > file='
gsdnt18\sapmnt\trans\data\RH60401.SAP'
4 ETW000 > buffersync=no
4 ETW000 >
4 ETW000 R3trans was called as follows: R3trans.exe -w
gsdnt18\sapmnt\trans\tmp\SAPPH60401.GTE -u 1
gsdnt18\sapmnt\trans\tmp\SAPKKH60401.GTE
4 ETW000 active unconditional modes: 1
4 ETW000 Connected to DBMS = ORACLE --- dbs_ora_tnsname = 'GTE' --- SYSTEM = 'GTE'.
4 ETW690 COMMIT "0" "0"
4 ETW000 trace at level 1 opened for a given file pointer
4 ETW000
4 ETW000 ================== STEP 1 =====================
4 ETW000 date&time : 02.06.2009 - 10:51:00
4 ETW000 function : TESTIMPORT
4 ETW000 data file :
gsdnt18\sapmnt\trans\data\RH60401.SAP
4 ETW000 buffersync : NO
4 ETW000 clients : as exported
4 ETW000 l.s.m. : VECTOR
4 ETW000 commit : 100000
4 ETW000 table cache : dynamic
4 ETW000
4 ETW000 Character set on this machine : ASCII (ISO 8859-1).
4 ETW000 Character set on the data file: 2 byte unicode little endian.
4 ETW000 Data file is compressed with algorithm 'L'.
4 ETW000 Export was executed on 29.10.2008 at 19:46:23 by k4hadm
3 ETW709 "701 "
4 ETW000 with R3trans version: 15.10.08 - 15:49:00
4 ETW000 Source System = Solaris on x86_64 CPU on DBMS = ADABAS D --- DBNAME = 'K4H' --- SYSTEM = 'K4H'.
2EETW165 Function "SERIAL_COPY_HU_MM (IPW3|11)" does not fit into the existing function group "(IPW1|65)".
2 ETW167 Please transport the whole function group.
2EETW165 Function "SERNR_ADD_BAPI_MM (IPW3|25)" does not fit into the existing function group "(IPW1|50)".
2 ETW167 Please transport the whole function group.
2EETW165 Function "SERNR_ADD_TO_HU (IPW3|15)" does not fit into the existing function group "(IPW1|63)".
2 ETW167 Please transport the whole function group.
2EETW165 Function "SERNR_ADD_TO_LS (IPW3|16)" does not fit into the existing function group "(IPW1|53)".
2 ETW167 Please transport the whole function group.
4......
4 ETW690 COMMIT "0" "0"
4 ETW000 206188316 bytes read.
4 ETW000 Transport overhead 14.6 %.
4 ETW000 Data compressed to 7.6 %.
4 ETW000 Duration: 1:59 min (1732674 bytes/sec).
3 ETW710 "0" "0"
4 ETW000 [dev trc ,00000] Tue Jun 02 10:52:59 2009 119048128 119.048128
4 ETW000 [dev trc ,00000] Disconnecting from ALL connections: 339 119.048467
4 ETW000 [dev trc ,00000] Disconnecting from connection 0 ... 492 119.048959
4 ETW000 [dev trc ,00000] Closing user session (con_hdl=0,svchp=02410068,usrhp=0241C970) 1705 119.050664
4 ETW000 [dev trc ,00000] Detaching from DB Server (con_hdl=0,svchp=02410068,srvhp=024116AC) 2470 119.053134
4 ETW000 [dev trc ,00000] Now I'm disconnected from ORACLE 1563 119.054697
4 ETW000 [dev trc ,00000] Disconnected from connection 0 663 119.055360
4 ETW000 [dev trc ,00000] statistics db_con_commit (com_total=2, com_tx=2) 549 119.055909
4 ETW000 [dev trc ,00000] statistics db_con_rollback (roll_total=0, roll_tx=0) 694 119.056603
4 ETW000 Disconnected from database.
4 ETW000 End of Transport (0008).
4 ETW000 date&time: 02.06.2009 - 10:52:59
4 ETW000 102 warnings occured.
4 ETW000 4 errors occured.
1 ETP152 TESTIMPORT
1 ETP110 end date and time : "20090602105259"
1 ETP111 exit code : "8"
1 ETP199 -
Upgrade error in Phase STARTSAP_NBAS
Dear Experts,
We are doing ECC 5.0 upgrade to ERP6.0 SR3 and during STARTSAP_NBAS phase DDIC locking out and cant start SAP original system. We tried to unlock the password and also did the reset using SAPup reset DDICpwd. But its still locking out. and through SU01 its not allowing to reset the password of DDIC user using SAP* and its showing " adress is inconsistant".
Please help
Regards,
Pillai.Hi,
Could you try the steps from below thread?
STARTSAP_NBAS DDIC password locking out
Also, when you try resetting the password from SAPGui - do you get a dump in SU01? The address inconsistency warning can
be skipped in my opinion.
Regards,
Srikishan -
EHP5 Installation: Error in Phase PREP_INPUT/KX_CPYORG
Hi there,
happy new to year to all of you
I have a problem with the EHPI (latest version). In Phase "PREP_INPUT/KX_CPYORG" i get the following error:
KX_CPYORG.LOG:
1 ETQ200 Executing actual phase 'PREP_INPUT/KX_CPYORG'.
1 ETQ399 Source directory: D:\usr\sap\BIL\SYS\exe\nuc\NTAMD64
1 ETQ399 optional list file 'dbclient.lst' not found at directory 'D:\usr\sap\BIL\SYS\exe\nuc\NTAMD64' - copy files skipped
1 ETQ399 optional list file 'igsexe.lst' not found at directory 'D:\usr\sap\BIL\SYS\exe\nuc\NTAMD64' - copy files skipped
1 ETQ399 optional list file 'sapcrypto.lst' not found at directory 'D:\usr\sap\BIL\SYS\exe\nuc\NTAMD64' - copy files skipped
1 ETQ399 Using copy list: instance.lst
1 ETQ399 Using copy list: instancedb.lst
1 ETQ399 Copying files from 'D:\usr\sap\BIL\SYS\exe\nuc\NTAMD64' to 'D:\usr\sap\EHPI\abap\exe'
2 ETQ399 Reading list file 'D:\usr\sap\BIL\SYS\exe\nuc\NTAMD64\instance.lst'
The problem here is its an unicode System - ever was! and there is no path D:\usr\sap\BIL\SYS\exe\ nuc \NTAMD64 but a D:\usr\sap\BIL\SYS\exe\ uc \NTAMD64
The Systems' profile parameter OS_UNICODE says: "uc". DIR_CT_RUN says "D:\usr\sap\BIL\SYS\exe\uc\NTAMD64"
So why does the EHPI think this is a Non-Unicode system?
Any ideas?
regards,
MarkusWhen i check the files "BIL_DVEBMGS00_BILBO.PPR" and "START_DVEBMGS00_BILBO.PPR" from the EHPI directory D:\usr\sap\EHPI\abap\log\ i do find entries like
2 DIR_CT_RUN User: SAP: D:\usr\sap\BIL\SYS\exe\nuc\NTAMD64
and
2 OS_UNICODE User: SAP: nuc
But the question remains. Where does it take these ones from? The System profiles do not refer to "nuc" anywhere but always to "uc". -
Problem with the UPGRADE in the PHASE - DEPLOY_ONLINE
Hello Expert,
I have a problem when a try to execute the upgrade in the phase
DEPLOY_ONLINE,
<<<<<<<<<<<BEGIN TROUBLE TICKET >>>>>>>>>>>>>>>>>>>>>>
Trouble Ticket Report
Upgrade to SAP NetWeaver'04s
SID................: J2E
Hostname...........: sapepd
Install directory..: d:/usr/sap/J2E
Upgrade directory..: D:\SAPEPD\saploc\jupgrade
Database...........: Microsoft SQL Server
Operating System...: NT
JDK version........: 1.4.2_11 Sun Microsystems Inc.
SAPJup version.....: 1.1.101
Source release.....: 630
Target release.....: 700
Current usages.....: EP;AS;DI
ABAP stack present.: false
The execution of UPGRADE/UPGRADE/DEPLOY_ONLINE ended in error.
Error while executing SDM process phase with action DEPLOY_SLOT. See
D:\SAPEPD\saploc\jupgrade\log\DEPLOY_SLOT_0__DON_01.LOG for details.
Cannot execute Java process for deployList with parameters
D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.PRE.01.LST.
Return code condition success evaluated to false for process java.exe
for action ACTION_DEPLOY_LIST.
More information can be found in the log file
D:\SAPEPD\saploc\jupgrade\log\DEPLOY_ONLINE_DON_01.LOG.
Use the information provided to trouble-shoot the problem. There might
be an OSS note providing a solution to this problem. Search for OSS
notes with the following search terms:
com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess
com.sap.sdt.ucp.phases.PhaseException
Error while executing SDM process phase with action DEPLOY_SLOT. See
D:\SAPEPD\saploc\jupgrade\log\DEPLOY_SLOT_0__DON_01.LOG for details.
DEPLOY_ONLINE
UPGRADE
NetWeaver Upgrade
SAPJup
Java Upgrade
<<<<<<<<<<< END OF TROUBLE TICKET >>>>>>>>>>>>>>>>>>>>>>>>>
THE FILE: DEPLOY_ONLINE_DON_01.LOG
BEGIN DEPLOY_ONLINE_DON_01.LOG----
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[D:\SAPEPD\saploc\jupgrade\log\DEPLOY_ONLINE_DON_01.LOG]/>
<!PATTERN[DEPLOY_ONLINE_DON_01.LOG]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
#1.5#C000AC10C807000000000B1D010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#Java###Phase has been started.#1#UPGRADE/UPGRADE/DEPLOY_ONLINE#
#1.5#C000AC10C807000000000B1E010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#Java###Phase type is .#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess#
#1.5#C000AC10C807000000000B1F010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#Java### Parameter =#2#action#DEPLOY_SLOT#
#1.5#C000AC10C807000000000B20010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#Java### Parameter =#2#connect#standard#
#1.5#C000AC10C807000000000B21010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:755)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:755)#Java###Checking phase parameters .#1#action, connect#
#1.5#C000AC10C807000000000B22010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:764)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:764)#Java###Phase parameters have been checked. All required phase parameters have been set.#1#1#
#1.5#C000AC10C807000000000B23010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.createSlotDeployLists(PhaseTypeSDMProcess.java:1216)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.createSlotDeployLists(PhaseTypeSDMProcess.java:1216)#Java###Temporary file has been created.#1#D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.LST#
#1.5#C000AC10C807000000000B24010BC49D0004358E7146B8B8#1184785808931#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:46)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:46)#Java###Java process ID has been started.#1#249#
#1.5#C000AC10C807000000000B25010BC49D0004358E7146B8B8#1184785808931#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#Java###Command line: #2# #C:
j2sdk
jre
bin
java.exe -Xmx256M -Djava.ext.dir=d:/usr/sap/J2E/JC00/SDM/program/lib -cp . -jar d:
usr
sap
J2E
JC00
SDM
program
bin
SDM.jar deploy onerror=skipdepending updateversions=all list=D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.PRE.01.LST sdmHome=d:/usr/sap/J2E/JC00/SDM/program logfile=D:
SAPEPD
saploc
jupgrade
log
DEPLOY_SLOT_0__DON_01.LOG#
#1.5#C000AC10C807000000000B26010BC49D0004358E7146B8B8#1184785808931#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#Java###Standard out: #2# #D:
SAPEPD
saploc
jupgrade
log
DEPLOY_SLOT_0__DON_01.OUT#
#1.5#C000AC10C807000000000B27010BC49D0004358E7146F350#1184785808946#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#Java###Process ID has been started.#1#249#
#1.5#C000AC10C807000000000B28010BC49D0004358E7146F350#1184785808946#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#Java###Waiting for process ID , name to finish.#2#249#java.exe#
#1.5#C000AC10C807000000000B29010BC49D0004358E90915390#1184786333914#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#Java###Process ID , name has been finished, exit code .#3#249#java.exe#4#
#1.5#C000AC10C807000000000B2A010BC49D0004358E90918E28#1184786333929#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#Java###Exception has occurred during the execution of the phase.##
#1.5#C000AC10C807000000000B2B010BC49D0004358E90918E28#1184786333929#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.procx.DefaultProcessAdapter.checkReturnCode(DefaultProcessAdapter.java:513)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.procx.DefaultProcessAdapter.checkReturnCode(DefaultProcessAdapter.java:513)#Java###Return code condition success evaluated to false for process java.exe for action ACTION_DEPLOY_LIST.##
#1.5#C000AC10C807000000000B2C010BC49D0004358E90918E28#1184786333929#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.tools.sdmprocess.AbstractSDMProcessCall.deployList(AbstractSDMProcessCall.java:722)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.tools.sdmprocess.AbstractSDMProcessCall.deployList(AbstractSDMProcessCall.java:722)#Java###Cannot execute Java process for deployList with parameters D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.PRE.01.LST.##
#1.5#C000AC10C807000000000B2D010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.execute(PhaseTypeSDMProcess.java:735)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.execute(PhaseTypeSDMProcess.java:735)#Java###Error while executing SDM process phase with action DEPLOY_SLOT. See D:
SAPEPD
saploc
jupgrade
log
DEPLOY_SLOT_0__DON_01.LOG for details.##
#1.5#C000AC10C807000000000B2E010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#Java###Phase has been completed.#1#UPGRADE/UPGRADE/DEPLOY_ONLINE#
#1.5#C000AC10C807000000000B2F010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#Java###Start time: .#1#2007/07/18 15:10:08#
#1.5#C000AC10C807000000000B30010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#Java###End time: .#1#2007/07/18 15:18:53#
#1.5#C000AC10C807000000000B31010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#Java###Duration: .#1#0:08:45.030#
#1.5#C000AC10C807000000000B32010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#Java###Phase status is .#1#error#
*************END DEPLOY_ONLINE_DON_01.LOG*******************
FILE ************** DEPLOY_SLOT_0__DON_01.LOG
BEGIN DEPLOY_SLOT_0__DON_01.LOG----
The application start is forbidden, because of the server mode and action.
Jul 18, 2007 3:18:33 PM Info: Starting to save the repository
Jul 18, 2007 3:18:33 PM Info: Finished saving the repository
Jul 18, 2007 3:18:33 PM Info: Starting: Initial deployment: Selected development component 'tc/wd/samples/testsuite/uuie'/'sap.com'/'SAP AG'/'7.0010.20061002110342.0000'/'0' will be deployed.
Jul 18, 2007 3:18:33 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\samples\testsuite\uuie\SAP AG\0\7.0010.20061002110342.0000\TestSuiteUUIE.sda
Jul 18, 2007 3:18:33 PM Info: Software type of SDA: J2EE
Jul 18, 2007 3:18:33 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:36 PM Info: Begin of log messages of the target system:
07/07/18 15:18:33 - ***********************************************************
07/07/18 15:18:34 - Start updating EAR file...
07/07/18 15:18:34 - start-up mode is lazy
07/07/18 15:18:34 - EAR file updated successfully for 172ms.
07/07/18 15:18:34 - Start deploying ...
07/07/18 15:18:34 - EAR file uploaded to server for 500ms.
07/07/18 15:18:36 - ERROR: Not deployed. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy application sap.com/tcwdsamplestestsuiteuuie..
Reason: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1016)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
... 10 more
For detailed information see the log file of the Deploy Service.
07/07/18 15:18:36 - ***********************************************************
Jul 18, 2007 3:18:36 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:36 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:36 PM Error: Aborted: development component 'tc/wd/samples/testsuite/uuie'/'sap.com'/'SAP AG'/'7.0010.20061002110342.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/tcwdsamplestestsuiteuuie..
Reason: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Jul 18, 2007 3:18:36 PM Info: Starting to save the repository
Jul 18, 2007 3:18:36 PM Info: Finished saving the repository
Jul 18, 2007 3:18:36 PM Info: Starting: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'7.0011.20061227101805.0000'/'0' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4020.00.0000.20070308112146.0000'/'0'.
Jul 18, 2007 3:18:36 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\tools\SAP AG\0\7.0011.20061227101805.0000\WebDynproTools.sda
Jul 18, 2007 3:18:36 PM Info: Software type of SDA: J2EE
Jul 18, 2007 3:18:36 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:39 PM Info: Begin of log messages of the target system:
07/07/18 15:18:36 - ***********************************************************
07/07/18 15:18:36 - Start updating EAR file...
07/07/18 15:18:36 - start-up mode is lazy
07/07/18 15:18:37 - EAR file updated successfully for 375ms.
07/07/18 15:18:37 - Start updating...
07/07/18 15:18:37 - EAR file uploaded to server for 422ms.
07/07/18 15:18:39 - Successfully updated. Update took 1641ms.
07/07/18 15:18:39 - Deploy Service status:
07/07/18 15:18:39 - Application : sap.com/tcwdtools
07/07/18 15:18:39 -
07/07/18 15:18:39 - sap.com/tcwdtools - WEBDYNPRO
07/07/18 15:18:39 - sap.com/tcwdtools monitoring configuration - MONITORING CONFIGURATION
07/07/18 15:18:39 - ***********************************************************
Jul 18, 2007 3:18:39 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:39 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:39 PM Info: Finished successfully: development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'7.0011.20061227101805.0000'/'0', grouped by :
The application start is forbidden, because of the server mode and action.
Jul 18, 2007 3:18:39 PM Info: Starting to save the repository
Jul 18, 2007 3:18:40 PM Info: Finished saving the repository
Jul 18, 2007 3:18:40 PM Info: Starting: Update: Selected development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'7.0011.20070125102926.0000'/'0' updates currently deployed development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4020.00.0000.20070308112008.0000'/'0'.
Jul 18, 2007 3:18:40 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\wslib\SAP AG\0\7.0011.20070125102926.0000\WebDynproWsLib.sda
Jul 18, 2007 3:18:40 PM Info: Software type of SDA: library
Jul 18, 2007 3:18:40 PM Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:40 PM Info: Begin of log messages of the target system:
07/07/18 15:18:40 - ***********************************************************
07/07/18 15:18:40 - Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\wslib\SAP AG\0\7.0011.20070125102926.0000\WebDynproWsLib.sda...
07/07/18 15:18:40 - Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\wslib\SAP AG\0\7.0011.20070125102926.0000\WebDynproWsLib.sda successfully deployed on the server.
Jul 18, 2007 3:18:40 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:40 PM Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:40 PM Info: Finished successfully: development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'7.0011.20070125102926.0000'/'0', grouped by
Jul 18, 2007 3:18:40 PM Info: Starting to save the repository
Jul 18, 2007 3:18:41 PM Info: Finished saving the repository
Jul 18, 2007 3:18:41 PM Info: Starting: Initial deployment: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'7.0011.20050509144048.0000'/'0' will be deployed.
Jul 18, 2007 3:18:41 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\workflowmodeler\SAP AG\0\7.0011.20050509144048.0000\Modeler.sda
Jul 18, 2007 3:18:41 PM Info: Software type of SDA: J2EE
Jul 18, 2007 3:18:41 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:49 PM Info: Begin of log messages of the target system:
07/07/18 15:18:41 - ***********************************************************
07/07/18 15:18:41 - Start updating EAR file...
07/07/18 15:18:41 - start-up mode is lazy
07/07/18 15:18:42 - EAR file updated successfully for 1000ms.
07/07/18 15:18:42 - Start deploying ...
07/07/18 15:18:43 - EAR file uploaded to server for 891ms.
07/07/18 15:18:48 - Successfully deployed. Deployment took 5375ms.
07/07/18 15:18:48 - Application : sap.com/tc~workflowmodeler
07/07/18 15:18:48 -
07/07/18 15:18:48 - /Application/WorkflowModeler - LOGGING CONFIGURATION
07/07/18 15:18:48 - com.sap.workflowmodeler.modeler - LOGGING CONFIGURATION
07/07/18 15:18:48 - workflowBean - EJB
07/07/18 15:18:48 - WorkflowConnection - EJB
07/07/18 15:18:48 - Modeler - WEB
07/07/18 15:18:48 - sap.com/tc~workflowmodeler monitoring configuration - MONITORING CONFIGURATION
07/07/18 15:18:48 - ***********************************************************
Jul 18, 2007 3:18:49 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:49 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:49 PM Info: Finished successfully: development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'7.0011.20050509144048.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0':
The application start is forbidden, because of the server mode and action.
Jul 18, 2007 3:18:49 PM Info: Starting to save the repository
Jul 18, 2007 3:18:49 PM Info: Finished saving the repository
Jul 18, 2007 3:18:49 PM Info: Starting: Update: Selected development component 'tc_SL_SDM_Client'/'sap.com'/'SAP AG'/'7.0011.20061227100346.0000'/'0' updates currently deployed development component 'tc_SL_SDM_Client'/'sap.com'/'SAP AG'/'6.4014.00.0000.20050818153711.0000'/'0'.
Jul 18, 2007 3:18:49 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Client\SAP AG\0\7.0011.20061227100346.0000\SDMClient.sda
Jul 18, 2007 3:18:49 PM Info: Software type of SDA: library
Jul 18, 2007 3:18:49 PM Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:49 PM Info: Begin of log messages of the target system:
07/07/18 15:18:49 - ***********************************************************
07/07/18 15:18:49 - Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Client\SAP AG\0\7.0011.20061227100346.0000\SDMClient.sda...
07/07/18 15:18:49 - Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Client\SAP AG\0\7.0011.20061227100346.0000\SDMClient.sda successfully deployed on the server.
Jul 18, 2007 3:18:49 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:49 PM Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:50 PM Info: Finished successfully: development component 'tc_SL_SDM_Client'/'sap.com'/'SAP AG'/'7.0011.20061227100346.0000'/'0', grouped by
Jul 18, 2007 3:18:50 PM Info: Starting to save the repository
Jul 18, 2007 3:18:50 PM Info: Finished saving the repository
Jul 18, 2007 3:18:50 PM Info: Starting: Update: Selected development component 'tc_SL_SDM_Util'/'sap.com'/'SAP AG'/'7.0010.20061019070020.0000'/'0' updates currently deployed development component 'tc_SL_SDM_Util'/'sap.com'/'SAP AG'/'6.4014.00.0000.20050818153711.0000'/'0'.
Jul 18, 2007 3:18:50 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Util\SAP AG\0\7.0010.20061019070020.0000\SDMutil.sda
Jul 18, 2007 3:18:50 PM Info: Software type of SDA: library
Jul 18, 2007 3:18:50 PM Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:50 PM Info: Begin of log messages of the target system:
07/07/18 15:18:50 - ***********************************************************
07/07/18 15:18:50 - Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Util\SAP AG\0\7.0010.20061019070020.0000\SDMutil.sda...
07/07/18 15:18:50 - Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Util\SAP AG\0\7.0010.20061019070020.0000\SDMutil.sda successfully deployed on the server.
Jul 18, 2007 3:18:50 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:50 PM Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:50 PM Info: Finished successfully: development component 'tc_SL_SDM_Util'/'sap.com'/'SAP AG'/'7.0010.20061019070020.0000'/'0', grouped by
Jul 18, 2007 3:18:50 PM Info: Starting to save the repository
Jul 18, 2007 3:18:51 PM Info: Finished saving the repository
Jul 18, 2007 3:18:51 PM Info: Starting: Initial deployment: Selected development component 'tc/sdt/cvl'/'sap.com'/'SAP AG'/'7.0010.20060210160258.0000'/'0' will be deployed.
Jul 18, 2007 3:18:51 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\sdt\cvl\SAP AG\0\7.0010.20060210160258.0000\sap.comtcsdt~cvl.sda
Jul 18, 2007 3:18:51 PM Info: Software type of SDA: library
Jul 18, 2007 3:18:51 PM Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:52 PM Info: Begin of log messages of the target system:
07/07/18 15:18:51 - ***********************************************************
07/07/18 15:18:51 - Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\sdt\cvl\SAP AG\0\7.0010.20060210160258.0000\sap.comtcsdt~cvl.sda...
07/07/18 15:18:52 - Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\sdt\cvl\SAP AG\0\7.0010.20060210160258.0000\sap.comtcsdt~cvl.sda successfully deployed on the server.
Jul 18, 2007 3:18:52 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:52 PM Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:52 PM Info: Finished successfully: development component 'tc/sdt/cvl'/'sap.com'/'SAP AG'/'7.0010.20060210160258.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0'
Jul 18, 2007 3:18:52 PM Info: Starting to save the repository
Jul 18, 2007 3:18:52 PM Info: Finished saving the repository
Jul 18, 2007 3:18:52 PM Info: Starting: Initial deployment: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0' will be deployed.
Jul 18, 2007 3:18:52 PM Error: Aborted: software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0':
Failed deployment of SDAs:
development component 'tc/wd/samples/testsuite/uuie'/'sap.com'/'SAP AG'/'7.0010.20061002110342.0000'/'0' : aborted
Please, look at error logs above for more information!
Jul 18, 2007 3:18:52 PM Info: Starting to save the repository
Jul 18, 2007 3:18:52 PM Info: Finished saving the repository
Jul 18, 2007 3:18:52 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Jul 18, 2007 3:18:52 PM Error: -
At least one of the Deployments failed -
Jul 18, 2007 3:18:53 PM Info: Summarizing the deployment results:
Jul 18, 2007 3:18:53 PM Info: OK: D:\SAPEPD\saploc\jupgrade\data\archives\EPBC11_0-10003473.SCA
Jul 18, 2007 3:18:53 PM Error: Aborted: D:\SAPEPD\saploc\jupgrade\data\archives\SAPJTECHS11_0-10003467.SCA
Jul 18, 2007 3:18:53 PM Error: Processing error. Return code: 4
END DEPLOY_SLOT_0__DON_01.LOG----
I SAW the SDN forum and talk about the question
Nw2004s Upgrade: Error in phase DEPLOY_ONLINE
but this one doesnu00B4t work
best regards
Luis MorenoHi
I resolved the issue by undeploying the TestSuiteUUIE component using SDM.
Thanks
Naresh P. -
Can not pass with phrase MAIN_SHDRUN/DDIC_UPG
Dear Experts
Database : Oracle 11.2.0.2.0
ERP 6.0 EHP4 Ready
Installer EHP Level 74
In processing upgrade to EHP4
am facing a problem with step MAIN_SHDRUN/DDIC_UPG in phrase Preprocessing
System throws a errors:
Checks after phrase MAIN_SHDRUN/DDIC_UPG were negative !
Choose action :
1. Repeat Pharse
2. Initialize Phrase
3. Exit Program
I chose option Repeat Phrase for this step many times but warning still display. I do not find any logs about this
and then, i chose option Initialize Phrase and i have a reports
a patch job RDDIMPDP must be running in your SAP system with events
trigger enables. If this is not case, -> log into shadow instance and start
report RDDNEWPP as user DDIC in client 000
Choose action :
1. Scheduled
2.Exit
i chose Schedule options and and finally, can not continue
Please help me to resolve
Thanks and best regardsHello Myfriend,
am also facinf same problem while upgrading to ehp5 please give the solution if you know.
Error Details:
Checks after phase MAIN_SHDRUN/DDIC_UPG were negative!
Last error code set: 1 processes failed, check 'EXSTATC.*' for details
EXSTATC.EC1 log file:
TRACE-INFO: 1: [ dev trc,00000] Fri Nov 18 13:52:34 2011 2993 0.002993
TRACE-INFO: 2: [ dev trc,00000] DlLoadLib success: LoadLibrary("dboraslib.dll"), hdl 0, addr 11650000 14 0.003007
TRACE-INFO: 3: [ dev trc,00000] using "G:\EHP5_Down\EHPI\abap\exe\dboraslib.dll" 13 0.003020
TRACE-INFO: 4: [ dev trc,00000] -->DbSlConnect(vers=-1, type=0, env='[default]', userid='[default]') 173 0.003193
TRACE-INFO: 5: [ dev trc,00000] Prepending D:\usr\sap\IJE\SYS\exe\uc\NTI386 to Path. 250 0.003443
TRACE-INFO: 6: [ dev trc,00000] Register application info. 141 0.003584
TRACE-INFO: 7: [ dev trc,00000] Oracle client version: 10.2.0.1.0, (dbsl 720 190511, UNICODE[2]) 32004 0.035588
TRACE-INFO: 8: [ dev trc,00000] Detailed Oracle client (patch) info not available. 24 0.035612
TRACE-INFO: 9: [ dev trc,00000] Default connection: tnsname ='IJE' 89 0.035701
TRACE-INFO: 10: [ dev trc,00000] -->oci_initialize(con=0, char='UTF16', nchar='AL16UTF16'),uc_ln=2 36 0.035737
TRACE-INFO: 11: [ dev trc,00000] OCIEnvCreate(mode=16384=OCI_UTF16) returned 0 (for default NLS handle) 3464 0.039201
TRACE-INFO: 12: [ dev trc,00000] OCIHandleAlloc(OCI_HTYPE_ERROR, con=0, ErrHp=037D279C) 45 0.039246
TRACE-INFO: 13: [ dev trc,00000] OCIHandleAlloc(OCI_HTYPE_ERROR, con=0, ErrBt=037D2024) 24 0.039270
TRACE-INFO: 14: [ dev trc,00000] NLS env. settings: lang=41004D00450052004900430041004E00 137 0.039407
TRACE-INFO: 15: [ dev trc,00000] terr=41004D0045005200490043004100 21 0.039428
TRACE-INFO: 16: [ dev trc,00000] char=55005400460031003600 17 0.039445
TRACE-INFO: 17: [ dev trc,00000] Client NLS setting (by OCINlsGetInfo(con=0)): 'AMERICAN_AMERICA.UTF16' 17 0.039462
TRACE-INFO: 18: [ dev trc,00000] charset='UTF16', ncharset='AL16UTF16', UNI_ASC=FALSE 15 0.039477
TRACE-INFO: 19: [ dev trc,00000] Logon as OPS$-user to get SAPSR3's password 35 0.039512
TRACE-INFO: 20: [ dev trc,00000] Connecting as /@IJE on connection 0 (nls 0) ... (dbsl 720 190511, UNICODE[2])
TRACE-INFO: 21: 26 0.039538
TRACE-INFO: 22: [ dev trc,00000] OCIHandleAlloc(OCI_HTYPE_SVCCTX, con=0, svchp=037D1F70) 35 0.039573
TRACE-INFO: 23: [ dev trc,00000] Allocating server context handle 17 0.039590
TRACE-INFO: 24: [ dev trc,00000] Attaching to database server IJE (con=0, svchp=037D1F70, srvhp=037D591C) 54 0.039644
TRACE-INFO: 25: [ dev trc,00000] Fri Nov 18 13:53:55 2011 81019298 81.058942
TRACE-INFO: 26: [ dev trc,00000] OCIServerAttach(OCI_DEFAULT) failed with -1=OCI_ERROR 12 81.058954
TRACE-INFO: 27: [ dev trc,00000] OCIServerAttach(OCI_DEFAULT) failed with SQL error 12518: 114 81.059068
TRACE-INFO: 28: [ dev trc,00000] ORA-12518: TNS:listener could not hand off client connection
TRACE-INFO: 29: 27 81.059095
TRACE-INFO: 30: [ dbsloci.,00000] *** ERROR => CONNECT failed with sql error '12518' 31 81.059126
TRACE-INFO: 31: [ dev trc,00000] set_ocica() -> SQL error code 12518 19 81.059145
TRACE-INFO: 32: [ dev trc,00000] -->oci_get_errmsg (con=0, rc=12518) 15 81.059160
TRACE-INFO: 33: [ dev trc,00000] OCIErrorGet -> SQL error code: 12518 70 81.059230
TRACE-INFO: 34: [ dev trc,00000] ORA-12518: TNS:listener could not hand off client connection
TRACE-INFO: 35: 23 81.059253
TRACE-INFO: 36: [ dev trc,00000] SAPUSER error or connect error 99=DBSL_ERR_DB, oerr=12518. 18 81.059271
TRACE-INFO: 37: [ dev trc,00000] DbSlConnect(con=0) -> orc=0, 99=DBSL_ERR_DB 15 81.059286
TRACE-INFO: 38: [ dblink ,00000] ***LOG BY2=>sql error 12518 performing CON 54 81.059340
TRACE-INFO: 39: [ dblink ,00000] ***LOG BY0=>ORA-12518: TNS:listener could not hand off client connection 22 81.059362
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0232
tp finished with return code: 232
meaning:
connect failed
ERROR: Connect to IJE failed (20111118135355, probably wrong environment).
Thanks,
venkat -
EHP4 for ERP 6.0 upgrade phase MAIN_SHDRUN/DDIC_UPG running takes long time
Dear all,
I just tried to upgrade a fresh ERP 6.0 EHP4 ready (Linux X86_64 - Oracle) to EHP4 ERP 6.0.
I go through phase MAIN_SHDRUN/DDIC_UPG running, but it takes a very long times.
I checked the server resources usage, it 's very low.
I checked on my ERP 6.0 system and also the shadow system (background job, SM50), it seems no activities on both).
MAIN_SHDRUN/DDIC_UPG running - what is this phase about?
Its normal for this phase to takes about several hours??
What should i check to ensure that the upgrade process is still running?
How can i estimate time needed for this EHP4 upgrade?
I installed that freshERP 6.0 EHP4 ready system only on around 3-4 hours.
Regards,
Fendhy.Dear All,
I have same issue in ERP 6.0, EHP4 update, "MAIN_SHDRUN/DDIC_UPG" phase is still running, 24 hours passed. (only for this phase)
This is a NEW installation and on Production. I had no issues with DEV and QA and has taken only 50 minutes for the same phase.
Everything is same between DEV and PRD except, Production is on AIX HACMP cluster and using latest Ehpi installer + latest SPAM - version 41.
- There is no any error or warnings in /usr/sap/SID/EHPI/abap/log directory
- Phase is running, writing and reading files to installation directory
- No any automatic cluster fail-over mechanisms enabled
- Cluster has two nodes, DB+ASCS on one node and CI on other node.
- Shadow instance is running, can login, no errors in sm21, st22, no any running or canceled background jobs
- I can see 15% to 35% CPU "waits" in CI node where ehpi is running, but 50% of CPU is idle
- Also on same CI node, 70% to 100% disk busy waits can be seen on disks which mounted Ehpi installation directory
- On DB node CPU utilization and disk utilization is low
What could be the reason? Any idea ? How to diagnose.
Thanks,
P.D -
Upgrade to ERP EhP5 fails in phase RUN_GENPUTTBSHD
Hi
We are updating en ERP 604 to 605.
Phase RUN_GENPUTTBSHD fails during schedule of a batch job.
A dump is generated with this text:
Runtime Errors GEN_PROGRAM_NOT_EXISTS
Short text: Program "PUTTB_SHD" does not exist.
The program could be running from the shadow instance, but from what I can see a shadow instance has not yet been created yet.
Output from logfiles has been inserted below.
Anyone facing this kind of error? I have seen at least one similar issue but no solution provided.
Thanks
Brgds Tom
SAPEHPICONSOLE.LOG:
>> 2011/06/08 11:58:59 START OF PHASE PREP_IMPORT/SUBMOD_TOOLIMPORT_POST/RUN_GENPUTTBSHD
Starting of PUTTB_SHD generation in batch (job RS_GENERATE_PUTTB_SHD)
RSPTBINI.LOG:
1 ETQ201 Entering upgrade-phase "RUN_GENPUTTBSHD" ("20110608115859")
4 ETQ399 Set environment for standard connect:
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '00', GwService = 'sapgw00'
4 ETQ399 Environment variables:
4 ETQ399 dbs_mss_schema=ed1
4 ETQ399 auth_shadow_upgrade=0
1 ETQ206 Executing pre-phase DB specific actions.
1 ETQ200 Executing actual phase 'PREP_IMPORT/RUN_GENPUTTBSHD'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = 'RS_GENERATE_PUTTB_SHD'
2 ETQ399 Arg[1] = 'SAP_TMPLOG'
2 ETQ399 Arg[2] = 'NO-IGNORE'
2 ETQ399 Arg[3] = 'RS_GENERATE_PUTTB_SHD\.$(SAPSID)'
2 ETQ399 Arg[4] = '5'
2 ETQ399 Arg[5] = 'PUTTB_SHD generation'
2 ETQ399 Arg[6] = 'RSPTBINI.ELG'
4 ETQ010 Date & Time: 20110608115859
4 ETQ265 Starting report "RS_GENERATE_PUTTB_SHD" with variant "SAP_TMPLOG" in batch
4 ETQ359 RFC Login to: System="ED1", Nr="00", GwHost="bas01", GwService="sapgw00"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "SUBST_START_REPORT_IN_BATCH" by RFC
2WETQ360 RFC of "SUBST_START_REPORT_IN_BATCH" failed:
2WETQ361 code/exception : BATCH_SCHEDULING_FAILED
4 ETQ359 RFC Login to: System="ED1", Nr="00", GwHost="bas01", GwService="sapgw00"
4 ETQ232 RFC Login succeeded
2EETQ360 RFC of "SUBST_START_REPORT_IN_BATCH" failed:
2EETQ361 code/exception : BATCH_SCHEDULING_FAILED
2EETQ362 key : BATCH_SCHEDULING_FAILED
2EETQ364 message :
2EETQ399 EXCEPTION BATCH_SCHEDULING_FAILED RAISED
4 ETQ359 RFC Login to: System="ED1", Nr="00", GwHost="bas01", GwService="sapgw00"
4 ETQ232 RFC Login succeeded
2EETG894 Exception "BATCH_SCHEDULING_FAILED" raised, write variant failed with error code -1
2EETG890 Exception "BATCH_SCHEDULING_FAILED" raised, job scheduling failed with error code -1
2EETQ261 Start of batchjob "RS_GENERATE_PUTTB_SHD" failed
1 ETQ207 Executing post-phase DB specific actions.
4 ETQ010 Date & Time: 20110608120854
BATCHCHK_IMP.LOG:
1 ETQ201 Entering upgrade-phase "BATCHCHK_IMP" ("20110608084941")
4 ETQ399 Set environment for standard connect:
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '00', GwService = 'sapgw00'
4 ETQ399 Environment variables:
4 ETQ399 dbs_mss_schema=ed1
4 ETQ399 auth_shadow_upgrade=0
1 ETQ206 Executing pre-phase DB specific actions.
1 ETQ200 Executing actual phase 'PREP_IMPORT/BATCHCHK_IMP'.
4 ETQ260 Starting batchjob "RDDIT008"
4 ETQ010 Date & Time: 20110608084941
4 ETQ260 Starting batchjob "RDDIT008"
4 ETQ230 Starting RFC Login to: System = "ED1", GwHost = "bas01", GwService = "sapgw00"
4 ETQ359 RFC Login to: System="ED1", Nr="00", GwHost="bas01", GwService="sapgw00"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "SUBST_START_BATCHJOB" by RFC
4 ETQ399 JOBNAME='RDDIT008', REPNAME='RDDIT008', VARNAME='', BATCHHOST='bas01', IV_SCHEDEVER=' '
4 ETQ234 Call of function module "SUBST_START_BATCHJOB" by RFC succeeded
4 ETQ399 Returned JOBCOUNT='08494100'
4 ETQ233 Calling function module "SUBST_CHECK_BATCHJOB" by RFC
4 ETQ010 Date & Time: 20110608084946
4 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded
4 ETQ239 Logging off from SAP system
4 ETQ263 Batchjob "RDDIT008" finished successfully
1 ETQ207 Executing post-phase DB specific actions.
4 ETQ010 Date & Time: 20110608084946
SAPEHPICHK.LOG:
CURRENTPHASE PREP_IMPORT/SUBMOD_TOOLIMPORT_POST/RUN_GENPUTTBSHD
...started at 20110608103533
Using phase log file 'RSPTBINI.LOG'.
...begin dialogue at 20110608103534
...end dialogue at 20110608103537
..finished at 20110608103537 with status CALLING PUTTB_SHD generation FAILED.
Error message set: 'RFC call to SUBST_START_REPORT_IN_BATCH failed with key BATCH_SCHEDULING_FAILED (BATCH_SCHEDULING_FAILED): EXCEPTION BATCH_SCHEDULING_FAILED RAISED'
...begin dialogue at 20110608103538Hi
SAP got back with this info:
This error is caused due to the report RS_GENERATE_PUTTB_SHD being deleted druing the upgrade.
This is a recently discovered problem with the SAPehpi patch 81.
and the issue is fixed with the lateset version of SAPehpi.
It will import the report RS_GENERATE_PUTTB_SHD during TOOLIMPORT.
To use this version, you have to reset the current EHPI run and start from scratch with the new version
New version (83) downloaded, reset prepare and the phase was now completed
Thanks,
Tom -
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 JagtapDear 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 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, -
EHP4 upgrade Error - phase MAIN_SHDINST/RUN_RSVWSCPY were negative
Hello
Currently I am doing EHP4 upgrade on Oracle 10g with Sun Solaris 5.10 , During preprocessing phase ( The EhP Installation program builds the shadow system from the original one.)
I am getting following error
Checks after phase MAIN_SHDINST/RUN_RSVWSCPY were negative!
Last error code set: BATCH JOB RSUPG_COPY_SHD_VIEWS FAILED: Error(s) found in the log(s), accumulated in "RSVWSCPY.ELG".
Log file for RSVWSCPY.ELG as below
cat RSVWSCPY.ELG
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Clone shadow views ERRORS and RETURN CODE in RSVWSCPY.<SID>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1EETGCLN ORA-12154: TNS:could not resolve the connect identifier specified
1EETGCLN Unable to open connection to shadow system.
1EETGCLN Use function module CREATE_SHDDBCON to adjust the settings for connection UPGSHD.
cat sqlnet.ora
===========
AUTOMATIC_IPC = ON
TRACE_LEVEL_CLIENT = OFF
NAMES.DEFAULT_DOMAIN = WORLD
05.01.06 unsorported parameter now
#NAME.DEFAULT_ZONE = WORLD
05.01.06 set the default to 10
SQLNET.EXPIRE_TIME = 10
05.01.06 set to default
#TCP.NODELAY=YES
05.01.06 set to 32768
DEFAULT_SDU_SIZE=32768
cat tnsnames.ora
=============
<SID>.WORLD=
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = SAP.WORLD)
(PROTOCOL = TCP)
(HOST = <hostname>)
(PORT = 1527)
(CONNECT_DATA =
(SID = <SID>)
(GLOBAL_NAME = <SID>.WORLD)
===
Could you please help me to fix the issue.
Thanks , BMHello Orkur,
Like bharath reddy and others, I´m facing with the same error, but in my case the platform is OS/400 (V7R1M0) database DB4!
I´m doing an EHP5 upgrade and it stopped in phase MAIN_SHDINST/RUN_RSVWSCPY, the following error is show me:
Checks after phase MAIN_SHDINST/RUN_RSVWSCPY were negative!
Last error code set: BATCH JOB RSUPG_COPY_SHD_VIEWS FAILED: Error(s)
found in the log(s), accumulated in "RSVWSCPY.ELG".
In that RSVWSCPY.ELG file it have the following details:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Clone shadow views ERRORS and RETURN CODE in RSVWSCPY.PRD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1EETGCLN
1EETGCLN Unable to open connection to shadow system.
1EETGCLN Use function module CREATE_SHDDBCON to adjust the settings for connection UPGSHD.
I performed what you mentioned, I execute "Create_SHDDBCON" function module on SE37... but I didn´t continue this execution because I´m not sure what I have to fill in that parameters: DBUSER ; DBPASS and CONENV. You recommended some values to that fields/parameters... but where you have been seeking this values/information? How you know that?
Can you help me/us?
Thank you
JC project -
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,
JuliaAfter 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
Maybe you are looking for
-
AP vendors with same vendor number in two different companies
I am having trouble running the payment run f110 for two vendors in two different company codes. The vendor is the same so the vendor number was set up the same in two different company codes. I continue to get the error fcz003. I deleted all of th
-
How can I display an Internal from a frame
Hello, I have a frame application, inside the frame I have a jtable. when the users double click on a row from the table. I want to display an internalJFrame, which contain a tree with data on it. I try different combination with no luck. Below is th
-
PubSec Digital signatures in Acrobat 9
Hi, i m developing a digital signature plug-in, PubSec, to be specific. My plugin will, hopefully, digitally sign open pdf, and also able to verify them. The signature i am creating will be standard so that any other plugin, including Acrobat's own,
-
Will connect to router but not internet!!!
If there is anything I absolutely detest about Apple, it's the fact that their wifi *****. I have never had problems with my PowerPC iMac, but my two intels, a macbook and my newest, a macbook pro, have ALWAYS had connection problems. One of the prob
-
Syncing iph4 - unknown error (-50)
I am getting the following error message and my iph 4 wont sync calendars - unknown error (-50). Any suggestions?