Error in START_J2EE_INITIAL phase of PI7.1 Ehp1 Upgrade

START_J2EE_INITIAL_TJI_02.LOG
com.sap.sdt.j2ee.phases.PhaseTypeControlEngine com.sap.sdt.ucp.phases.PhaseException Could not start AS Java instance with name J2EE and number 03 of the standard system. START_J2EE_INITIAL DOWNTIME UPGRADE NetWeaver Upgrade SAPJup Java Upgrade
dev_server0 log
F [Thr 26215] Tue Dec  1 20:22:27 2009
F  [Thr 26215] *** WARNING => SfCFramework::registerNatives: failed for com.sap.conn.rfc.driver.CpicDriver [sfxxifrw.hpp 165]

M [Thr 21075] Tue Dec  1 20:22:46 2009
M  [Thr 21075] ***LOG Q0I=> NiPConnect: 127.0.0.1:3305: connect (79: A remote host refused an attempted connect operation.) [nixxi.cpp 2777]
M  [Thr 21075] *** ERROR => NiPConnect: SiConnect failed for hdl 25/sock 72
    (SI_ECONN_REFUSE/79; I4; ST; 127.0.0.1:3305) [nixxi.cpp    2777]
std_server0.  log
Service [com.sap.security.core.ume.service] start ================= ERROR =================
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: com.sap.conn.jco.JCoException: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
Connection parameters: TYPE=A DEST=SAPJup ASHOST=localhost SYSNR=05 PCS=1
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       partner '127.0.0.1:3305' not reached
TIME        Tue Dec  1 20:17:29 200
RELEASE     711
COMPONENT   NI (network interface)
VERSION     39
RC          -10
MODULE      nixxi.cpp
LINE        2777
DETAIL      NiPConnect: 127.0.0.1:3305
SYSTEM CALL connect
ERRNO       79
ERRNO TEXT  A remote host refused an attempted connect operation.
COUNTER     3
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:446)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:155)
     at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:60)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: com.sap.conn.jco.JCoException: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
Connection parameters: TYPE=A DEST=SAPJup ASHOST=localhost SYSNR=05 PCS=1
In this phase it is trying to starup the instance with 03 sys no, but std_server0 log shows that ume service is trying to connect
to instance with sys-no 05 ( shadow).
I also refered to the wiki link,
https://wiki.sdn.sap.com/wiki/pages/viewpage.action?spaceKey=JSTSG&title=(SLTG)(SAPJUP)+Problems-P1&decorator=printable
where it says the DDIC password needs to be same in both 000 and the ume store client ( eg 030), which i checked in our case
and the DDIC password is the same,
Experts please help, helpful answers will be fully rewarded with points.
Thanks,
Govind
Edited by: Govind Prathi on Dec 2, 2009 5:24 PM
Edited by: Govind Prathi on Dec 2, 2009 5:27 PM

Hi Govind,
please post the /work/dev_jcontrol trace file.
maybe the following link helps you to analyze your problem regarding RFC_ERROR_COMMUNICATION
http://help.sap.com/saphelp_nw70/helpdata/EN/20/361941edd5ef23e10000000a155106/content.htm
Please have a look in dev_jrfc.trc files. These files are written by JRFC and can be found in the directories j2ee/cluster/server* of the J2EE Application Server Installation. The following document describes, how tracing can be switched on/off:
http://help.sap.com/saphelp_nw70/helpdata/en/f6/daea401675752ae10000000a155106/content.htm
Be sure that j2ee_admin user is not locked.
Check /etc/services for '127.0.0.1:3305'
please also be sure that the UME.Properties settings in com.sap.security.core.ume.service are correct:
Please start offline configtool, goto cluster_data - server - cfg - services and check the property sheet
com.sap.security.core.ume.service
please also update ume.r3.connection.master.ashost with hostname of your portal server.
then restart your JAVA instance.
Is this dual stack (ABAP+JAVA) ?
Does your system is running on High Availability server?
Gerd
Edited by: Gerd Schuster on Dec 2, 2009 5:09 PM
Edited by: Gerd Schuster on Dec 2, 2009 5:20 PM

Similar Messages

  • Error in XPRAS_AIMMRG phase | Netweaver 7.4  BW Upgrade

    Hello Experts,
    We are upgrading our BW system from SAP Netweaver 7.0 to 7.4.
    The phase XPRAS_AIMMRG in Execution section of the tool is running for a very long time.
    We have observed the below error Message in MSGOUT.LOG-
    SAPup> Starting subprocess with PID 25929 in phase 'XPRAS_AIMMRG' at
    20140515124210
    ENV: DIR_LIBRARY=/sapbkpbbd/upgdir/SUM/abap/exe
    ENV: JAVA_HOME=/usr/jdk/j2sdk1.4.2_16
    ENV:
    LD_LIBRARY_PATH=/sapbkpbbd/upgdir/SUM/abap/exe:/sapbkpbbd/upgdir/SUM/jvm/jre/lib/sparcv9/server:/sapbkpbbd/upgdir/SUM/jvm/jre/lib/sparcv9:/sapbkpbbd/upgdir/SUM/jvm/jre/../lib/sparcv9:/usr/sap/BBD/SYS/exe/run:/usr/sap/BBD/SYS/exe/uc/sun_64:/oracle/client/11x_64/instantclient
    ENV: NLS_LANG=AMERICAN_AMERICA.UTF8
    ENV: ORACLE_BASE=/oracle
    ENV: ORACLE_HOME=/oracle/BBD/112_64
    ENV: ORACLE_SID=BBD
    ENV:
    PATH=/sapbkpbbd/upgdir/SUM/abap/exe:/oracle/BBD/112_64/bin:/usr/jdk/j2sdk1.4.2_16/bin:/usr/bin:.:/usr/sap/BBD/SYS/exe/uc/sun_64:/usr/sap/BBD/SYS/exe/run:/export/home/bbdadm:/usr/ccs/bin:/usr/ucb
    ENV: SAPDATA_HOME=/oracle/BBD
    ENV: SAPSYSTEMNAME=BBD
    ENV: dbms_type=ORA
    ENV: dbs_ora_schema=SAPSR3
    ENV: dbs_ora_tnsname=BBD
    EXECUTING /sapbkpbbd/upgdir/SUM/abap/exe/tp extrdocu BBD
    pf=/sapbkpbbd/upgdir/SUM/abap/var/DEFAULT.TPP
    if=/sapbkpbbd/upgdir/SUM/abap/tmp/MSGIN.LST
    of=/sapbkpbbd/upgdir/SUM/abap/tmp/MSGOUT.LST
    This is tp version 380.13.43 (release 741, unicode enabled)
    tp finished with return code: 8
    meaning:
    A tool used by tp produced errors
    SAPup> Process with PID 25925 terminated with status 8 at 20140515124204!
    Additionally RDDEXCEL job, which normally finishes in seconds, is running for
    more than 58000 seconds
    We didnt receive any ST22 dump in the system
    Please let me know your opinion to resolve this issue.
    I am suffering a lot , so expect reply ASAP 
    You can directly reply me through mail as well.
    Regards,
    Kisho
    Mail id: [email protected]

    Connect to the SAP system and do a "Check Status" for the job RDDEXCEL.
    If the job is running then you need to wait.

  • Error in ACTIVATE_CURRENT_USAGES phase of portal upgrade (NW04 to NW04s)

    hello gurus,
    i am upgrading Netweaver 04 to netweaver 04s (Enterprise Portal)
    oracle upgrade from 9.2.0.7 to 10.2.0.1 successfully
    but i am getting error in 78 phase out 100 in java upgrade program management
    ACTIVATE_CURRENT_USAGES
    i am unable to track the cause.......
    log file is shown below
    kindly help......
    its urgent
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[D:\usr\sap\jupgrade\log\ACTIVATE_CURRENT_USAGES_ACU_07.LOG]/>
    <!PATTERN[ACTIVATE_CURRENT_USAGES_ACU_07.LOG]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[Cp1252]/>
    <!LOGHEADER[END]/>
    #1.5#C000AC1908C2000000000029014A8CD1000432D6B5DD7008#1181797662421#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:713)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:713)#Java###Phase has been started.#1#UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES#
    #1.5#C000AC1908C200000000002A014A8CD1000432D6B5DDAE88#1181797662437#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:714)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:714)#Java###Phase type is .#1#com.sap.sdt.ucp.phases.PhaseTypeExecuteTask#
    #1.5#C000AC1908C200000000002B014A8CD1000432D6B5DDAE88#1181797662437#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:338)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:338)#Java###  Parameter =#2#inputFile#ExecuteTasks.xml#
    #1.5#C000AC1908C200000000002C014A8CD1000432D6B5DDAE88#1181797662437#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:338)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:338)#Java###  Parameter =#2#taskName#ACTIVATE_CURRENT_USAGES#
    #1.5#C000AC1908C200000000002D014A8CD1000432D6B5DDAE88#1181797662437#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.PhaseTypeExecuteTask.checkParameters(PhaseTypeExecuteTask.java:191)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.PhaseTypeExecuteTask.checkParameters(PhaseTypeExecuteTask.java:191)#Java###Phase parameters have been checked. All required phase parameters have been set.#1#2#
    #1.5#C000AC1908C200000000002E014A8CD1000432D6B5F009C0#1181797663640#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.cfg.ConfigurationBuilder.buildConfiguration(ConfigurationBuilder.java:297)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.cfg.ConfigurationBuilder.buildConfiguration(ConfigurationBuilder.java:297)#Java###Configuration has been built from input file .#1#D:/usr/sap/jupgrade/config/ExecuteTasks.xml#
    #1.5#C000AC1908C200000000002F014A8CD1000432D6B5F13A70#1181797663718#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.cfg.ConfigurationBuilder.buildConfiguration(ConfigurationBuilder.java:297)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.cfg.ConfigurationBuilder.buildConfiguration(ConfigurationBuilder.java:297)#Java###Configuration has been built from input file .#1#D:/usr/sap/jupgrade/config/ExecuteTasks_WIN.xml#
    #1.5#C000AC1908C2000000000030014A8CD1000432D6B5F13A70#1181797663718#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.cfg.ConfigurationBuilder.buildGlobalConfiguration(ConfigurationBuilder.java:251)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.cfg.ConfigurationBuilder.buildGlobalConfiguration(ConfigurationBuilder.java:251)#Java###Global configuration has been built from input file .#1#D:/usr/sap/jupgrade/config/ExecuteTasks.xml#
    #1.5#C000AC1908C2000000000031014A8CD1000432D6B5F13A70#1181797663718#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:41)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:41)#Java###Java process ID , name has been started.#2#2#com.sap.engine.offline.OfflineToolStart#
    #1.5#C000AC1908C2000000000032014A8CD1000432D6B5F178F0#1181797663734#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##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:
    j2sdk1.4.2_09
    jre
    bin
    java.exe -cp d:/usr/sap/W60/SYS/global/sltools/sharedlib/launcher.jar;d:/usr/sap/W60/SYS/global/sltools/sharedlib; com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain d:/usr/sap/W60/SYS/global/sltools/sharedlib;D:/usr/sap/W60/SYS/global/security/lib/tools;D:/usr/sap/w60/jc00/exe/classes12.jar -activated -sid=W60 -dsn=jdbc/pool/W60 -ssprops=D:/usr/sap/W60/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/W60/SYS/global/security/data/SecStore.key -log=D:
    usr
    sap
    jupgrade
    log/ACTIVATE_USAGE_AS.LOG -prod_name=NetWeaver -usage_name=AS -usage_vendor=sap.com -action=true#
    #1.5#C000AC1908C2000000000033014A8CD1000432D6B5F178F0#1181797663734#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##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:
    usr
    sap
    jupgrade
    log
    ACTIVATE_USAGE_AS_ACU_01.OUT#
    #1.5#C000AC1908C2000000000034014A8CD1000432D6B5F178F0#1181797663734#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#2#
    #1.5#C000AC1908C2000000000035014A8CD1000432D6B5F1B770#1181797663750#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#2#java.exe#
    #1.5#C000AC1908C2000000000036014A8CD1000432D6B6B9BE78#1181797676859#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#2#java.exe#64#
    #1.5#C000AC1908C2000000000037014A8CD1000432D6B6B9BE78#1181797676859#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:735)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:735)#Java###Exception has occurred during the execution of the phase.##
    #1.5#C000AC1908C2000000000038014A8CD1000432D6B6B9FCF8#1181797676875#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.execute.AbstractExtProcessOperation.generateResultProcessingException(AbstractExtProcessOperation.java:579)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.execute.AbstractExtProcessOperation.generateResultProcessingException(AbstractExtProcessOperation.java:579)#Java###Could not activate usage AS. Could not execute 'C:
    j2sdk1.4.2_09
    jre
    bin
    java.exe -cp d:/usr/sap/W60/SYS/global/sltools/sharedlib/launcher.jar;d:/usr/sap/W60/SYS/global/sltools/sharedlib; com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain d:/usr/sap/W60/SYS/global/sltools/sharedlib;D:/usr/sap/W60/SYS/global/security/lib/tools;D:/usr/sap/w60/jc00/exe/classes12.jar -activated -sid=W60 -dsn=jdbc/pool/W60 -ssprops=D:/usr/sap/W60/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/W60/SYS/global/security/data/SecStore.key -log=D:
    usr
    sap
    jupgrade
    log/ACTIVATE_USAGE_AS.LOG -prod_name=NetWeaver -usage_name=AS -usage_vendor=sap.com -action=true', return code '64'. You can check the file(s) 'D:
    usr
    sap
    jupgrade
    log/ACTIVATE_USAGE_AS_ACU.OUT', 'D:
    usr
    sap
    jupgrade
    log/ACTIVATE_USAGE_AS_ACU.ERR' to which the output of the process has been redirected.##
    #1.5#C000AC1908C2000000000039014A8CD1000432D6B6B9FCF8#1181797676875#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.execute.AbstractExtProcessOperation.execute(AbstractExtProcessOperation.java:176)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.execute.AbstractExtProcessOperation.execute(AbstractExtProcessOperation.java:176)#Java###Error while processing the result.##
    #1.5#C000AC1908C200000000003A014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.PhaseTypeExecuteTask.execute(PhaseTypeExecuteTask.java:173)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.PhaseTypeExecuteTask.execute(PhaseTypeExecuteTask.java:173)#Java###Error while executing PhaseTypeExecuteTask with input file ExecuteTasks.xml and task ACTIVATE_CURRENT_USAGES.##
    #1.5#C000AC1908C200000000003B014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:779)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:779)#Java###Phase has been completed.#1#UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES#
    #1.5#C000AC1908C200000000003C014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:780)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:780)#Java###Start time: .#1#2007/06/14 10:37:42#
    #1.5#C000AC1908C200000000003D014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:781)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:781)#Java###End time: .#1#2007/06/14 10:37:56#
    #1.5#C000AC1908C200000000003E014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:782)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:782)#Java###Duration: .#1#0:00:14.453#
    #1.5#C000AC1908C200000000003F014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:783)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:783)#Java###Phase status is .#1#error#
    waiting for solution
    thankx in advance....
    shoeb

    Could you please share us the solution?

  • PI7.1 EHP1 Java suppor packages LM-CORE Deployment ERROR

    Hi,
    I have installed PI7.1 EHP1 on Linux X86_64 /oracle 11.
    Successfully Updated the ABAP Stack support packages to 7.11 SPS07 thru
    SPAM, but During Java stack thru JSPM i have encountered follwoing
    error for LS-CORE
    7.11.7.3.
    Error: 1. Item is skipped because of failed deployment of the item
    sap.com_tclmwebadminflexstateview and because the applied error
    strategy is oneErrorstop 1. Contains Aborted Deployment Component
    sap.com_tclmwebadminflexstateview .
    LOG::
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[2.0.7.1006]/>
    <!NAME[/usr/sap/JXD/DVEBMGS00/j2ee/JSPM/log/log_2011_09_22_20_20_06/deploy_2011-09-22_20-56-07.log]/>
    <!PATTERN[deploy_2011-09-22_20-56-07.log]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%25d[%6s]:%m)]/>
    <!ENCODING[UTF8]/>
    <!LOGHEADER[END]/>
    Sep 22, 2011 8:56:07 PM  [Info  ]:DC API is trying to connect to 'SJXD0001:50004'
    Sep 22, 2011 8:56:07 PM  [Info  ]:DC API has Connected to 'SJXD0001:50004'
    Sep 22, 2011 8:56:07 PM  [Info  ]:+++++ Starting  D E P L O Y action +++++ [ deployerId=5 ] [ timerId=177]
    Sep 22, 2011 8:56:07 PM  [Info  ]:Selected archives for deployment. [ deployerId=5 ]
    Sep 22, 2011 8:56:07 PM  [Info  ]:/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA
    Sep 22, 2011 8:56:07 PM  [Info  ]:DC API got Session id='161',time:[id:#177, elapsed: 23 ms.].[ deployerId=5 ]
    Sep 22, 2011 8:56:07 PM  [Info  ]:component version handling rule is UpdateLowerOrChangedVersionsOnly.[ deployerId=5 ]
    Sep 22, 2011 8:56:07 PM  [Info  ]:deployment workflow strategy is safety deploy strategy.[ deployerId=5 ]
    Sep 22, 2011 8:56:07 PM  [Info  ]:life cycle deploy strategy is disable LCM deploy strategy.[ deployerId=5 ]
    Sep 22, 2011 8:56:07 PM  [Info  ]:Error strategies[ deployerId=5 ]:
    Sep 22, 2011 8:56:07 PM  [Info  ]:error action 'DeploymentAction' is 'OnErrorStop'
    Sep 22, 2011 8:56:07 PM  [Info  ]:error action 'PrerequisitesCheckAction' is 'OnErrorStop'
    Sep 22, 2011 8:56:09 PM  [Info  ]:clusterRestartTriggered for transactionId:161, clusterEventAction:cluster restart triggered
    Sep 22, 2011 8:56:09 PM  [Info  ]:Caught exception [P4ConnectionException]. Because cluster restart has been triggered beforehand, assuming a cluster restart.
    Sep 22, 2011 8:56:09 PM  [Info  ]:+++ Server is being restarted +++. The currently set engine start timeout is: 7200 seconds.
    Sep 22, 2011 8:56:09 PM  [Info  ]:+++ Wait for server response +++. Elapsed: 0 seconds. Remainig to timeout 7200 seconds.
    Sep 22, 2011 8:56:25 PM  [Info  ]:+++ Wait for server response +++. Elapsed: 16 seconds. Remainig to timeout 7183 seconds.
    Sep 22, 2011 8:56:41 PM  [Info  ]:+++ Wait for server response +++. Elapsed: 32 seconds. Remainig to timeout 7167 seconds.
    Sep 22, 2011 8:56:57 PM  [Info  ]:+++ Wait for server response +++. Elapsed: 48 seconds. Remainig to timeout 7151 seconds.
    Sep 22, 2011 8:57:13 PM  [Info  ]:+++ Wait for server response +++. Elapsed: 64 seconds. Remainig to timeout 7135 seconds.
    Sep 22, 2011 8:57:26 PM  [Info  ]:Wait for the operation 'Deploying' to finish
    Sep 22, 2011 8:57:28 PM  [Info  ]:Assuming a subsequent restart of the server due to exception: [P4ConnectionException], message: Error. Check your available working servers. Error message: the requested server is not available
    Sep 22, 2011 8:57:28 PM  [Error ]:[ Exception ]::Unexpected exception during the notification of cluster listeners
    Sep 22, 2011 8:57:28 PM  [Info  ]:+++ Wait for server response +++. Elapsed: 0 seconds. Remainig to timeout 7200 seconds.
    Sep 22, 2011 8:57:45 PM  [Info  ]:+++ Wait for server response +++. Elapsed: 16 seconds. Remainig to timeout 7183 seconds.
    Sep 22, 2011 8:58:01 PM  [Info  ]:+++ Wait for server response +++. Elapsed: 32 seconds. Remainig to timeout 7167 seconds.
    Sep 22, 2011 8:58:18 PM  [Info  ]:+++ Wait for server response +++. Elapsed: 49 seconds. Remainig to timeout 7150 seconds.
    Sep 22, 2011 8:58:36 PM  [Info  ]:Obtaining the deployment result from the server ...
    Sep 22, 2011 8:58:37 PM  [Info  ]:Deployment result
    Sorted Items -
         1. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtcsld~data.sda'
              Deploy status is 'Skipped'
              SDA : name 'tcslddata', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823093938.0000', software type ('FS', sub type ''), csn component 'BC-CCM-SLD', dependencies :[none]
         2. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmwebadminflexjavastatistics.sda'
              Deploy status is 'Skipped'
              SDA : name 'tclmwebadminflexjavastatistics', vendor 'sap.com', location 'SAP AG', version '7.1107.20110309083123.0000', software type ('FS', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[none]
         3. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmctcutilinfra_lib.sda'
              Deploy status is 'Skipped'
              SDA : name 'tclmctcutilinfra_lib', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823083938.0000', software type ('library', sub type ''), csn component 'BC-INS-CTC', dependencies :[none]
         4. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.com~sl.ut.infoprovider.sda'
              Deploy status is 'Skipped'
              SDA : name 'sl.ut.infoprovider', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826143016.0000', software type ('library', sub type ''), csn component 'BC-INS-JCI', dependencies :[( name 'com.sap.exception', vendor 'sap.com') , ( name 'com.sap.tc.Logging', vendor 'sap.com') ]
         5. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.sl.ut.info.sda'
              Deploy status is 'Skipped'
              SDA : name 'com.sap.sl.ut.info', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826143016.0000', software type ('J2EE', sub type ''), csn component 'BC-INS-JCI', dependencies :[( name 'com.sap.exception', vendor 'sap.com') , ( name 'com.sap.tc.Logging', vendor 'sap.com') , ( name 'sl.ut.infoprovider', vendor 'sap.com') ]
         6. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcsldabapapi_ear.sda'
              Deploy status is 'Skipped'
              SDA : name 'tcsldabapapi_ear', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823093938.0000', software type ('J2EE', sub type ''), csn component 'BC-CCM-SLD', dependencies :[( name 'com.sap.mw.jco', vendor 'sap.com') , ( name 'tcsldsldclient_sda', vendor 'sap.com') ]
         7. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcjebasicadminsapcontrolapp.sda'
              Deploy status is 'Skipped'
              SDA : name 'tcjebasicadminsapcontrolapp', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826165427.0000', software type ('J2EE', sub type ''), csn component 'BC-JAS-ADM-ADM', dependencies :[( name 'tcjmx', vendor 'sap.com') , ( name 'adminadapter', vendor 'sap.com') , ( name 'tcjebasicadminsapcontrol~lib', vendor 'sap.com') ]
         8. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.com~com.sap.engine.customizing.ccms.sda'
              Deploy status is 'Skipped'
              SDA : name 'com.sap.engine.customizing.ccms', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826155427.0000', software type ('J2EE', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[( name 'com.sap.mw.jco', vendor 'sap.com') , ( name 'monitor', vendor 'sap.com') , ( name 'tcjmx', vendor 'sap.com') , ( name 'rfcengine', vendor 'sap.com') , ( name 'tcmonitoring~api', vendor 'sap.com') , ( name 'monitortree', vendor 'sap.com') ]
         9. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmwebadminflexflexcommons.sda'
              Deploy status is 'Skipped'
              SDA : name 'tclmwebadminflexflex_commons', vendor 'sap.com', location 'SAP AG', version '7.1107.20110309083123.0000', software type ('FS', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[none]
         10. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmwebadminflexstateview.sda'
              Deploy status is 'Aborted'
              SDA : name 'tclmwebadminflexstateview', vendor 'sap.com', location 'SAP AG', version '7.1107.20110309083123.0000', software type ('FS', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[none]
         11. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtcrprof~rprof_tbl.sda'
              Deploy status is 'Skipped'
              SDA : name 'tcrprofrprof_tbl', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823093938.0000', software type ('JDDSCHEMA', sub type ''), csn component 'BC-CCM-SLD', dependencies :[none]
         12. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcjecontextcollectorwsproxyapp.sda'
              Deploy status is 'Skipped'
              SDA : name 'tcjecontextcollectorwsproxyapp', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826165427.0000', software type ('J2EE', sub type ''), csn component 'BC-NWA-EMB', dependencies :[( name 'tcjeembeddedsupportlib', vendor 'sap.com') , ( name 'contextcollector', vendor 'sap.com') ]
         13. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.com~sl.ut.dbcontent.sda'
              Deploy status is 'Skipped'
              SDA : name 'com.sap.sl.ut.jddi.content', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826143016.0000', software type ('DBSC', sub type ''), csn component 'BC-INS-JCI', dependencies :[( name 'com.sap.sl.ut.jddi.schema', vendor 'sap.com') ]
         14. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA'
              Deploy status is 'Aborted'
              SCA : name 'LM-CORE', vendor 'sap.com', location 'SAP AG', version '1000.7.11.7.3.20110829165900'
    Deployment Items -
         1. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA'
              Deploy status is 'Aborted'
              Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop
              1. Contains Aborted deployment component:
    sap.com_tclmwebadminflexstateview'.
              SCA : name 'LM-CORE', vendor 'sap.com', location 'SAP AG', version '1000.7.11.7.3.20110829165900'
              Composite Time statistics( ms ):
                   1.Check composite version : 24
                        1.1.Check version:sap.com_LM-CORE : 1
                        1.2.Check contained SDAs versions : 23
                   2.validate : 31
                        2.1.Check composite version : 31
                             2.1.1.Check contained SDAs versions : 31
                   3.Persist in storage : 11
              Contained DCs:
                   1.1 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcsldcds~wsproxy_ear.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110823093938.0000
              2. Already deployed component has version:7.1107.20110823093938.0000'.
                        SDA : name 'tcsldcds~wsproxy_ear', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.2 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.lcr.namealloc.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110711084722.0000
              2. Already deployed component has version:7.1107.20110711084722.0000'.
                        SDA : name 'com.sap.lcr.namealloc', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.3 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmctc~interface_lib.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110823083938.0000
              2. Already deployed component has version:7.1107.20110823083938.0000'.
                        SDA : name 'tclmctc~interface_lib', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.4 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtcslddpj2ee.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110823093938.0000
              2. Already deployed component has version:7.1107.20110823093938.0000'.
                        SDA : name 'tcslddp~j2ee', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.5 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.util.monitor.grmg.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110309073123.0000
              2. Already deployed component has version:7.1107.20110309073123.0000'.
                        SDA : name 'com.sap.util.monitor.grmg', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.6 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> apptracing.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110826165427.0000
              2. Already deployed component has version:7.1107.20110826165427.0000'.
                        SDA : name 'apptracing', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23

    versions : 31
                             3.Persist in storage : 11
                   1.22 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcsldcds~cdsclient_lib.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110823093938.0000
              2. Already deployed component has version:7.1107.20110823093938.0000'.
                        SDA : name 'tcsldcds~cdsclient_lib', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.23 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.com~sl.ut.infoprovider.sda'
                        Deploy status is 'Skipped'
                        Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
                        SDA : name 'sl.ut.infoprovider', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826143016.0000', software type ('library', sub type ''), csn component 'BC-INS-JCI', dependencies :[( name 'com.sap.exception', vendor 'sap.com') , ( name 'com.sap.tc.Logging', vendor 'sap.com') ]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.24 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcsldcds~wsproxy_lib.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110823093938.0000
              2. Already deployed component has version:7.1107.20110823093938.0000'.
                        SDA : name 'tcsldcds~wsproxy_lib', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.25 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> monitortree.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110826155427.0000
              2. Already deployed component has version:7.1107.20110826155427.0000'.
                        SDA : name 'monitortree', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.26 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.lcr.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110823093938.0000
              2. Already deployed component has version:7.1107.20110823093938.0000'.
                        SDA : name 'com.sap.lcr', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.27 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtcrprof~rprof_tbl.sda'
                        Deploy status is 'Skipped'
                        Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
                        SDA : name 'tcrprofrprof_tbl', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823093938.0000', software type ('JDDSCHEMA', sub type ''), csn component 'BC-CCM-SLD', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.28 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtcmonitoring~sda.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110826155427.0000
              2. Already deployed component has version:7.1107.20110826155427.0000'.
                        SDA : name 'tcmonitoringsda', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.29 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmctcutilinfra_lib.sda'
                        Deploy status is 'Skipped'
                        Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
                        SDA : name 'tclmctcutilinfra_lib', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823083938.0000', software type ('library', sub type ''), csn component 'BC-INS-CTC', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.30 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmwebadminflexstateview.sda'
                        Deploy status is 'Aborted'
                        Description:'1. CFS Container reported an error. Check the causing exceptions for the reason for failure.
               -> [ERROR CODE DPL.CFS.0301] Error while notifying bootstrap about component "sap.com/tclmwebadminflexstateview". Collected error messages are: Collected bootstrap error messages ( appName:sap.com/tclmwebadminflexstateview) :
         /usr/sap/JXD/DVEBMGS00/exe/servicehttp/ctsv/AC_OETags.js (No such file or directory)
         /usr/sap/JXD/DVEBMGS00/exe/servicehttp/ctsv/ComponentStateView.html (No such file or directory)
         /usr/sap/JXD/DVEBMGS00/exe/servicehttp/ctsv/ComponentStateView.swf (No such file or directory)
         /usr/sap/JXD/DVEBMGS00/exe/servicehttp/ctsv/playerProductInstall.swf (No such file or directory)
                        SDA : name 'tclmwebadminflexstateview', vendor 'sap.com', location 'SAP AG', version '7.1107.20110309083123.0000', software type ('FS', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.31 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcsldabapapi_ear.sda'
                        Deploy status is 'Skipped'
                        Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
                        SDA : name 'tcsldabapapi_ear', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823093938.0000', software type ('J2EE', sub type ''), csn component 'BC-CCM-SLD', dependencies :[( name 'com.sap.mw.jco', vendor 'sap.com') , ( name 'tcsldsldclient_sda', vendor 'sap.com') ]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.32 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.sl.ut.info.sda'
                        Deploy status is 'Skipped'
                        Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
                        SDA : name 'com.sap.sl.ut.info', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826143016.0000', software type ('J2EE', sub type ''), csn component 'BC-INS-JCI', dependencies :[( name 'com.sap.exception', vendor 'sap.com') , ( name 'com.sap.tc.Logging', vendor 'sap.com') , ( name 'sl.ut.infoprovider', vendor 'sap.com') ]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.33 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.engine.heartbeat.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110826155427.0000
              2. Already deployed component has version:7.1107.20110826155427.0000'.
                        SDA : name 'com.sap.engine.heartbeat', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.34 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> dsr.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110826165427.0000
              2. Already deployed component has version:7.1107.20110826165427.0000'.
                        SDA : name 'dsr', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.35 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtclmctccul~service_sda.sda'
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:7.1107.20110815124828.0000
              2. Already deployed component has version:7.1107.20110815124828.0000'.
                        SDA : name 'tclmctcculservice_sda', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.36 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcjecontextcollectorwsproxyapp.sda'
                        Deploy status is 'Skipped'
                        Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
                        SDA : name 'tcjecontextcollectorwsproxyapp', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826165427.0000', software type ('J2EE', sub type ''), csn component 'BC-NWA-EMB', dependencies :[( name 'tcjeembeddedsupportlib', vendor 'sap.com') , ( name 'contextcollector', vendor 'sap.com') ]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
                   1.37 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmwebadminflexjavastatistics.sda'
                        Deploy status is 'Skipped'
                        Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
                        SDA : name 'tclmwebadminflexjavastatistics', vendor 'sap.com', location 'SAP AG', version '7.1107.20110309083123.0000', software type ('FS', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[none]
                        Time statistics( ms ):
                             1.Check composite version : 24
                                  1.1.Check version:sap.com_LM-CORE : 1
                                  1.2.Check contained SDAs versions : 23
                             2.validate : 31
                                  2.1.Check composite version : 31
                                       2.1.1.Check contained SDAs versions : 31
                             3.Persist in storage : 11
    Sep 22, 2011 8:58:37 PM  [Info  ]:+++ Deployment finished with status 'Error' +++.[ deployerId=5 ][#178: 149.398 sec]
    Sep 22, 2011 8:58:37 PM  [Info  ]:+++++ End  D E P L O Y action +++++[ deployerId=5 ]. Total time:[#177: 149.501 sec]

  • START_J2EE_INITIAL phase error

    hi,
    i'm trying to upgrade dual stack system and i've got an error during the execution of the START_J2EE_INITIAL phase.
    this is trouble ticket info:
    Trouble Ticket Report
    Upgrade to SAP NetWeaver'04s SR3
    SID................: DWD
    Hostname...........: fsczpga01519
    Install directory..: /usr/sap/DWD
    Upgrade directory..: /usr/sap/jupgrade
    Database...........: Oracle
    Operating System...: UNIX
    JDK version........: 1.4.2 IBM Corporation
    SAPJup version.....: 1.3.16
    Source release.....: 630
    Target release.....: 700
    Current usages.....: AS;AAS
    ABAP stack present.: true
    The execution of UPGRADE/UPGRADE/START_J2EE_INITIAL ended in error.
    Could not start J2EE Engine instance with name J2EE and number 10 of the standard system.
    Could not start instance 10.
    More information can be found in the log file /usr/sap/jupgrade/log/START_J2EE_INITIAL_TJI_03.LOG.
    Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Se
    arch for OSS notes with the following search terms:
    com.sap.sdt.j2ee.phases.PhaseTypeControlEngine
    com.sap.sdt.ucp.phases.PhaseException
    Could not start J2EE Engine instance with name J2EE and number 10 of the standard system.
    START_J2EE_INITIAL_TJI_03.LOG is saying this:
    #1.5#C0000A2ABA08000000000CEF62E2B88B000480E7B2CA7CD0#1267632532258#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/START_J2EE_INITIAL##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:834)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:834)#Java###Phase status is .#1#error#
    and there is an error in std_server0.out:
    Loading: ConfigurationManager returned false!
    Kernel not loaded. System halted.
    any help appreciated.
    thanks,
    martin

    Hello Martin,
    The defaultTrace of server0 might provide you with more information about the error.
    The Kernel of the J2EE Engine is made by mostly libraries and therefore when it doesnu2019t start usually a bad deployment is the cause. Therefore if the information in the defaultTrace doesnu2019t help you to find the solution you could try to re-deploy with SDM the following SDA file that contains the J2EE Kernel:
    SAPJEECOR[SP_Version].SCA. Select the option u201CUpdate SDAu2019s/SCAu2019s that have any versionu201D in the SDM GUI. Refer to the SDM documentation at SDM/program/doc for more information about SDM.
    Regards,
    Ventsi Tsachev
    Technology Development Support (J2EE Engine)
    SAP Labs, Palo Alto, Ca (USA)

  • EHP1 upgrade error in PREP_INPUT..phase

    Hello,
    I am doing EHP1 upgrade and getting error in EHPI during the PREP_INPUT/KX_CPYORG! phase.
    Below is the error:
    Severe error(s) occured in phase PREP_INPUT/KX_CPYORG!
    Last error code set: Cannot open '/usr/sap/<SID>/SYS/exe/run/dbatoolsora.lst': No such file or directory
    It complains about dabtoolsora.lst file not existing in /SYS/exe/run Dir. This is because our DB is in separate machine/host and the CI is in separate. Hence the file mentioned above only exist in */SYS/exe/run Dir of DB host.
    Can anyone please suggest what steps should be taken to resolve this issue? Do i need to copy that file manually to the CI host's */SYS/exe/run Directory and then repeat the EHPI steps again?
    Any help would be greatly appreciated. Thanks.

    I know this answer is too late for your question, but it's still the top google hit for this message, so I'm leaving this here for others.
    SUM still has this behavior as of 1.0 SP6.  One workaround is to copy dbatoolsora.lst from your DB server kernel directory, and create wrapper scripts which will SSH from the CI to the DB and run the brtools commands that SUM would want to run.
    Here's an example of such a script, for brtools:
    #!/bin/csh
    ssh $SAPDBHOST brtools $*
    So, you'd have a script like this for brarchive, brbackup, and the other br* tools mentioned in dbatoolsora.lst, each containing the name of the command to run on the db server.
    Be sure to look in dbatoolsora.lst for a list of other files it may expect to find.

  • Error in preprocessing phase

    Hi All ,
    We are facing error in preprocessing phase of upgrade to EHP 7 ,Let me know if anyone can help us in this critical situation
    System details:Oracle 11gr2,Linux x86-64 ,
    Below is the error :
    During the phase MAIN_SHDIMP/SUBMOD_SHD2_RUN/RFCDEST_CREATE_S2OX in
    Pre-processing of the SUM we are facing below error.
    1 ETQ233 Calling function module "FUNCTION_EXISTS" by RFC
    2 ETQ373 parameter "FUNCNAME" = "RFC_DESTINATION_CREATE"
    1 ETQ234 Call of function module "FUNCTION_EXISTS" by RFC succeeded
    4 ETQ010 Date & Time: 20140912043336
    1 ETQ359 RFC Login to: System="XXX", AsHost="sapXXXpas" Nr="12",
    GwHost="sapa10pas", GwService="sapgwZZ"
    2 ETQ232 RFC Login succeeded
    4 ETQ010 Date & Time: 20140912043336
    1 ETQ233 Calling function module "RFC_DESTINATION_CREATE" by RFC
    2 ETQ373 parameter "DESTINATION_NAME" = "SAP_UPGRADE_ORIG_SYSTEM"
    2 ETQ373 parameter "USER" = "DDIC"
    2 ETQ373 parameter "HOST" = "sapXXXpas"
    2 ETQ373 parameter "SYSTEMNR" = "11"
    2 ETQ373 parameter "CHECK" = "X"
    1EETQ235 Call of function module "RFC_DESTINATION_CREATE" by RFC failed
    (error-status "3")
    2EETQ360 RFC of "RFC_DESTINATION_CREATE" failed:
    2EETQ361 code/exception : 3
    2EETQ362 key : CALL_FUNCTION_NO_DEST
    2EETQ399 RFC destination SAP_UPGRADE_ORIG_SYSTEM does not exist.
    Regards
    Bharat
    Mob No: 91 9008804153

    Hi Reagan ,
    The issue was taken to SAP development security team :::Below is the  weird issue ::
    Firstly ,for the authorizations to work correctly, all authorization tables must be in a consistent state as below :
    ust04, ust10c, ust10s, ust12, usrbf2, usrbf3.
    If we  want to maintain authorizations, also usr04, usr10, usr12 are  required.
    But here , a mismatch of tables usrbf2 and usrbf3  in 2 instances are the reason for the stuck in the upgrade :::
    SQL> select count(*) from sapsr3.USRBF2 where MANDT = '000' and BNAME =
    'DDIC';
    COUNT(*)
    2997
    SQL> select count(*) from sapsr3.USRBF3 where MANDT = '000' and BNAME =
    'DDIC';
    COUNT(*)
    1
    SQL>
    SQL> select count(*) from sapsr3shd.USRBF2 where MANDT = '000' and
    BNAME =
    'DDIC';
    COUNT(*)
    673
    SQL> select count(*) from sapsr3shd.USRBF3 where MANDT = '000' and
    BNAME =
    'DDIC';
    COUNT(*)
    1
    This issue was resolved by SAP and then upgrade went fine ,This is not an issue with password of DDIC !!!!!
    Regards
    Ram

  • Support Pack upgrade error in Import Phase

    Hello,
    Currently I am upgrading SCM system with Support pack level 12 to 20 . When i am applying Basis 12 to 20. I got an error in Import_Proper phase.
    Could you please help me on this? I tried and still searching solution for this..But no luck...
    Os is : AIX and
    Log File:                /usr/sap/trans/log/SAPIB70013.xxx
    Main import
    Transport request   : SAPKB70013
    System              : xxxx
    tp path             : tp
    Version and release: 372.04.71 700
    child process 934006 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_report_interface
    fcode:      CLOSE_LINE_MODE
    tabname:    SOURCE
    len (char): 40
    key:        CL_OBJECT_COLLECTION==========CT
    retcode:    1
    SQL error -913 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
    child process 1212554 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_report_interface
    fcode:      CLOSE_LINE_MODE
    tabname:    SOURCE
    len (char): 40
    key:        CL_WDR_APPLICATION_WINDOW=====CT
    retcode:    1
    SQL error -913 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
    child process 1171520 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_report_interface
    fcode:      CLOSE_LINE_MODE
    tabname:    SOURCE
    len (char): 40
    key:        CL_WDY_MD_EVENT_SOURCE========CI
    retcode:    1
    SQL error -913 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
    child process 1331412 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_xrtab
    fcode:      RT_MI_LOAD
    tabname:    ECSCR_DATA
    len (char): 106
    key:        EC_TEST_DATA                  00000000P10                           IECATTDEFAULT
    retcode:    1
    SQL error -904 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
    insert / update sequence failed due to an error in DBI.
    maybe there's a concurrent process which inserted this table entry at the same time.
    insert / update sequence failed due to an error in DBI.                       
    maybe there's a concurrent process which inserted this table entry at the same time.
    child process 1310922 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_xrtab
    fcode:      RT_MI_END
    tabname:    WDY_APP_PROPERTY
    len (char): 64
    key:        DEMO_UIEL_DROPDOWN_BY_IDX     DEMO_VIEW
    retcode:    1
    SQL error -904 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
    import portion 018446 - 999999 not imported because the child processes died for unknown reason
    child process 1310924 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_report_interface
    fcode:      CLOSE_LINE_MODE
    tabname:    SOURCE
    len (char): 40
    key:        CL_WDY_MD_OUTGOING_EVENT======CT
    retcode:    1
    SQL error -913 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
    child process 1286192 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_xrtab
    fcode:      RT_MI_LOAD
    tabname:    ECSCR_DATA
    len (char): 106
    key:        EC_TEST_DATA                  00000000P10                           IECATTDEFAULT
    retcode:    1
    SQL error -904 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
    import portion 009158 - 018411 not imported because the child processes died for unknown reason
    import portion 018412 - 018527 not imported because the child processes died for unknown reason
    import portion 018528 - 999999 not imported because the child processes died for unknown reason
    sap_dext called with msgnr 1:
    db call info -
    function:   db_xrtab
    fcode:      RT_MI_LOAD
    tabname:    ECSCR_DATA
    len (char): 106
    key:        EC_TEST_DATA                  00000000P10                           IECATTDEFAULT
    retcode:    1
    SQL error -904 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
    Main import
    End date and time : 20100909034914
    Ended with return code:  ===> 12 <===
         |   ######################################                     
    Thanks and Regards,
    Sankar
    SAP BASIS Consultant

    Hi,
    Thanks for you reply. I restarted import but no luck still. I activated some object also not working. when i call SPAM it is not going to the SPAM pager. Showing dump...
    Runtime Errors         CALL_FUNCTION_NOT_FOUND
    Except.                CX_SY_DYN_CALL_ILLEGAL_FUNC
    Date and Time          10.09.2010 09:41:37
    Short text
         Function module "POSS_UIREQ_OPT_SUBMIT" not found.
    What happened?
         The function module "POSS_UIREQ_OPT_SUBMIT" is called,
         but cannot be found in the library.
         Error in the ABAP Application Program
         The current ABAP program "SAPLSTXC" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
          not caught in
         procedure "OPEN_FORM" "(FUNCTION)", nor was it propagated by a RAISING clause.
         Since the caller of the procedure could not have anticipated that the
         exception would occur, the current program is terminated.
         The reason for the exception is:
         The program "SAPLSTXC" contains the CALL FUNCTION statement.
         The name of the function module to be called is "POSS_UIREQ_OPT_SUBMIT".
         No function module exists with the name "POSS_UIREQ_OPT_SUBMIT".
         All function modules are listed in the Function Library (SE37).
    Possible reasons:
    a) Wrong name specified. Pay particular attenti
        upper/lower case and underscores ("_").
        or
    b) Transport error
    c) In the case of an enqueue/dequeue module,
        the lock object may not have been activated
        (ABAP/4 Dictionary).
    When i tried to check function module it is not there..
    Could you please help on this?
    Regards,
    Sankar Basis Consultant

  • What is the difference between SAP NW PI7.1 and PI7.1 EHP1

    We have a customer using SAP PI7.1 EHP1. The application to be deployed
    isdeveloped on SAP Netweaver PI 7.1 SP06.
    We need to know if application developed and transported from PI7.1 is
    compatible with EHP1?
    Below are the Components used by the application .
    1) SSL communication using SOAP adapter
    2) Java mapping , Graphical mapping , XSLT mapping
    3) Customised EJB modules
    4) Adapter framework
    5) ALE layer for IDoc communication from ERP to PI
    6) RFC lookups to PI system and ERP system.
    Questions
    1)Will PI EHP1 be able to communicate with PI7.1 using SOAP adapter ?
    2) What is the difference between SAP NW PI7.1 and PI7.1 EHP1 ?
    Regards,
    Sneha

    Hi,
    EHP Pi7.1 new
    IPv6 Support in SAP Systems (new)
    Async/Sync and Sync/Async Bridge in the JMS Adapter (New)
    High Availability (New)   Locate the document in its SAP Library structure
    Use
    A new concept is available for setting up a high availability environment for SAP NetWeaver Process Integration (PI). To do this, you need SAP Web Dispatcher for load balancing, and you must reconfigure your HTTP, RFC, and RMI connections so that they can be used for load balancing. You must also make various configuration steps in other components of your PI environment.
    [Level 4: Document: XML to Text Conversion Module (New)] XML to Text Conversion Module (New)
    Message Packaging (New)
    Monitoring Milestones (New)   Locate the document in its SAP Library structure
    Use
    You can use the new scenario variant Monitoring Milestones of the Business Process Management scenario to define a monitoring process that can monitor events from different applications. A monitoring process can subscribe to events from SAP or non-SAP systems.
    check  given Link
    http://help.sap.com/saphelp_nwpi711/helpdata/en/61/8c3842bb58f83ae10000000a1550b0/frameset.htm
    Regards,
    Amit

  • PI 7.1 upgrade error in GETSYNC_PROFILES_CHANGED phase

    Hello
    Currently I am upgrading an XI 7.0 system to PI 7.1. The downtime phases have just started and I've hit an error in the phase 'GETSYNC_PROFILES_CHANGED'; the error is 'Not enough space for string replacement'. Based on the phase name, and the previous phases, it looks as if the error is something to do with the profiles. The relevant upgrade logs have no useful info in them except for the string space message.
    I have done the usual SDN, SAP Marketplace and Google searches but could not find an answer to my problem. I have also opened a high priority call with SAP but they have not come up with an answer yet. Does anybody have any useful advice?
    The system being upgraded is running on Windows 2003 Server R2 64bit, has an Oracle 10.2.0.4 DB, and the source system was XI/PI 7.0 SP15.
    Thanks.

    Hello Rohit
    Freespace is more than sufficient:
    C:\ = 5.2GB (O/S)
    D:\ = 18.9GB (Oracle & SAP)
    E:\ = 8.53GB (Oracle)
    Andrew
    Edited by: Andrew Turvey on May 28, 2009 3:48 PM

  • Error in ABAP_Import Phase

    Dear Guru's,
    We are facing some issue on ABAP Import phase, out of 29 Import Monior jobs 2 jobs gets failed.
    Error in Import_ABAP Phase, 2 jobs failed
    Loading of 'DD03L' import package: ERROR
    Loading of 'SACONT01' import package: ERROR
    could anyone suggest me, what could be done to resolve this issue.
    regards,
    Guna

    Hi,
    Thanks for your information.
    We tried with retry option, still in same position.
    We're doing solution manager 7.0 installation on AIX 5.
    (DB) INFO: SACONT01 deleted/truncated #20100429153529
    (DB6) Using LOAD API for table SACONT01
    (RFF) ERROR: invalid checksum in data file "/hm/cdmedia/solman7.0/51033518_Expor
    t2/EXP3/DATA/SACONT01.001"
                 current table was "SACONT01"
    (DB) INFO: disconnected from DB
    /usr/sap/SM1/SYS/exe/run/R3load: job finished with 1 error(s)
    /usr/sap/SM1/SYS/exe/run/R3load: END OF LOG: 20100429153530
    Suggestions appreciated.
    regards,
    Guna

  • Error in DEPLOY_ONLINE_DEPL phase EHPI 7.01 SPS05 DualStack ABAP+JAVA

    Hello experts,
    I'm getting an error in DEPLOY_ONLINE_DEPL phase (Downtime Roadmap) under J2EE tab in enhancement package installation in our BW System (Netweaver 7.0 SP 17 to NW 7.01 SPS 05 DualStack ABAP+JAVA)
    The system is running on High Availability server.
    Restarting Q2B 00 instance failed.
    Cannot find instance with instance number 0 on host mcho35au in the cluster.
    I'm not sure, but maybe anything is wrong with my profiles...? I don't know....
    All J2EE deployments has been successfully finished (JSPM).
    I have restarted all instances DVEBMGS00 & SCS01 and Shadow Instance DVEBMGS02. SCS01 Instance is up and running as well.
    Then I have stop EHPI Upgrade and start it again.
    DEPLOY_ONLINE_DEPL_DDB_18.LOG:
    ==========================================
    RequestController.java:178)[Thread[main,5,main]]: Deployment of queue sapjup-queue completedwith error Cannot check the state(running/stoped) of the CI.
    Restarting Q2B 00 Instance failed
    Connot find instance with instance number 0 on host mcho35au in the cluster
    ==========================================
    An error has occurred during the execution of the DEPLOY_ONLINE_DEPL phase.
    Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action. Could not execute deployment of stack file /usr/sap/trans/EPS/in/SMSDXML_CROSSSYS_20091109075202.238.xml. The deployment of the queue failed. Deployment of queue sapjup-queue completed with error Cannot check the state(running/stoped) of the CI. Restarting Q2B 00 instance failed. Cannot find instance with instance number 0 on host mcho35au in the cluster. JSPM version is 7.01.5.0.20. Current JSPM log directory is /usr/sap/Q2B/DVEBMGS00/j2ee/JSPM/log/log_2009_11_14_18_20_03.
    You can find more information in the log file /usr/sap/swdc/EHPI/java/log/DEPLOY_ONLINE_DEPL_DDB_19.LOG.
    ==========================================
    Any ideas ?
    Please help me in this case.
    I'm wating for any feedbacks.
    Thanks a lot in advance !
    Gerd
    Edited by: Gerd Schuster on Nov 14, 2009 6:23 PM

    Problem:
    The DEPLOY_ONLINE_DEPL phase (Downtime Roadmap) under J2EE tab in enhancement package installation in BW System (Netweaver 7.0 SP 17 to NW 7.01 SPS 05 DualStack ABAP+JAVA, system is running on High Availability server) stopped with error:
    RequestController.java:178)[Threadmain,5,main]: Deployment of queue sapjup-queue
    completedwith error Cannot check the state(running/stoped) of the CI.
    Restarting Q2B 00 Instance failed
    Connot find instance with instance number 0 on host mcho35au in the cluster
    An error has occurred during the execution of the DEPLOY_ONLINE_DEPL phase.
    Error while executing DeploymentManager phase with action deploySlot. Check the log files for
    the specified action. Could not execute deployment of stack
    file /usr/sap/trans/EPS/in/SMSDXML_CROSSSYS_20091109075202.238.xml. The deployment
    of the queue failed. Deployment of queue sapjup-queue completed with error Cannot check the
    state(running/stoped) of the CI. Restarting Q2B 00 instance failed. Cannot find instance with instance
    number 0 on host mcho35au in the cluster. JSPM version is 7.01.5.0.20. Current JSPM log directory
    is /usr/sap/Q2B/DVEBMGS00/j2ee/JSPM/log/log_2009_11_14_18_20_03.
    You can find more information in the log file /usr/sap/swdc/EHPI/java/log/DEPLOY_ONLINE_DEPL_DDB_19.LOG.
    Solution:
    stop all instances (shadow instance, SCSxx)
    In a High Availability server you have to modify few parameters in DEFAULT profile temporarily (replace alias-servername with real hostname):
    DEFAULT.PFL: SAPLOCALHOST = mcho35au
    DEFAULT.PFL: SAPDBHOST = mcho35au
    DEFAULT.PFL: rdisp/mshost = mcho35au
    # DEFAULT.PFL: rdisp/vbname = mcho35au_Q2B_00  (<- maby it'snot relevant)
    # DEFAULT.PFL: rdisp/enqname = mcho35au_Q2B_00  (<- maby it'snot relevant)
    # DEFAULT.PFL: rdisp/btcname = mcho35au_Q2B_00  (<- maby it'snot relevant)
    DEFAULT.PFL: rdisp/sna_gateway = mcho35au
    in instance DVEBMGS00 switch profile icman = 0 to 1 (otherwise J2EE instance will not started)
    startsap DVEBMGS00
    Restart EHPI Upgrade (EHPI keep the old DEFAULT.PFL settings in shared memory!)
    ./EHPI/STARTUP jce_policy_zip=90000125.zip
    Repeat phase DEPLOY_ONLINE_DEPL
    Gerd
    Edited by: Gerd Schuster on Nov 16, 2009 2:59 PM

  • Error in XPRA_EXECUTION phase in instalation BI_CONT 3.53

    Hello,
    After installing SAP Netweaver 04 as ABAP i am Installing Add-on
    BI_CONT Rel.353 : Import of the queue -
    via SAINT Tcode.
    Now it is in error in XPRA_EXECUTION Phase of pkg
    SAPKIBIFQ4 BI_CONT 353: patch 0014.
    Error is in Method Execution step:
    InfoObject 0GRC_CSEOWR, version D being deleted, (basic char. not
    found)
    Start of the after-import method for object type R3TR DTMP ( )
    Errors occurred during post-handling RS_AFTER_IMPORT_D for DUPD L
    RS_AFTER_IMPORT_D belongs to package RS
    The errors affect the following components:
    BW-WHM (Warehouse Management)
    Post-import method RS_AFTER_IMPORT_D completed for DUPD L, date and
    time: 20080103122305
    Pls help me ASAP to resolve this error.
    Regards,
    Ankita

    Hi,
    I solved this problem after implementing
    Note 1083886 - Method IF_FDT_EXPRESSION~IS_GENERATING is not implemented.
    is thsi dosent work try restarting the queue again.
    Kind regards,
    Vamsi

  • Error at PHASE   SHD_FIX_IMP in R/3 upgrade.

    Hi,
    i am getting the below error:
    UPGRADE/SHADOW: END OF PHASE   SHD_FIX_IMP
    >> 13:00:28  UPGRADE/SHADOW: START OF PHASE SHD_FIX_IMP
    running C:\usr\sap\put\exe\tp.exe pf=C:\usr\sap\put\bin\SHD_FIX.TPP put DEV
    tp terminated successfully.
    analyzing result of tp call ...
    ERROR: 6 errors detected during SHD_FIX_IMP.
           Analyze summary error logfile SHD_FIX.ELG
           and remove all error conditions in the way
           it is described in the upgrade manual. Repeat
           this phase until it is error free.
           Additional hints may be given in logfiles
           SLOG640 and C:\usr\sap\put\log\R3up.ECO
      LIST OF ERRORS AND RETURN CODES  *******
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    CUSTOMER MAIN IMPORT ERRORS and RETURN CODE in B20I8A2NLM.DEV
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    2EETW000 Probably the data file was destroyed during file transfer!?
    2EETW000 Probably the data file was destroyed during file transfer!?
    2EETW000 Probably the data file was destroyed during file transfer!?
    1 ETP111 exit code           : "8"
    C:\usr\sap\put\exe\R3trans.exe finished (0000).
    Syslog: k CPG : &0000&C&0000&                                        rscploc   9Syslog: k CP3 : 0000&TCPDB&                                          rscpmi    1This is C:\usr\sap\put\exe\R3trans.exe version 6.09 (release 640 - 05.04.04 - 14:45:00).
    C:\usr\sap\put\exe\R3trans.exe finished (0004).
    Syslog: k CPG : &0000&C&0000&                                        rscploc   9Syslog: k CP3 : 0000&TCPDB&                                          rscpmi    1This is C:\usr\sap\put\exe\R3trans.exe version 6.09 (release 640 - 05.04.04 - 14:45:00).
    2EETW000 Probably the data file was destroyed during file transfer!?
    2EETW000 Probably the data file was destroyed during file transfer!?
    2EETW000 Probably the data file was destroyed during file transfer!?
    C:\usr\sap\put\exe\R3trans.exe finished (0008).
    stopping on error 8 during MAIN IMPORT
    tp returncode summary:
    TOOLS: Highest return code of single steps was: 8
    WARNS: Highest tp internal warning was: 0118
    tp finished with return code: 8
    meaning:
      A tool used by tp produced errors
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: stopping on error 8 during MAIN IMPORT
    Process with ID 3528 terminated with status 8
    Deleting file C:\usr\sap\put\log\SHD_FIX.ELG
    Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\B20I8A1JJN.DEV
    Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\B20I8A2NLM.DEV
    Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\B4AI009743.DEV
    Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\B4AI009755.DEV
    Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\B4AI009759.DEV
    Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\B4AI009760.DEV
    Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\B4AI009780.DEV
    Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\B6AI005685.DEV
    Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\F8HI900010.DEV
    Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\RS6I900005.DEV
    Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\Y6DI012127.DEV
    Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\Y6DI022467.DEV
    Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\Y6DI042418.DEV
    Moving file C:\usr\sap\put\log\SHD_FIX.ELG to C:\usr\sap\put\tmp\SHD_FIX.ELG
    Deleting file C:\usr\sap\put\tmp\MSGIN.LST
    Deleting file C:\usr\sap\put\tmp\MSGOUT.LST
    Deleting file C:\usr\sap\put\tmp\MSGOUT.LOG
    Deleting file C:\usr\sap\put\tmp\SHD_FIX.ELG

    Hello,
    When you get this problem first thing down load the latest R3trans
    then "uncar". Copy the uncar file into "/usr/sap/put/exe" after that
    repet this phase again. After few seconds you get the error again then you do one thing Go to "/usr/sap/<SID>/SYS/exe/run" copy the all files resides in run directory and paste in "/usr/sap/put/exe"
    then again repet the phase you get good output.
    Thanks & Regards,
    Sumanbabu.B

  • Error in TP_ACTION_CP2STRIG phase ERP 6 EHP4

    Hi all,
    I have a error in TP_ACTION_CP2STRIG phase, please check the error..
    SAPEBBQ701.GE3
    3 ETW685Xstart copying of "R3TRTABUKSML" ...
    4 ETW000 Mon Jul 26 09:36:14
    2010 104301412 359.495280
    4 ETW000 OCIStmtExecute() failed with
    -1=OCI_ERROR 26 359.495306
    4 ETW000 SQL error
    942: 17 359.495323
    ***4 ETW000 **LOG BZA=>table KSML~ does not**
    *exist on database *
    4
    ETW000
    69 359.495392
    2EETW000 sap_dext called with msgnr "2":
    2EETW000 -
    db call info -
    2EETW000 function: db_xrtab
    2EETW000 fcode: RT_INSERT
    2EETW000 tabname: KSML~
    2EETW000 len (char): 182
    2EETW000 key: 00099999900000010000
    99999493990000000000100 00000000 000
    2EETW000 retcode: 2
    2EETP200 Export with errors, request will not be imported
    1 ETP150 MAIN EXPORT
    1 ETP110 end date and time : "20100726093614"
    1 ETP111 exit code : "12"
    1 ETP199 ######################################
    4 EPU202XEND OF SECTION BEING ANALYZED
    Thank you
    Rogério

    Hi,
    I used the latest version of R3trans but the problem not solved.
    I used the SAPEHP Inst with the patch 32 but the problem not solved.
    In outhers ERP system with EHP 4 the table KSML~ not exist.
    The OSS with SAP opened.
    Thank you.
    Rogério

Maybe you are looking for

  • How Can I Fix The Graphics Issue...?

    After having my computer for a few years, it started getting an artifact around the mouse, and when it did that, everything was frozen, key commands didn't work, and I would have to manually shut it down. I went to the Apple store, and they couldn't

  • Problem w/ InitialContext

    Here is my issue: 1. I have and stateless session EJB deploy to OC4J (the preview release). 2. I have a servlet that access the the EJB using the "RMInitialContextFactory" factory. 3. When I deploy the servlet to Tomcat on a different box it works fi

  • Boot Mac Mini w/Bluetooth without Keyboard/Mouse attachted

    Hi, I´m trying to boot a Mac Mini with Bluetooth without any Keyboard/Mouse attachted to it. It doesn´t work. Every time the Mac stucks at looking for Bluetooth devices. Running 10.4.11 Any ideas? Thanks a lot, seb

  • [915 Series] LiveUpdate 3 Hangs systems at end of Windows XP boot

    After installing LiveUpdate 3, my system hangs near the end of XP boot.  Searching the forum, I found one thread related to this - https://forum-en.msi.com/index.php?topic=63173.0 but it didn't offer any solution. Anyone else experience this or have

  • Difference between building/consuming web service in ERP vs. XI (PI)

    Hi All, Can someone direct me to the pros and cons of whether to build/consume a web service in ERP (ABAP - SE80, etc.) versus in XI?  We have ECC 6.0 and the latest version of Web AS running - so no issues with that.  I'm just wondering - if we can