EHPI on Solman

Hi colleagues
Is EHPI supported to execute Solman 7.0 SP15 to 7.01 SP28 ?
I would like to optimize the time of this process and I think EHPI can help me here.

Hi Kumar,
Please use SAINT for updating SAP Solution Manager 7.0 to  SAP Solution Manager 7.0 Enhancement Package 1. For more
information please refer the note 1169247
1169247 - Additional info for Solution Manager 7.0 EHP1 update
Thank You.
Regards,
Deepika

Similar Messages

  • I want to connect ecc 6.0 server and SOLMAN server together

    Hello All , I need your help please ,
    I`m working on ecc 6.0 on windows server 2008 R2 and i want to upgrade some components via EHPI ,
    So after reading i reached that I need to install SOLMAN on another seperate server to generate the XML stack files for EHPI from t-code " mopz " .
    I`ve installed the SOLMAN on another server " windows server 2008 R2 " , and succsesfully finished .
    Now i have two seperated servers one for ECC and the other one for solution manager 7.1 .
    NOW I NEED to connect the two servers together to let them see each other .
    How Can I Connect them together Step by step Please ???
    Hope to help Immedietly And thnx in advance.

    Hi Rami,
    Once the basic configurations are done. It will be just 30 minutes sufficient to complete the connections between Solution manager and ECC 6 system.
    http://help.sap.com/saphelp_bpc70sp02/helpdata/en/83/47421d68ea497fb7b813e17843122d/content.htm
    Above link for the same.
    You should create ECC system in solution manager as below link
    http://help.sap.com/saphelp_bpc70sp02/helpdata/en/45/56dd10b5f62a50e10000000a11466f/frameset.htm
    Set SUser id to solution manager which comes under the basic settings.
    http://help.sap.com/saphelp_bpc70sp02/helpdata/en/45/56dd10b5f62a50e10000000a11466f/frameset.htm
    Maintain SAPOSS RFC connection, hope you have an SAPROUTER setup for your company.
    Please let us know if you are facing any issues.
    Thanks
    Jaianandh V

  • How to upgrade from Solman 7.0 to 7.0 EHP1?

    Hi,
    In the SAP note 1169247, it talks about doing the upgrade from 7.0 to EHP1 using SAINT and JSPM. But in the Upgrade Guide SAP Enhancement Package 1 for Solution Manager 7.0 - UNIX Oracle˝, it talks about running the upgrade using an Upgrade MAster DVD.
    1. Now is this the same as the EHP installer? If so, why is it not mentioned anywhere in the upgrade guide that we have to use EHPI? If not, what is this Upgrade Master installer?
    2. Should I use SAINT/JSPM for the upgrade to solman 7.01?
    Your answers to these questions will be highly appreciated.
    Thanks,
    Ajay

    Hi Ajay,
    I had the same question a few day's ago.
    The difference between these two methods are the word updarte and upgrade.
    If you are on Solman 7.0 you have to do a update with SPAM/SAINT.
    If you are on Solman 3.0 or something you have to do a upgrade with the master dvds. You can read this on one of the first sites of the upgrade guide.
    So you have to use SPAM/SAINT, and the Update Guide for EHP1 Using SPAM/SAINT will help you.
    [Update Guide on Marketplace|https://websmp101.sap-ag.de/~sapidb/011000358700000427772009E.PDF]
    Regards
    Tobias

  • Solman upgrade 7.1 error in  PREPARE_JSPM_QUEUE

    Hi All,
    We are upgrading solman from 7.0 EHP1 to 7.1 , getting the below error in  PREPARE_JSPM_QUEUE phase
    " Checking whether product SAP SOLUTION MANAGER with version 7.1 is supported by this EHP Installer.
    Feb 21, 2012 6:04:32 PM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.validateProducts(JSPMSpStackQueuePreparator.java:309) [Thread[main,5,main]]: The product is not supported.
    Feb 21, 2012 6:04:32 PM [Error]:                       com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase."
    I had checked the note Note 1431340 - EHPI fails at PREPARE_JSPM_QUEUE phase - stack rejected, no solution got .
    Can anyone advice please
    Regards,
    Nibu Antony

    Hi
    @ Nirmal
    For solman upgrade tool is Solmanup nad version is as below:
    Client Version 1.5.0 Server Version 1.5.0 Server Port 4241 DSUService
    Version: 1.1.6  Configured Plugins 
    Plugin ABAP at Version:      
    1.0.3      
    Plugin J2EE at Version:      
    1.0.5      
    I had already gone through the thread and the note as mentioned in initially, no luck still..

  • Upgrade SAP Solman

    Boa noite colegas de SAP
    Gostaria de saber se eu poderia usar o SAPEHPI para fazer o update de meu sistema solman para SP28, temos uma versão muito antiga e gostaria de fazer esse update diretamente, na minha dúvida anterior gostaria de saber quais são os benefícios dessa nova versão 7.01 SP28.

    Bom dia Marcos, segundo a nota 1169247, você não pode utilizar o SAPEHPI.
       -  You can perform the update only using SAINT and JSPM. Using the EHPI is not intended and is not supported. Ignore the
          corresponding message in transaction SAINT.

  • Pre Requistes for to start Ehpi

    Hi,
      We have  SAP ECC 6.0 with patch level 09(i.e Basis at 09 , ABAP at 09 , APPL at 06).
    We have upgraded our solman to Ehp1 and the maitenance optimizer is configured.
    Can i Directly start the installation of the EHp4 with ehp installer and it will also do the stack update or first i have to update any patches in ecc6 system then i have to start Ehpi.
    Thanku

    Hi Kumar,
    You can do directly from here. For more information check SAP Note 849887 - SAP ERP 6.0: Support Package Stacks
    Release and Info Note
    Thanks
    Sunny

  • SOLMAN EHP1 - anyone can create support message in Satellite System's Help?

    Hi,
    I just curios that why everyone can create support message in satellite system-> help -> create support message?
    I tested with restricted profile user and without role SAP_SUPPDESK_CREATE, NO BP created but he still manage to create support message???? Any idea??
    Also, same goes to any user can process ticket in SOLMAN with no BP-Employee role and SAP_SUPPDESK_* roles assigned.
    Your kind input is very much appreciated.
    Thanks,
    Nicholas Chang

    Hi Nicholas
    If you are using a "Named" user instead of the Trusted Relationship in the RFC maintained in BCOS_CUST for entry OSS_MSG then this is quite possible. In this case the "Named" user will be used to call the interface to create message and the calling user ie the end user creating the ticket will only be used as "Reporter" of the message.
    The user entered in the RFC details probably has the authorization to create Support desk messages.
    Regards
    Amit

  • Creating a New Task in SOLMAN Change request Management

    Dear all,
    We are using SOLMAN 4.0 and scm functionality.In the change request screen we have a create follow up task(+ icon on top left).What is the use of this task,can we asign a task to some particular person?for example can i assign task to tester?If the task has not completed the task,while closing the correction will it give error?
    Please give your suggestions.
    Thanks in advance,
    Avinash.

    Hi,
    Pls click the check button(next to activate button)
    see the SLG1 log generated remove the errors shown in red.
    One it is done u press the refresh button & thn u cn create the task list
    chk
    https://websmp202.sap-ag.de/~sapdownload/011000358700000657692007E/ECTS_CHARM_SP12.PDF
    /people/dolores.correa/blog/2008/07/26/first-steps-to-work-with-change-request-management-scenario
    http://help.sap.com/saphelp_sm32/helpdata/en/0c/5b2160f6fa4b83a3674a210b1cdeb0/content.htm
    Regards
    Prakhar

  • Logical component in SolMan using SMSY

    Hi,
    What is a logical component and why is it necessary. Why do we create that in our solman system for the landscape.
    Also i was going through one tutor in rkt-solman link for creating logical component. It shows for a r/3 system. Is the same selection valid for the Netweaver component also.
    Help required and shall be appreciated as well.

    Hi,
    First of all thanks for the reply.
    One thing is while i create a new system with assistant, and select the product as netweaver and proceed it asks me to select the main instance. What is this main instance. Say for me the system i am adding is the one having J2ee engine and portal plus trex on it. It doesnot have the ABAP instance. So what should be my selection. Should it be only WebAS Java or java + portal + trex.
    Secondly what i did was i selected java and EP and Trex and proceeded. It didn't give me the option of entering the System Number and Message Server. In the next screen the only option i had was to assign logical component. If i select the box then it asks for client but the box for client is disabled.
    Don't know what to do. Also RFC anyway is required. In such a case what should be the case. How should i create those RFC's and what RFC's are required for the same.
    Lot of questions. Hope to get the detailed reply.
    Answers will be rewarded nicely.
    Thanks

  • Error in installing Solman 4.0 SR2

    Hi,
    An Error occured during the installation of Solman 4.0 SR2 in import ABAP phase.
    Sofware and Hardware configurartion:
    Java 1.4.2_12
    Database MSSQL 2005 SP2
    Solution manager 4.0 SR2
    Dual core 2.6 GHZ
    2 gb ram
    160gb hard drive
    Plz find attached the sapinst.log file and import_monitor.log file.
    Needfull help in this regard would be highly appreciated. Deserving points will be rewarded.
    Best Regards
    Omeir.
    *import_monior.log*
    INFO: 2007-09-21 01:21:36
    Import Monitor is started.
    CONFIG: 2007-09-21 01:21:36
    Application options:
    dbCodepage=4103
    dbType=MSS
    extFiles=no
    importDirs=E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4
    installDir=C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS
    jobNum=3
    loadArgs= -loadprocedure fast
    monitorTimeout=30
    orderBy=
    r3loadExe=C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe
    sapinst=
    trace=all
    tskFiles=yes
    CONFIG: 2007-09-21 01:21:36
    List of packages with table structure: 'SAP0000'.
    CONFIG: 2007-09-21 01:21:36
    List of packages with views: 'SAPVIEW'.
    TRACE: 2007-09-21 01:21:36 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is started.
    INFO: 2007-09-21 01:21:36 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is successfully completed.
    Primary key creation: before load.
    Index creation: after load.
    INFO: 2007-09-21 01:21:36
    Data codepage 1100 is determined using TOC file 'E:\Export\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
    INFO: 2007-09-21 01:21:37
    Version table 'SVERS' is found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
    INFO: 2007-09-21 01:21:37
    Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
    TRACE: 2007-09-21 01:21:37 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDIC' import package is started.
    TRACE: 2007-09-21 01:21:37 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSDIC' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP2\DATA\SAPSDIC.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDIC.TSK MSS -l SAPSDIC.log
    TRACE: 2007-09-21 01:21:37 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSDIC' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -loadprocedure fast
    INFO: 2007-09-21 01:25:22 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDIC' import package is successfully completed.
    TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is started.
    TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSSEXC' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP1\DATA\SAPSSEXC.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSSEXC.TSK MSS -l SAPSSEXC.log
    TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is started.
    TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL0' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPAPPL0.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL0.TSK MSS -l SAPAPPL0.log
    TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL1' import package is started.
    TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL1' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP4\DATA\SAPAPPL1.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL1.TSK MSS -l SAPAPPL1.log
    TRACE: 2007-09-21 01:25:37 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSSEXC' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast
    TRACE: 2007-09-21 01:25:37 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL1' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
    TRACE: 2007-09-21 01:25:38 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL0' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
    INFO: 2007-09-21 13:22:54
    Import Monitor is started.
    CONFIG: 2007-09-21 13:22:54
    Application options:
    dbCodepage=4103
    dbType=MSS
    extFiles=no
    importDirs=E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4
    installDir=C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS
    jobNum=3
    loadArgs= -loadprocedure fast
    monitorTimeout=30
    orderBy=
    r3loadExe=C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe
    sapinst=
    trace=all
    tskFiles=yes
    CONFIG: 2007-09-21 13:22:54
    List of packages with table structure: 'SAP0000'.
    CONFIG: 2007-09-21 13:22:54
    List of packages with views: 'SAPVIEW'.
    TRACE: 2007-09-21 13:22:54 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is started.
    INFO: 2007-09-21 13:22:54 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is successfully completed.
    Primary key creation: before load.
    Index creation: after load.
    INFO: 2007-09-21 13:22:54
    Data codepage 1100 is determined using TOC file 'E:\Export\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
    INFO: 2007-09-21 13:22:58
    Version table 'SVERS' is found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
    INFO: 2007-09-21 13:22:58
    Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
    TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is started.
    TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL1' import package is started.
    TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is started.
    TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSSEXC' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast
    TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL1' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
    TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL0' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
    ERROR: 2007-09-21 13:23:21 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is interrupted with R3load error.
    Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast' exited with return code 2.
    For mode details see 'SAPAPPL0.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: 2007-09-21 13:23:21 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL1' import package is interrupted with R3load error.
    Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast' exited with return code 2.
    For mode details see 'SAPAPPL1.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: 2007-09-21 13:23:21 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is interrupted with R3load error.
    Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast' exited with return code 2.
    For mode details see 'SAPSSEXC.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL2' import package is started.
    TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSRC' import package is started.
    TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL2' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP2\DATA\SAPAPPL2.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL2.TSK MSS -l SAPAPPL2.log
    TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPPOOL' import package is started.
    TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSSRC' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP4\DATA\SAPSSRC.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSSRC.TSK MSS -l SAPSSRC.log
    TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPPOOL' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP2\DATA\SAPPOOL.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPPOOL.TSK MSS -l SAPPOOL.log
    TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPPOOL' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPPOOL.cmd -dbcodepage 4103 -l SAPPOOL.log -loadprocedure fast
    TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSSRC' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -loadprocedure fast
    TRACE: 2007-09-21 13:23:25 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL2' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -loadprocedure fast
    INFO: 2007-09-21 13:24:19 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPPOOL' import package is successfully completed.
    TRACE: 2007-09-21 13:24:24 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSPROT' import package is started.
    TRACE: 2007-09-21 13:24:24 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSPROT' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPSPROT.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSPROT.TSK MSS -l SAPSPROT.log
    TRACE: 2007-09-21 13:24:24 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSPROT' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -loadprocedure fast
    INFO: 2007-09-21 13:25:38 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSPROT' import package is successfully completed.
    TRACE: 2007-09-21 13:25:54 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDOCU' import package is started.
    TRACE: 2007-09-21 13:25:54 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSDOCU' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP2\DATA\SAPSDOCU.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDOCU.TSK MSS -l SAPSDOCU.log
    TRACE: 2007-09-21 13:25:54 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSDOCU' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -loadprocedure fast
    INFO: 2007-09-21 13:26:05 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDOCU' import package is successfully completed.
    TRACE: 2007-09-21 13:26:24 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLEXC' import package is started.
    TRACE: 2007-09-21 13:26:24 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSLEXC' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPSLEXC.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSLEXC.TSK MSS -l SAPSLEXC.log
    TRACE: 2007-09-21 13:26:24 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSLEXC' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -loadprocedure fast
    INFO: 2007-09-21 13:26:30 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLEXC' import package is successfully completed.
    TRACE: 2007-09-21 13:26:54 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPCLUST' import package is started.
    TRACE: 2007-09-21 13:26:54 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPCLUST' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPCLUST.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPCLUST.TSK MSS -l SAPCLUST.log
    TRACE: 2007-09-21 13:26:56 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPCLUST' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -loadprocedure fast
    INFO: 2007-09-21 13:27:12 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPCLUST' import package is successfully completed.
    TRACE: 2007-09-21 13:27:24 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLOAD' import package is started.
    TRACE: 2007-09-21 13:27:24 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSLOAD' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPSLOAD.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSLOAD.TSK MSS -l SAPSLOAD.log
    TRACE: 2007-09-21 13:27:24 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSLOAD' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -loadprocedure fast
    INFO: 2007-09-21 13:27:28 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLOAD' import package is successfully completed.
    INFO: 2007-09-21 13:27:40 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSRC' import package is successfully completed.
    TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDFACT' import package is started.
    TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDDIM' import package is started.
    TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPDDIM' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPDDIM.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDDIM.TSK MSS -l SAPDDIM.log
    TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPDFACT' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPDFACT.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDFACT.TSK MSS -l SAPDFACT.log
    TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPDDIM' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -loadprocedure fast
    TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPDFACT' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -loadprocedure fast
    INFO: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDDIM' import package is successfully completed.
    INFO: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDFACT' import package is successfully completed.
    TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPUSER' import package is started.
    TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDODS' import package is started.
    TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPUSER' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPUSER.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPUSER.TSK MSS -l SAPUSER.log
    TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPDODS' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPDODS.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDODS.TSK MSS -l SAPDODS.log
    TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPDODS' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -loadprocedure fast
    TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPUSER' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -loadprocedure fast
    INFO: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPUSER' import package is successfully completed.
    INFO: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDODS' import package is successfully completed.
    TRACE: 2007-09-21 13:28:54 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is started.
    TRACE: 2007-09-21 13:28:54 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAP0000' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP4\DATA\SAP0000.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAP0000.TSK MSS -l SAP0000.log -o D
    TRACE: 2007-09-21 13:28:54 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAP0000' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAP0000.cmd -dbcodepage 4103 -l SAP0000.log -loadprocedure fast
    INFO: 2007-09-21 13:28:54 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is successfully completed.
    INFO: 2007-09-21 13:34:56 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL2' import package is successfully completed.
    WARNING: 2007-09-21 13:35:24
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2007-09-21 13:35:24
    3 error(s) during processing of packages.
    INFO: 2007-09-21 13:35:24
    Import Monitor is stopped.
    INFO: 2007-09-21 13:38:06
    Import Monitor is started.
    CONFIG: 2007-09-21 13:38:06
    Application options:
    dbCodepage=4103
    dbType=MSS
    extFiles=no
    importDirs=E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4
    installDir=C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS
    jobNum=3
    loadArgs= -loadprocedure fast
    monitorTimeout=30
    orderBy=
    r3loadExe=C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe
    sapinst=
    trace=all
    tskFiles=yes
    CONFIG: 2007-09-21 13:38:06
    List of packages with table structure: 'SAP0000'.
    CONFIG: 2007-09-21 13:38:06
    List of packages with views: 'SAPVIEW'.
    TRACE: 2007-09-21 13:38:06 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is started.
    INFO: 2007-09-21 13:38:06 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is successfully completed.
    Primary key creation: before load.
    Index creation: after load.
    INFO: 2007-09-21 13:38:06
    Data codepage 1100 is determined using TOC file 'E:\Export\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
    INFO: 2007-09-21 13:38:06
    Version table 'SVERS' is found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
    INFO: 2007-09-21 13:38:06
    Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
    TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is started.
    TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL1' import package is started.
    TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSSEXC' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast
    TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is started.
    TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL1' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
    TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL0' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
    ERROR: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is interrupted with R3load error.
    Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast' exited with return code 2.
    For mode details see 'SAPSSEXC.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL1' import package is interrupted with R3load error.
    Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast' exited with return code 2.
    For mode details see 'SAPAPPL1.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    ERROR: 2007-09-21 13:38:08 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is interrupted with R3load error.
    Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast' exited with return code 2.
    For mode details see 'SAPAPPL0.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    WARNING: 2007-09-21 13:38:36
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2007-09-21 13:38:36
    3 error(s) during processing of packages.
    INFO: 2007-09-21 13:38:36
    Import Monitor is stopped.
    sapinst.log
    INFO 2007-09-21 13:22:26
    Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.2.xml'.
    INFO 2007-09-21 13:22:27
    Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.3.xml'.
    INFO 2007-09-21 13:22:29
    Execute step
    Component  W2K_ServicePack_Check|ind|ind|ind|ind
    Preprocess  of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|0|0|W2K_ServicePack_Check|ind|ind|ind|ind|2|0.
    INFO 2007-09-21 13:22:40
    Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/keydb.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/keydb.2.xml'.
    INFO 2007-09-21 13:22:41
    Execute step runMigrationMonitor of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0.
    INFO 2007-09-21 13:22:51
    Switched to user: prdadm.
    INFO 2007-09-21 13:22:51
    Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\import_monitor.java.log.
    INFO 2007-09-21 13:22:51
    Switched to user: prdadm.
    INFO 2007-09-21 13:22:51
    Working directory changed to C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS.
    INFO 2007-09-21 13:22:51
    Output of C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst is written to the logfile import_monitor.java.log.
    WARNING 2007-09-21 13:35:24
    Execution of the command "C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst" finished with return code 103. Output:
    java version "1.4.2_12"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
    Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
    Import Monitor jobs: running 1, waiting 16, completed 1, failed 0, total 18.
    Import Monitor jobs: running 2, waiting 15, completed 1, failed 0, total 18.
    Import Monitor jobs: running 3, waiting 14, completed 1, failed 0, total 18.
    Loading of 'SAPAPPL0' import package: ERROR
    Loading of 'SAPAPPL1' import package: ERROR
    Import Monitor jobs: running 1, waiting 14, completed 1, failed 2, total 18.
    Import Monitor jobs: running 0, waiting 14, completed 1, failed 3, total 18.
    Loading of 'SAPSSEXC' import package: ERROR
    Import Monitor jobs: running 0, waiting 14, completed 1, failed 3, total 18.
    Import Monitor jobs: running 1, waiting 13, completed 1, failed 3, total 18.
    Import Monitor jobs: running 2, waiting 12, completed 1, failed 3, total 18.
    Import Monitor jobs: running 3, waiting 11, completed 1, failed 3, total 18.
    Loading of 'SAPPOOL' import package: OK
    Import Monitor jobs: running 2, waiting 11, completed 2, failed 3, total 18.
    Import Monitor jobs: running 3, waiting 10, completed 2, failed 3, total 18.
    Loading of 'SAPSPROT' import package: OK
    Import Monitor jobs: running 2, waiting 10, completed 3, failed 3, total 18.
    Import Monitor jobs: running 3, waiting 9, completed 3, failed 3, total 18.
    Loading of 'SAPSDOCU' import package: OK
    Import Monitor jobs: running 2, waiting 9, completed 4, failed 3, total 18.
    Import Monitor jobs: running 3, waiting 8, completed 4, failed 3, total 18.
    Loading of 'SAPSLEXC' import package: OK
    Import Monitor jobs: running 2, waiting 8, completed 5, failed 3, total 18.
    Import Monitor jobs: running 3, waiting 7, completed 5, failed 3, total 18.
    Loading of 'SAPCLUST' import package: OK
    Import Monitor jobs: running 2, waiting 7, completed 6, failed 3, total 18.
    Import Monitor jobs: running 3, waiting 6, completed 6, failed 3, total 18.
    Loading of 'SAPSLOAD' import package: OK
    Import Monitor jobs: running 2, waiting 6, completed 7, failed 3, total 18.
    Loading of 'SAPSSRC' import package: OK
    Import Monitor jobs: running 1, waiting 6, completed 8, failed 3, total 18.
    Import Monitor jobs: running 2, waiting 5, completed 8, failed 3, total 18.
    Import Monitor jobs: running 3, waiting 4, completed 8, failed 3, total 18.
    Loading of 'SAPDDIM' import package: OK
    Import Monitor jobs: running 2, waiting 4, completed 9, failed 3, total 18.
    Loading of 'SAPDFACT' import package: OK
    Import Monitor jobs: running 1, waiting 4, completed 10, failed 3, total 18.
    Import Monitor jobs: running 2, waiting 3, completed 10, failed 3, total 18.
    Import Monitor jobs: running 3, waiting 2, completed 10, failed 3, total 18.
    Loading of 'SAPUSER' import package: OK
    Import Monitor jobs: running 2, waiting 2, completed 11, failed 3, total 18.
    Loading of 'SAPDODS' import package: OK
    Import Monitor jobs: running 1, waiting 2, completed 12, failed 3, total 18.
    Import Monitor jobs: running 2, waiting 1, completed 12, failed 3, total 18.
    Loading of 'SAP0000' import package: OK
    Import Monitor jobs: running 1, waiting 1, completed 13, failed 3, total 18.
    Loading of 'SAPAPPL2' import package: OK
    Import Monitor jobs: running 0, waiting 1, completed 14, failed 3, total 18.
    ERROR 2007-09-21 13:35:24
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
    ERROR 2007-09-21 13:35:24
    FCO-00011  The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
    INFO 2007-09-21 13:38:06
    An error occured and the user decided to retry the current step: "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor".
    INFO 2007-09-21 13:38:06
    Switched to user: prdadm.
    INFO 2007-09-21 13:38:06
    Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\import_monitor.java.log.
    INFO 2007-09-21 13:38:06
    Switched to user: prdadm.
    INFO 2007-09-21 13:38:06
    Working directory changed to C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS.
    INFO 2007-09-21 13:38:06
    Output of C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst is written to the logfile import_monitor.java.log.
    WARNING 2007-09-21 13:38:36
    Execution of the command "C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst" finished with return code 103. Output:
    java version "1.4.2_12"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
    Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
    Import Monitor jobs: running 1, waiting 3, completed 14, failed 0, total 18.
    Import Monitor jobs: running 2, waiting 2, completed 14, failed 0, total 18.
    Import Monitor jobs: running 3, waiting 1, completed 14, failed 0, total 18.
    Loading of 'SAPSSEXC' import package: ERROR
    Import Monitor jobs: running 2, waiting 1, completed 14, failed 1, total 18.
    Loading of 'SAPAPPL1' import package: ERROR
    Import Monitor jobs: running 1, waiting 1, completed 14, failed 2, total 18.
    Loading of 'SAPAPPL0' import package: ERROR
    Import Monitor jobs: running 0, waiting 1, completed 14, failed 3, total 18.
    ERROR 2007-09-21 13:38:36
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
    ERROR 2007-09-21 13:38:36
    FCO-00011  The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
    INFO 2007-09-21 13:38:40
    An error occured and the user decide to stop.\n Current step "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor".
    Edited by: mohammed  omeir on Dec 31, 2007 2:30 PM

    Hi Markus,
    Its says a previous run may not have finished clearly.
    What i need to do now?
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20070921132313
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Sep  1 2006 00:38:35
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
    Hi Markus,
    Its says a previous
    (DB) INFO: connected to DB
    (TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPAPPL1.TSK.bck already seems to exist
                 a previous run may not have been finished cleanly
                 file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPAPPL1.TSK possibly corrupted
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20070921132321
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20070921133807
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Sep  1 2006 00:38:35
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
    (DB) INFO: connected to DB
    (TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPAPPL1.TSK.bck already seems to exist
                 a previous run may not have been finished cleanly
                 file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPAPPL1.TSK possibly corrupted
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20070921133807

  • EHPI installer: Error while reading a dynpro. Stuck at Start Shadow First.

    Hi Everyone,
    I am dead in the water with my test install of EhP5 using the most current installer.  This small test is on an older iseries, V5R4 with 8G memory. The SAP version is ECC 6.0 at sp Basis  23 and Applications at 19.
    The install stops at Start Shadow First, but the instance and work processes are up on the server.   The log- SAPehpiConsole reads:
    Severe error(s) occured in phase MAIN_SHADOW/START_SHDI_FIRST!
    Last error code set: RFC call to upg_is_shadow_system failed with key
    RFC_ERROR_SYSTEM_FAILURE (open): Error while reading a dynpro
    Please refer to these logs in the posted replys following this post for readability.
    The shadow system work process wp01 log showsan RFC error as follows:
    Wed Sep 14 11:29:58 2011
    ABAP Program SAPMSSY2                                .
    Source                                          Line 0.
    Error Code DYNPRO_READ_FAILED.
    Module  $Id: //bas/720_REL/src/krn/dynp/dyrdypdb.c#3 $ SAP.
    Function dy_dbread Line 100.
    RABAX: level LEV_RX_STDERR completed.
    RABAX: level LEV_RX_RFC_ERROR entered.
    RABAX: level LEV_RX_RFC_ERROR completed.
    RABAX: level LEV_RX_RFC_CLOSE entered.
    RABAX: level LEV_RX_RFC_CLOSE completed.
    RABAX: level LEV_RX_ERROR_SAVE entered.
    RABAX: level LEV_RX_ERROR_SAVE completed.
    RABAX: level LEV_RX_ERROR_TPDA entered.
    RABAX: level LEV_RX_ERROR_TPDA completed.
    RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
    RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
    RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
    RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
    RABAX: level LEV_RX_END entered.
    RABAX: level LEV_RX_END completed.
    RABAX: end no http/smtp
    RABAX: end RX_BTCHLOG RX_VBLOG
    Error while reading a dynpro.
    C Wed Sep 14 11:33:59 2011
    C  *** ERROR => SQL-Error -204 in function db_open  (dbsldb4.cpp  10630)
    C  {root-id=4E6F19A9A5F02851E10080020A7F0064}_{conn-id=}_0
    RABAX: level LEV_RX_IMC_ERROR entered.
    RABAX: level LEV_RX_IMC_ERROR completed.
    RABAX: level LEV_RX_DATASET_CLOSE entered.
    RABAX: level LEV_RX_DATASET_CLOSE completed.
    C  Reopen: FALSE
    B  *** ERROR => dbdynpdb2: dbdd_dbtab_columns (DYNPSOURCE) failed with rc = 4
    dbdynpdb2.c  2506]
    B  {root-id=4E6F19A9A5F02851E10080020A7F0064}_{conn-id=00000000000000000000000000000000}_0
    B  ***LOG BZY=> unexpected return code 4          calling dbdd_dbtab [dbdynpdb     2508]
    So I have a problem communicating with the shadow. Or is it a problem with the db_open?
    From the test system I have an entry in SM59 to the shadow and I get this error when trying a connection test.
    Error Details     Error while reading a dynpro.
    And trying to logon to the client sends the same message, it does not bring up the login screen.
    OK. So in the 3 weeks that I have restarted, re-set and completely restored and restarted the install, I have always come to this point. I have search for similar issues and have done a review of pertinent notes etcu2026    Just as a comment, last year I successfully did the Ehp 4 upgrade without many problems on this same system using last years SAP system.   In the month that I have been trying to do this,  SAP has replaced the EHPI installer 3 times which indicates some problems on their part.
    Any comments or suggestions would be greatly appreciated.
    Pat

    The 2 logs from the installer are here.
    The STARTSFI is as follows:
    1 ETQ201 Entering upgrade-phase "START_SHDI_FIRST" ("20110913144811")
    4 ETQ399 Set environment for standard connect:
    2 ETQ367 Connect variables are set for standard instance access
    4 ETQ399 System-nr = '14', GwService = 'sapgw14'
    4 ETQ399 Environment variables:
    4 ETQ399   dbs_db4_schema=SAPR3
    4 ETQ399   auth_shadow_upgrade=0
    1 ETQ206 Executing pre-phase DB specific actions.
    3 ETQ399 Fixing IFS authorities for '/usr/sap/TEH/EHPI/abap/exe'
    1 ETQ206 Executing pre-phase DB specific actions.
    1 ETQ200 Executing actual phase 'MAIN_SHADOW/START_SHDI_FIRST'.
    1 ETQ399 Phase arguments:
    2 ETQ399 Arg[0] = 'DEVTRACE.LOG'
    4 ETQ399 Set environment for shadow connect:
    4 ETQ399 Set RFC variables for shadow connect:
    4 ETQ399 System-nr = '15', GwService = 'sapgw15'
    4 ETQ380 computing toolpath for request "TP_SHADOW_CONNECT"
    4 ETQ381 request "TP_SHADOW_CONNECT" means "tp needs to connect to shadow system"
    4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
    4 ETQ383 translates to path "exe"
    4 ETQ383 translates to path "exe"
    4 ETQ399 Set tool parameters for shadow connect:
    4 ETQ399   default TPPARAM: SHADOW.TPP
    4 ETQ380 computing toolpath for request "TP_ALWAYS_NEW"
    4 ETQ381 request "TP_ALWAYS_NEW" means "always tp from DIR_PUT/exe, for phase KX_SWI
    4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
    4 ETQ383 translates to path "exe"
    4 ETQ383 translates to path "exe"
    2 ETQ399 Starting shadow instance
    4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
    2 ETQ231 RFC Login failed
    repeats the rfc call with a fail until this final entry.
    2EETQ399 Starting shadow instance failed
    2EETQ399 Test RFC failed finally
      The DEVTRACE.LOG is here:
    $                               Directory:    /usr/sap/TEH/EHPI/abap/log
    Name:         DEVTRACE.LOG
    trc file: "dev_disp.new", trc level: 1, release: "720"
    sysno      15
    sid        TEH
    systemid   327 (IBM i with OS400)
    relno      7200
    patchlevel 0
    patchno    100
    intno      20020600
    make       single threaded, ASCII, 64 bit, optimized
    profile    /usr/sap/TEH/EHPI/abap/TEH/SYS/profile/TEH_DVEBMGS15_omni
    pid        75851
    kernel runs with dp version 131(ext=118) (@(#) DPLIB-INT-VERSION-131)
    length of sys_adm_ext is 376 bytes
    SWITCH TRC-HIDE on ***
    ***LOG Q00=> DpSapEnvInit, DPStart (15 75851) [dpxxdisp.c   1287]
    #shared lib "dw_xml.so" version 100 successfully loaded
    #shared lib "dw_xtc.so" version 100 successfully loaded
    #shared lib "dw_stl.so" version 100 successfully loaded
    #shared lib "dw_gui.so" version 100 successfully loaded
    #shared lib "dw_mdm.so" version 100 successfully loaded
    #shared lib "dw_rndrt.so" version 100 successfully loaded
    #shared lib "dw_abp.so" version 100 successfully loaded
    #shared lib "dw_sym.so" version 100 successfully loaded
    #shared lib "dw_aci.so" version 100 successfully loaded
    rdisp/softcancel_sequence :  -> 0,5,-1
    rdisp/dynamic_wp_check : 0
    rdisp/calculateLoadAverage : 1
    Tue Sep 13 14:48:58 2011
    WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds
    ***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  6404]
    MtxInit: 30000 0 0
    DpSysAdmExtInit: ABAP is active
    DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
    DpIPCInit2: write dp-profile-values into sys_adm_ext
    DpIPCInit2: start server >omni_TEH_15                             <
    DpShMCreate: sizeof(wp_adm)##17440#(1744)
    DpShMCreate: sizeof(tm_adm)##4976768#(24760)
    DpShMCreate: sizeof(wp_ca_adm)##56000#(56)
    DpShMCreate: sizeof(appc_ca_adm)#56000#(56)
    DpCommTableSize: max/headSize/ftSize/tableSize=500/16/576048/576064
    DpShMCreate: sizeof(comm_adm)##576064#(1136)
    DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
    DpShMCreate: sizeof(slock_adm)##0#(104)
    DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    DpShMCreate: sizeof(file_adm)##0#(80)
    DpShMCreate: sizeof(vmc_adm)##0#(1856)
    DpShMCreate: sizeof(wall_adm)##(25648/36736/64/104)
    DpShMCreate: sizeof(gw_adm)#48
    DpShMCreate: sizeof(j2ee_adm)#2032
    DpShMCreate: SHM_DP_ADM_KEY##(addr: 700000050000000, size: 5759216)
    DpShMCreate: allocated sys_adm at 700000050000010
    DpShMCreate: allocated wp_adm_list at 700000050002970
    DpShMCreate: allocated wp_adm at 700000050002b60
    DpShMCreate: allocated tm_adm_list at 700000050006f90
    DpShMCreate: allocated tm_adm at 700000050006fe0
    DpShMCreate: allocated wp_ca_adm at 7000000504c6070
    DpShMCreate: allocated appc_ca_adm at 7000000504d3b40       
    Directory:    /usr/sap/TEH/EHPI/abap/log
    Name:         DEVTRACE.LOG
    DpShMCreate: allocated comm_adm at 7000000504e1610
    DpShMCreate: system runs without slock table
    DpShMCreate: system runs without file table
    DpShMCreate: allocated vmc_adm_list at 70000005056e060
    DpShMCreate: system runs without vmc_adm
    DpShMCreate: allocated gw_adm at 70000005056e110
    DpShMCreate: allocated j2ee_adm at 70000005056e150
    DpShMCreate: allocated ca_info at 70000005056e950
    DpShMCreate: allocated wall_adm at 70000005056e9d0
    DpCommAttachTable: attached comm table (header=7000000504e1610/ft=7000000504e1620)
    DpSysAdmIntInit: initialize sys_adm
    rdisp/test_roll : roll strategy is DP_NORMAL_ROLL
    dia token check not active (3 token)
    MBUF state OFF
    DpCommInitTable: init table for 500 entries
    DpRqQInit: keep protect_queue / slots_per_queue 0 / 2001 in sys_adm
    rdisp/queue_size_check_value :  -> on,50,30,40,500,50,500,80
    EmInit: MmSetImplementation( 2 ).
    MM global diagnostic options set: 0
    <ES> client 0 initializing ....
    <ES> InitFreeList
    <ES> block size is 4096 kByte.
    Using implementation std
    EsStdUnamFileMapInit: ES base = 0x7000000a0000000
    EsStdInit: Extended Memory 4096 MB allocated
    <ES> 1023 blocks reserved for free list.
    ES initialized.
    mm.dump: set maximum dump mem to 96 MB
    DpVmcSetActive: set vmc state DP_VMC_NOT_ACTIVE
    MPI: dynamic quotas disabled.
    MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
    Tue Sep 13 14:48:59 2011
    WARNING => System running without ICM - check rdisp/start_icman [dpxxdisp.c   13097]
    Tue Sep 13 14:49:02 2011
    rdisp/http_min_wait_dia_wp : 1 -> 1
    ***LOG Q0K=> DpMsAttach, mscon ( omni) [dpxxdisp.c   12339]
    MBUF state LOADING
    DpStartStopMsg: send start message (myname is >omni_TEH_15                             <)
    DpStartStopMsg: start msg sent
    Tue Sep 13 14:49:11 2011
    CCMS uses Shared Memory Key 73 for monitoring.
    CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
    CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
    CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    Tue Sep 13 14:49:13 2011
    CCMS: start to initalize 3.X shared alert area (first segment).
    DpMBufHwIdSet: set Hardware-ID
    ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1296]
    MBUF state ACTIVE
    DpWpBlksLow: max wp blocks in queue is 800 (80 %)
    MBUF component UP
    DpMsgProcess: 1 server in MBUF
    DpAppcBlksLow: max appc blocks in queue is 500 (50 %)
    Tue Sep 13 14:50:24 2011
    DpModState: change server state from STARTING to ACTIVE
    trc file: "dev_ms.new", trc level: 1, release: "720"
    [Thr 01] Tue Sep 13 14:48:39 2011
    [Thr 01] MsSOsPrivInit: Run priority adjusted to 12
    [Thr 01] ms/http_max_clients = 500 -> 500
    [Thr 01] MsSSetTrcLog: trc logging active, max size = 52428800 bytes
    systemid   327 (IBM i with OS400)
    relno      7200
    patchlevel 0
    patchno    92
    intno      20020600
    make       multithreaded, ASCII, 64 bit, optimized
    pid        75850
    [Thr 01] Tue Sep 13 14:48:40 2011
    [Thr 01] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 75850) [msxxserv_mt. 2274]
    [Thr 01] SigISetDefaultAction : default handling for signal SIGCHLD
    [Thr 01] load acl file = /usr/sap/TEH/EHPI/abap/TEH/SYS/global/ms_acl_info
    [Thr 01] MsGetOwnIpAddr: my host addresses are :
    [Thr 01]   1 : [10.127.0.100] omni.plastekgroup.com (HOSTNAME)
    [Thr 01]   2 : [127.0.0.1] LOOPBACK (LOCALHOST)
    [Thr 01] MsHttpInit: full qualified hostname = omni.plastekgroup.com
    [Thr 01] HTTP logging is switch off
    [Thr 01] MsHttpOwnDomain: own domain[1] = plastekgroup.com
    [Thr 01] *** I listen to port 3615 (3615) ***
    [Thr 01] CUSTOMER KEY: >H1357713078<
    [Thr 01] build version=720.2011.05.04
    trc file: "dev_rd", trc level: 1, release: "720"
    Tue Sep 13 14:49:07 2011
    ***LOG S00=> GwInitReader, gateway started ( 75855) [gwxxrd.c     1758]
    systemid   327 (IBM i with OS400)
    relno      7200
    patchlevel 0
    patchno    96
    intno      20020600
    make       single threaded, ASCII, 64 bit, optimized
    pid        75855
    gateway runs with dp version 131(ext=118) (@(#) DPLIB-INT-VERSION-131)
    gateway (version=720.2011.04.20)
    Tue Sep 13 14:49:10 2011
    gw/reg_no_conn_info = 1
    gw/local_addr : 0.0.0.0
    gw/reg_no_conn_info = 1
    SWITCH TRC-RESOLUTION from 1 TO 1
    CCMS: initialize CCMS Monitoring for ABAP instance with J2EE addin.
    CCMS uses Shared Memory Key 73 for monitoring.
    CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    Tue Sep 13 14:49:13 2011
    CCMS: Initalized shared memory of size 40000000 for monitoring segment.
    CCMS: Checking Downtime Configuration of Monitoring Segment.
    CCMS: AlMsUpload called by wp 1002.
    CCMS: AlMsUpload successful for /usr/sap/TEH/EHPI/abap/TEH/DVEBMGS15/log/ALMTTREE (0 MTEs).
    Bind service sapgw15 (socket) to port 3315
    GwIRegInitRegInfo: reg_info file /usr/sap/TEH/EHPI/abap/TEH/DVEBMGS15/data/reginfo not found
    GwPrintMyHostAddr: my host addresses are :
      1 : [10.127.0.100] omni.plastekgroup.com (HOSTNAME)
      2 : [127.0.0.1] LOOPBACK (LOCALHOST)
    Full qualified hostname = omni.plastekgroup.com
    DpSysAdmExtCreate: ABAP is active
    DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
    DpIPCInit2: read dp-profile-values from sys_adm_ext
    DpShMCreate: sizeof(wp_adm)##17440#(1744)
    DpShMCreate: sizeof(tm_adm)##4976768#(24760)
    DpShMCreate: sizeof(wp_ca_adm)##56000#(56)
    DpShMCreate: sizeof(appc_ca_adm)#56000#(56)
    DpCommTableSize: max/headSize/ftSize/tableSize=500/16/576048/576064
    DpShMCreate: sizeof(comm_adm)##576064#(1136)
    DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
    DpShMCreate: sizeof(slock_adm)##0#(104)
    DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    DpShMCreate: sizeof(file_adm)##0#(80)
    DpShMCreate: sizeof(vmc_adm)##0#(1856)
    DpShMCreate: sizeof(wall_adm)##(25648/36736/64/104)
    DpShMCreate: sizeof(gw_adm)#48
    DpShMCreate: sizeof(j2ee_adm)#2032
    DpShMCreate: SHM_DP_ADM_KEY##(addr: 700000060000000, size: 5759216)
    DpShMCreate: allocated sys_adm at 700000060000010
    DpShMCreate: allocated wp_adm_list at 700000060002970
    DpShMCreate: allocated wp_adm at 700000060002b60
    DpShMCreate: allocated tm_adm_list at 700000060006f90
    DpShMCreate: allocated tm_adm at 700000060006fe0
    DpShMCreate: allocated appc_ca_adm at 7000000604d3b40
    DpShMCreate: allocated comm_adm at 7000000604e1610
    DpShMCreate: system runs without slock table
    DpShMCreate: system runs without file table
    DpShMCreate: allocated vmc_adm_list at 70000006056e060
    DpShMCreate: system runs without vmc_adm
    DpShMCreate: allocated gw_adm at 70000006056e110
    DpShMCreate: allocated j2ee_adm at 70000006056e150
    DpShMCreate: allocated ca_info at 70000006056e950
    DpCommAttachTable: attached comm table (header=7000000604e1
    MtxInit: -2 0 0
    DpRqQInit: use protect_queue / slots_per_queue 0 / 2001 fro
    Tue Sep 13 14:50:14 2011
    GwDpInit: attached to gw_adm at 70000006056e110
    Tue Sep 13 14:50:16 2011
    DpSetProcessPriority: Run priority for gwrd adjusted to 12

  • Installation problem with SolMan on SUSE 9,0 / Oracle

    Hi Experts,
    I have just started to work with SAP environment. My first challenge is to install Solution Manager on SUSE 9.0 Linux. I have faced quite lot of error messages and managed to solve them with help of support and forum pages. But the last mile seems to be the hardest one. Installation stopped on phase 42 / 45 (Configure System Landscape Directory) with following errors:
    WARNING 2007-02-08 09:18:13
    Execution of the command "/usr/sap/HSM/DVEBMGS01/exe/jlaunch UserCheck.jlaunch com.sap.security.tools.UserCheck /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/lib:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install -c sysnr=01 -c ashost=haukka -c client=001 -c user=DDIC -c XXXXXX -a checkCreate -u SLDDSUSER -p XXXXXX -message_file UserCheck.message" finished with return code 4. Output:
    Warning: tmpfs at /dev/shm is configured quite small with 1956 MB! Minimum value is 2048 MB.
    Recommended size is 75 % of RAM + swap.
    Warning: tmpfs at /dev/shm is configured quite small with 1956 MB! Minimum value is 2048 MB.
    Recommended size is 75 % of RAM + swap.
    Feb 8, 2007 9:18:10 AM   Info: User management tool (com.sap.security.tools.UserCheck) called for action "checkCreate"
    Feb 8, 2007 9:18:11 AM   Error: Exception during execution of the operation
    [EXCEPTION]
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
    Connect_PM  TYPE=A ASHOST=haukka SYSNR=01 GWHOST=haukka GWSERV=sapgw01 PCS=1
    LOCATION    CPIC (TCP/IP) on local host with Unicode
    ERROR       partner 'haukka:sapgw01' not reached
    TIME        Thu Feb  8 09:18:11 2007
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -10
    MODULE      nixxi.cpp
    LINE        2764
    DETAIL      NiPConnect2
    SYSTEM CALL connect
    ERRNO       111
    ERRNO TEXT  Connection refused
    COUNTER     2
         at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:456)
         at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:922)
         at com.sap.mw.jco.JCO$Client.connect(JCO.java:3171)
         at com.sap.security.tools.UserCheck.main(UserCheck.java:172)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Feb 8, 2007 9:18:12 AM   Info: Leaving with return code 4
    INFO 2007-02-08 09:18:13
    Removing file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/dev_UserCheck.
    INFO 2007-02-08 09:18:13
    Removing file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/dev_UserCheck.clone.
    ERROR 2007-02-08 09:18:13
    CJS-30196  Connect to SAP gateway failed
    Connect_PM  TYPE=A ASHOST=haukka SYSNR=01 GWHOST=haukka GWSERV=sapgw01 PCS=1
    LOCATION    CPIC (TCP/IP) on local host with Unicode
    ERROR       partner 'haukka:sapgw01' not reached
    TIME        Thu Feb  8 09:18:11 2007
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -10
    MODULE      nixxi.cpp
    LINE        2764
    DETAIL      NiPConnect2
    SYSTEM CALL connect
    ERRNO       111
    ERRNO TEXT  Connection refused
    COUNTER     2
    ERROR 2007-02-08 09:18:13
    FCO-00011  The step createSLDDSUser with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|5|0|NW_Usage_Types_Configuration_AS|ind|ind|ind|ind|0|0|NW_CONFIG_SLD|ind|ind|ind|ind|0|0|createSLDDSUser was executed with status ERROR .
    I have stopped the installation, rebooted the system and started the installation again. Well that didn’t help at all. After that I have to start Oracle database and listener to proceed with old installation.
    Can you give me any advices how to solve this problem and finish the installation?
    Grateful for help.
    Jukka

    Hi Dolores,
    Thank you for your advices.
    I would appreciate further assistance with this problem because I couldn’t work it out jet.
    I logged in to the Visual Admin by using go file in usr/sap/HSM/DVEBMGS01/j2ee/admin.
    The Visual Administrator screen is opening but I cannot connect in.
    The error message popping up is "Cannot open connection on host xx.yy.xx.yy and port 50004".
    The login parameters specified are:
    Display name: j2ee
    User name: Administrator / (J2EE_ADMIN)
    Host: localhost
    HTTP Port: 50004
    Load balancing method: manual
    Transport layer: default
    I tried with two different username, see above.
    I also tried DDIC user logon via ssh command in Shell console, but didn’t succeed.
    Here is the information in some of those files your mentioned:
    trc file: "dev_rd", trc level: 1, release: "700"
    Wed Jan 31 10:47:35 2007
    ***LOG S00=> GwInitReader, gateway started ( 19402) [gwxxrd.c     1677]
    systemid   387 (Intel x86 with Linux)
    relno      7000
    patchlevel 0
    patchno    46
    intno      20050900
    make:      single threaded, Unicode, optimized
    pid        19402
    gateway runs with dp version 210000(ext=109000) (@(#) DPLIB-INT-VERSION-210000-UC)
    Wed Jan 31 10:47:37 2007
    gw/local_addr : 0.0.0.0
    CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    Wed Jan 31 10:48:05 2007
    Bind service sapgw01 (socket) to port 3301
    Wed Jan 31 10:48:06 2007
    GwPrintMyHostAddr: my host addresses are :
      1 : [192.168.229.131] haukka (HOSTNAME)
      2 : [127.0.0.1] localhost (LOCALHOST)
    Wed Jan 31 10:48:07 2007
    DpSysAdmExtCreate: ABAP is active
    DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
    Wed Jan 31 10:48:57 2007
    DpShMCreate: sizeof(wp_adm)          12744     (1416)
    DpShMCreate: sizeof(tm_adm)          4011160     (19956)
    DpShMCreate: sizeof(wp_ca_adm)          28800     (96)
    DpShMCreate: sizeof(appc_ca_adm)     9600     (96)
    DpCommTableSize: max/headSize/ftSize/tableSize=500/8/520056/520064
    DpShMCreate: sizeof(comm_adm)          520064     (1032)
    DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    DpShMCreate: sizeof(file_adm)          0     (68)
    DpShMCreate: sizeof(vmc_adm)          0     (1596)
    DpShMCreate: sizeof(wall_adm)          (38456/34360/80/184)
    DpShMCreate: sizeof(gw_adm)     48
    DpShMCreate: SHM_DP_ADM_KEY          (addr: 0x457a0000, size: 4663248)
    DpShMCreate: allocated sys_adm at 0x457a0000
    DpShMCreate: allocated wp_adm at 0x457a1e88
    DpShMCreate: allocated tm_adm_list at 0x457a5050
    DpShMCreate: allocated tm_adm at 0x457a5080
    DpShMCreate: allocated appc_ca_adm at 0x45b7f598
    DpShMCreate: allocated comm_adm at 0x45b81b18
    DpShMCreate: system runs without file table
    DpShMCreate: allocated vmc_adm_list at 0x45c00a98
    DpShMCreate: allocated gw_adm at 0x45c00ad8
    DpShMCreate: system runs without vmc_adm
    DpShMCreate: allocated ca_info at 0x45c00b08
    Wed Jan 31 10:48:58 2007
    MtxInit: -2 0 0
    Wed Jan 31 10:49:38 2007
    GwDpInit: attached to gw_adm at 0x45c00ad8
    Wed Jan 31 10:49:39 2007
    ***LOG Q0I=> NiIWrite: writev (32: Broken pipe) [nixxi.cpp 3797]
    ERROR => NiIWrite: SiSendV failed for hdl 1 / sock 12
         (SI_ECONN_BROKEN; UD; ST; 127.0.0.1:0) [nixxi.cpp    3797]
    LOCATION    SAP-Gateway on host haukka / sapgw01
    ERROR       connection to partner 'localhost:0' broken
    TIME        Wed Jan 31 10:49:39 2007
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -6
    MODULE      nixxi.cpp
    LINE        3797
    DETAIL      NiIWrite
    SYSTEM CALL writev
    ERRNO       32
    ERRNO TEXT  Broken pipe
    COUNTER     1
    ERROR => GwIConnectHandle GwWrite failed (NIECONN_BROKEN) [gwxxrd.c     8689]
    C-STACK -
    (CTrcStack2+0x78)[0x80c1938]
    (SigIGenAction+0x2d1)[0x81e9451]
    [0xffffe440]
    trc file: "sapstartsrv.log", trc level: 0, release: "700"
    Thu Feb  8 09:15:05 2007
    <<- ERROR: SapSSLInit(read_profile=1)==SSSLERR_LIB_NOT_FOUND
    SapSSLInit failed => https support disabled
    Webservice thread started, listening on port 50013
    Trusted http connect via Unix domain socket '/tmp/.sapstream50013' enabled.
    trc file: "dev_disp.new", trc level: 1, release: "700"
    sysno      01
    sid        HSM
    systemid   387 (Intel x86 with Linux)
    relno      7000
    patchlevel 0
    patchno    48
    intno      20050900
    make:      single threaded, Unicode, optimized
    pid        19381
    Wed Jan 31 10:48:07 2007
    CCMS: start to initalize 3.X shared alert area (first segment).
    Wed Jan 31 10:48:10 2007
    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 48
    Release check o.K.
    Wed Jan 31 10:49:57 2007
    MBUF state ACTIVE
    Wed Jan 31 10:50:11 2007
    DpModState: change server state from STARTING to ACTIVE
    Wed Jan 31 10:50:18 2007
    WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
    WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
    WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
    WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
    WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
    For some reason the latest files are dated 1.2.2007?
    Hopefully You can see the problem from this log file information.
    As I mentioned earlier I am a green novice at SAP systems and Linux.
    Best regards
    Jukka

  • Installation Of Solman 7.1 aix Oracle failed with Java Error

    Dear All,
    We are doing SOLMAN Installation 7.1 SR1 AIX Oracle.
    Now the installation stopped at the 19th phase "IMport ABAP"as in the attached screenshot.
    OS : AIX 6100-07-02-1150
    Database:  Oracle 11.2.0.3
    Java Version currently maintained:  java version "1.4.2"
    When i checked in log File  import_monitor.java.log  (  /tmp/sapinst_instdir/SOLMAN71/SYSTEM/ORA/CENTRAL/AS) ,
    [root@solmantrg: /tmp/sapinst_instdir/SOLMAN71/SYSTEM/ORA/CENTRAL/AS] cat import_monitor.java.log
    java version "1.6.0_45"
    Java(TM) SE Runtime Environment (build 6.1.051)
    SAP Java Server VM (build 6.1.051 23.5-b02, May 30 2013 05:04:21 - 61_REL - optU - aix ppc64 - 6 - bas2:197575 (mixed mode))
    Required system resources are missing or not available:
      Import directory '/cddumps/Solman_Export_Cds/51042607_1/DATA_UNITS/EXP1' does not exist;
      Import directory '/cddumps/Solman_Export_Cds/51042607_1/DATA_UNITS/EXP2' does not exist;
      Import directory '/cddumps/Solman_Export_Cds/51042607_2/DATA_UNITS/EXP3' does not exist;
      Import directory '/cddumps/Solman_Export_Cds/51042607_2/DATA_UNITS/EXP4' does not exist.
    [root@solmantrg: /tmp/sapinst_instdir/SOLMAN71/SYSTEM/ORA/CENTRAL/AS]
    Also i checked all the above import Directories [
    '/cddumps/Solman_Export_Cds/51042607_1/DATA_UNITS/EXP1'
    '/cddumps/Solman_Export_Cds/51042607_1/DATA_UNITS/EXP2'
    '/cddumps/Solman_Export_Cds/51042607_2/DATA_UNITS/EXP3'
    '/cddumps/Solman_Export_Cds/51042607_2/DATA_UNITS/EXP4'
    ] and all the above import directories are present in my system.
    Later from the above log, i compared the Java Version of our System
    [root@solmantrg: /tmp/sapinst_instdir/SOLMAN71/SYSTEM/ORA/CENTRAL/AS] java -version
    java version "1.4.2"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
    Classic VM (build 1.4.2, J2RE 1.4.2 IBM AIX 5L for PowerPC (64 bit JVM) build caix64142ifx-20110630 (SR13 FP10) (JIT enabled: jitc))
    [root@solmantrg: /tmp/sapinst_instdir/SOLMAN71/SYSTEM/ORA/CENTRAL/AS] which java
    /usr/java14_64/jre/bin/java
    Kindly clarify the below Queries.
    1)Is the above Solman installation error was due to Java version? If so, do we need to install   java version "1.6.0_45" in Solman Server to proceed with the installation.
    2)Cant we proceed the Solman installation with the current Java version (java version "1.4.2") of our System .
    3) What is the actual Prerequistes to be maintained for JAVA.  I have downloaded the Installtion guide from SMP.
    but in the installation guide, The exact java version to be maintained to proceed with the Solman Installation 7.1 SR1 is not mentioned anywhere.
    4)If we install the Java 1.6, do we need to start Solman installation from the scratch . Any reboot required after installing java 1.6?
    5)Because of the inconsistencies in java version in our System, The installation shows the Error " Import directory does not exist  "?
    6)Please tel the cause of the Error
    Kindly assist to proceed with the installation
    Regards,
    Gayathri.K

    Hello Gayathri
    The import_monitor.java.log says the JRE used is 1.6 - java version "1.6.0_45"
    There must be multiple JRE's installed on the system.
    Run the below command and check the output
    ls -lad /usr/java*
    Few things I would try.
    Is the '/cddumps/Solman_Export_Cds/51042607_1/DATA_UNITS/EXP1' an NFS mount ? If yes use a local file system.
    Create a directory called /SMINSTALL and move all from /cddumps/Solman_Export_Cds
    It should look like /SMINSTALL/51042607_1/DATA_UNITS/EXP1
    Start the installation.
    Try to use Java 1.4 or 1.5 and see if that helps.
    You need to set the environment variable JAVA_HOME before starting the installation.
    export JAVA_HOME=/usr/java14_64/jre
    Are there any files/directories under 51042607_*/DATA_UNITS/EXP* ?
    Regards
    RB

  • SOLMAN 7.1 SP10 CRM UI Service Desk - How to clear / remove Message Processor on a particular status

    Hi Experts,
    I have a requirement to remove the stated Message Processor, when the incident / Service Desk ticket is being saved using a particular status (Eg: Sent to Level 1).
    Appreciate if someone can guide me how this can be done (whether using simple PPF (tcode SPPFCADM) or we are forced to use BFR+
    Thanks in advance
    Regards
    Shahul

    The solution is here
    SOLMAN 7.1 CRM UI - "Reported By" Empty
    Thanks to Ash.

  • "Table VSEOPARENT is not in the database" after SolMan system copy to x64

    Hi SDNners,
    We've just completed a system copy of our SolMan 3.1 system onto a new
    (Xeon x64 based) server. This system copy is part of the process of
    moving SolMan 3.1 from an old server onto 64bit hardware and then
    upgrading it to SolMan v4 and Oracle 10G.
    Although the system appears to start properly in the MMC, we are unable
    to log into the system through SAPGUI - we get a SYNTAX_ERROR window
    instead of a logon screen.
    I've checked the SysLog from within the MMC and noticed a number of
    errors stating:
    Database: Table VSEOPARENT is not in the database
    Database: Table VSEOIFIMPL is not in the database
    Database: Table VSEOIFCOMP is not in the database
    I tried running SQL command 'select * from "SAPSOL"."VSEOPARENT"; and
    it confirmed that the table didn't exist. I then ran the same command
    on the source SolMan system and it showed that VSEOPARENT DID exist. I
    don't understand how these VSEO* tables could have gone missing between
    the source and target systems.
    I've searched OSS for VSEO* and cannot find anything. Please help!
    Thanks,
    Arwel.

    We have 640 kernel, ECC 5.0 and BASIS patch 23.
    For me the problem was with SAPVIEW table wasnt imported from source to target becuase SAPVIEW.STR file was 0 byte. STR files gets created in export preparation phase.
    It did happen because on source side master DVD, there was no option for export preparation. I had only option for tablesplit and export db.
    I did use ECC 5.0 SR2 Master DVD which had option for export preparation phase and that created SAPVIEW.STR file.
    Using migration monitor I did re-export and re-import and this time all views are imported in target.
    Regards,
    Mamadi.

Maybe you are looking for

  • Messages are sending as SMS texts instead of iMessages to some contacts

    Hi, I have noticed that a couple of my contacts with iPhones that I would normally iMessage to now I can only SMS text to. It seems that in both cases, previously I received and iMessage from them and when I replied, it failed so I chose to send it a

  • 6.0 release date

    When are they going to release 6.0 for the blackberry tour users?

  • Page content disappears as applet is loaded....

    Hello All, Question 1: I have a webpage where I have a form. I ask user to input a few things in there, and as user press the submit button I pass this information to the embedded applet. However as soon as he presses the submit button, the form disa

  • How do I switch from Home Sharing to my own account?

    I currently share an account with my family but I want to move my iPad to my own account without loosing everything on it. I could really use some help! Thanks

  • Stutter Vocal Effect?

    I was wondering if someone could help me out creating a 'stutter' vocal effect? I know it requires cutting up of the recording track...or something along those lines...a lot of pop/techno tracks are using this progressive stutter effect. Thank you!