Change source system name in variant in BWQ

Hi Gurus,
I created a process chain for global seetings for unit of measurement and fiscal year variants and transported to BWQ.
In BWQ, I found the source system name in variant is showing ERD source system name, but I need to change it to ERQ source system name. Any advice how to change source system name in variant in BWQ I would appreciate it.
Thanks
Liza

Hello Again Liza...
I had the same problem but I didn't need to include in process chain...
So to execute periodically you can change it in debug mode, not the best solution...
But since you need to use it in a process chain, you should copy that program to one of yours Z.
Do this:
Go to transaction se38 and insert the program name "RSIMPCUST".
Click on the button of "Copy" (Ctrl+F5).
Change the source program name to ZRSIMPCUST (or whatever you want)
Click Enter
Click the button to mark everything (F8)
Click Enter
On the next window of the name of the include click enter (leave it blank)
Click on the button Change of your Source Code
In line number 54 you'll find this in Selection Screen part:
PARAMETERS:  logsys  TYPE rsa_logsys MODIF ID p01.
PARAMETERS: logsysnm LIKE tbdlst-stext MODIF ID p02.
Delete those two lines and insert this ones:
PARAMETERS:  logsys  TYPE rsa_logsys.
PARAMETERS: logsysnm LIKE tbdlst-stext.
Now click on Activate button (Ctrl+F3)
Now you have a new program just like the old one but you can change the source system to whatever you want!
Please assign points,
Diogo.

Similar Messages

  • Does not allow to change source system in Variant

    Hi Gurus,
    I am creating a variant for the program RSIMPCUST, but it does not allow me to change source system name. It is showing me gray color. Do you how to fix this issue ?.
    Thanks
    Liza

    Hello Liza,
    Did you try my solution?
    [Re: Change source system name in variant in BWQ]
    There are solutions to change variants properties, but that particular program has the logsys parameter not able to change, so you cannot change the value of that variant (only with debug).
    It's best to go for that solution I already provided to you...
    Diogo.

  • "Conversion of Source System names after the transport" : O

    Experts:
    Environment : BI 7.0 and SP 12
    <b>Tranports related to transformation rules are failing with inactive status...</b>
    Further investigation on this, I have noticed that in our QA system, where "Conversion of Source System names after the transport" : O screen, we have columns
    Original Source System, Target Source System, 7.0, Description(I guess, since no name is found)
    Everything looks fine to me with reference to actual techinical names of source/target system...
    My question there is a check box on column "7.0", which is UNCHECKED. Is this correct?
    My understanding is that, this check box needs to be CHECKED, since this is related " Only Valid for RSDS, TRFN and DTPA Objects ". Is this correct?
    If yes, Can I check this box in QA system, save and retransport my requests. If so, what happens to standard BW objects i.e., transfer ruels, update rules etc...
    OR do i need to create another entry with same source/target system and check the 7.0 box.
    OR do i need to create 3 entries with same source/target system and check 7.0 box for each entry i.e., RSDS, TRFN, DTPA.
    Finally, please advise the exact steps that need to be taken here...pros and cons
    Your inputs will be of great help....
    Thanks,
    BI
    Message was edited by:
            B I

    Hi,
       Yes you need to check the checkbox as it is related to Data sources and transformation and DTPs. you can mark the check box if  your client is modifiable, if not you need to transport the setting from DEV. Go to
    SPRO > Business Intelligence>Transport Settings--> Change Source system name after transport.
    you also need to maintain the Source system IDs .
    Hope it helps.

  • Change Source system Tech.Name

    Production :   PRE -
    >  PRB
    PRE-Production    :   PPE -
    > PRE
    We make a copy of our production BI to Preproduction BI (PPB) we follow note # 886102. We want to connect this system to our pre production ERP (PPE).We already run BDLS change the logical system name we created new RFC created which is pointed to new R3 system .Problem is when we are going to run Tcode RSA1 in source system it shows old Tech name PRE600. We are unable to activate the source system.
    We can create new source system (PPE),but All our BI objects mapped with old source System (PRE600). I am afraid to change thousands of BI objects ( change source system from PRE600 to PPE600).
    Is there any work around we can change the Logical Source system Tech.Name? or some batch job which change the source system name for all BI objects.
    Appreciate your earliest reply.
    Nawab

    Hi
    Can you please check the Tcode BDLS
    Check the document it will be helpful
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bff13df2-0c01-0010-6ba7-bc50346a6fd8
    Regards

  • Changing source system reference

    Hi,
         When I transport from dev to Q, how can I change the source system assignments to Q system? I guess I have to change the assignments as they are referencing dev source system in development and should reference Q when they come to Q.
    Thanks.

    Consider you have BWD, BWQ and BWP and you want to have them loaded from R3D, R3Q and R3p respectively.
    First you need to create R3 source systems in each of the BW systems (and not transport it).
    For steps refer:
    Creating Source System in BW
    Before transporting your rest of the development make sure you have maintained source system mapping.
    If it is not maintained then the same source system name will be used in the target system.
    This can be done via rsa1->tools->mapping source system or transaction RSLGMP
    Lets say your landscape in BWD, BWQ and BWP connected R3D, R3Q and R3P respectively.
    In BWQ create a new entry with values, OrSrceSyste = R3D and TargSrceSy = R3Q
    In BWP create a new entry with values, OrSrceSyste = R3D and TargSrceSy = R3P
    If you are tranporting any datasource of BW sourcesystem (ex: technical content datasources), then
    In BWQ create a new entry with values, OrSrceSyste = BWD and TargSrceSy = BWQ
    In BWP create a new entry with values, OrSrceSyste = BWD and TargSrceSy = BWP

  • Display Source System Name in Process Chain Email

    We would like to show the source system name (QA, Prod, etc) in the email subject when process chain messages are emailed so we can easily discern between production messages and messages from our test system. There doesn't appear to be a straightforward way to do this.
    I have seen a Re: Howto Insert System ID into Process Chain Email Message which discussed this topic and offered 2 potential solutions neither of which work for us:
    1. Open the production system and modify the messsage directly in the production system
    2. Edit the First & Last Name of the sending user in the production system (does not work for us because we use central user administration)
    Can anyone suggest another method of accomplishing this requirement?

    we achieved it by changing text of [email protected] from 'BIWREMOTE' to BIP BIWREMOTE'....so in our mails even though mail id is same, but it display it for us as BIP.
    Just go for user BIWREMOTE, and change format field with whatever name you wanna recieve mail. It should work properly.

  • Conversion of Source system name after transport

    Dear All,
    I need one clarification.
    Say you have developed a fresh modelling in BW Dev server and your source system is R3 dev system. Now you need to transport all the request  to BW Quality system but the source system will be R/3 quality system.
    For this change of source system name we need to maintain some mappings.... From Tools menu there is an option to do this...
    My doubt is in Production server how do we maintain the mapping...
    Quality system ---> Production
    or
    Development system---->Production.
    Hope i am clear....
    Thanks &  Regards,
    Anup

    Hello Anup,
    The question you raised particularly is about the change of source system when your transports are alredy done. For this, i would like to say is that when you do any transports in the R/3 or BW front, the source system change is done only when :
    1. It is done, when you have a single base system and different R/3 (source system)
    2. If you have a single source (R/3) and a single destination (BW Quality), you do not need to map the source system.
    Well, i case that is needed, you may do it via :
    1. Go to RSA1
    2. Go to Tools.
    3. Tools -> Conversion of source system.
    In the right most table column, provide the source system you need to connect with your BW system.
    This will internally connect you with the specified R/3 system.
    Hope it helps!
    Neha.

  • Conversion of source system names

    Hello Experts,
    After having some transport problem (transporting infopackages), I notice that the source system mapping is not the same in DEV compared to PRD.
    Other than change log which was not turned on, is there any other way I can find out who or when was the last change to this mapping table?
    Am I right to say the mapping entries should exist in all systems? My DEV currently only has 1 entry compared to 6 entries in QAS and PRD.
    The source system underwhich the infopackage resides is not shown in the DEV source system mapping table.
    Is this the cause of my transport problem?
    Regards,
    Mirella Russo

    Dear Experts,
    Thanks for the useful information. Points awarded.
    Am I right to say that mapping in target system cannot be transported and is set directly in target system QAS, PRD via RSA1 and no mapping is required even if there are other source systems, like flat file source systems, when the source system name is to be the same in all systems? In this case, my source system is a flatfile. Does this mean I need not maintain it? The 'no mapping' warning received in transport log shows that the flatfile source system concerned exists in the target system but no mapping. As I do not need source system name change, can I say I need not maintain in the mapping table? I still cannot understand why the error come about.
    Many thank you in advance.
    Regards,
    Mirella Russo

  • Change logical system names after system copy

    Hi!
    We successfully installed SAP ECC 6.0 system as system copy.
    All the logical system names of old system have been copied to new system.
    Question
    What is the approach to change the logical system names for new SAP system?
    a) just via tcode SCC4
    b) via BDLS
    c) other tcodes, reports
    Thank you very much!
    regards
    Jürgen

    Hi,
    Go though the system copy guide.
    http://service.sap.com/instguides
    After system copy,
    If you need to change logical system names in the system that results from the copy, change the logical system names as described in SAP Notes 103228 and 544509.
    https://service.sap.com/sap/support/notes/103228
    https://service.sap.com/sap/support/notes/544509
    Before running BDLS to change the logical system name, you have to define the correct logical system name in the new copied system. in tcode BD54.
    - while running BDLS, execute in background.
    Regards,
    Debasis.

  • Conversion of source system names after transport

    Hi gurus,
    Please someone can tell me how to configure the "conversion of source system names after transport"  in the BI system as my transport is not working on a new BI System  ?
    Thx in advance

    Hi Firmin,
    You can do this in RSA1 in tools under conversion of logical source system names.
    Here you maintain the development system or the system used for development as the source system.
    You will have to mention the logical name of the development system.
    In the target system column mention the system in which the transports would be imported. This could be the quality system or the production system.Again you would have to mention the logical system name
    Check the folllowing link for more informationn on this.
    [Conversion of logical names|http://help.sap.com/saphelp_nw70/helpdata/en/46/94b1fc87bd13eae10000000a155369/content.htm]
    Hope it helps you ,
    Best regards,
    Sunmit.

  • Conversion of source system names --- error in transport

    hi
    i want to transport my object from Dev111 to Quality222
    but the transport ended up in error 8
    it gave the error...
    Source system PRODUCTION333 does not exist
    I am confused,
    shouldnot it should give error related to Quality system ???
    how should be the mapping in Source system names?
    after research it seems it should be maintained in
    RSA1-TOOLS-mapping of SOURCE SYSTEM NAMES.
    i have following systems...
    BW- DEV111 QUTY222  PDN333
    R3   DEV121  QUTY242 PDN363
    What should the entries look like in which system

    Landscape is -Transport should be send from Deve-Quality---Production
    BW....................................
    DEV111 QUTY222 PDN333
    R3.....................................
    DEV121 QUTY242 PDN363
    CAN you advise if the entries SHOULD look like below in Quality and Production System???
    Quality system should have entries like:
    bw DEV111.............. bw Quality 222
    r3 DEV121................ bw Quality222
    Production system should have entries like:
    bw Quality222.............. bw Production333
    r3 DEV242................ bw Production333
    Q1 ......IS THIS HOW ENTRIES SHOULD BE IN Quality & Production system???

  • Changing the system Name after Installing EP

    Hi All,
    I need to change the system name of the server and the IP address of the server after EP is installed. Is it possible to do this? Will the EP work properly?
    Regards
    Arun

    Hi Arun,
    There is many reference in the config of the portal to the server name.
    I doubt you will be able to do it without difficulties.
    If you use KM, you will have trouble with internal links in documents. We had to install an apache server for redirection when we migrated/upgraded from EP6 SP2 to 2004s, because the server's name changed.
    Also, you will need to reinstall the local edit activeX to your users.
    I hope someone can answer you better than me.
    There always the system copy option.
    Brad

  • Change Groupwise system name, po name and domain name?

    Hello Board,
    we want to migrate a Groupwise 7 System (Netware) to a Groupwise 8 System (Linux).
    Doesnt sound that difficult, but we dont want to use the names for the system name, the post office and the domain (groupwise domain, _not_ internet domain) which were used on the old system.
    Currently iam trying the way mentioned in TID 10077372, which mentions merging the two systems and then delete the old System.
    Am i on the right way? Do you have any hints?
    Any help appreciated.
    best regards
    sven

    Grewes,
    Ok you have a GW system(s) that you do not like the names and you want to change them. Not a problem. As you stated, and as Tommy said -merging works.
    The process you need is to build a new GW system -same as the version you have running preferred. Set it up as you like it -name-wise. Then, merge the older systems (branches) into the new system you built. Then you will have to build new domains/post offices and move mailboxes from the old GW branches into the new domains/post offices. When its all done -delete the old, and you are done.
    I have done many different variations of this type of migration/merge/consolidation. It works, its just a lot of work. Just make sure to plan it all out on paper first, document it, then go forward.
    Good Luck!
    Take Care.
    Gregg A. Hinchman
    Consultant
    [email protected]
    www.HinchmanConsulting.com
    A Novell Consulting Partner
    317.329.0288 Office
    413.254.2819 eFax
    "Courage is doing what is right."
    "Do not be bound to any doctrine, theory or ideology, even Buddhist ones. All systems of thought are guiding means, not absolute truth." Thich Nhat Hanh, Vietnamese monk.
    Book Travel @: www.booknewtravelnow.com
    >>>
    From: grewes<[email protected]>
    To:novell.support.groupwise.migrations
    Date: 8/20/2009 6:56 AM
    Subject: Re: Change Groupwise system name, po name and domain name?
    Thank you for your reply.
    I do not want to keep the names.
    If i want to link this domain to another branches domain and the domain
    is called the same this doesnt work AFAIK.
    grewes
    grewes's Profile: http://forums.novell.com/member.php?userid=3563
    View this thread: http://forums.novell.com/showthread.php?t=383606

  • Probem after changing the system name of EP 6.0 SP9

    Hi,
    I have changed the system name of the EP 6.0 SP9 system and restarted it and after I again shifted back to the old system name and restarted the system.
    Now the j2ee engine is not coming up ...
    I am placing the developer trace.
    Pl. suggest what might have went wrong.
    Thanks & Regards
    Mrutyunjay
    trc file: "E:\usr\sap\D01\JC00\work\dev_jcontrol", trc level: 1, release: "640"
    node name   : jcontrol
    pid         : 5552
    system name : D01
    system nr.  : 00
    started at  : Mon Dec 19 11:14:46 2005
    arguments   :
        arg[00] : E:\usr\sap\D01\JC00\j2ee\os_libs\jcontrol.exe
        arg[01] : pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
    JStartupReadInstanceProperties: read instance properties [E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties;E:\usr\sap\D01\JC00\SDM\program\config\sdm_jstartup.properties]
    -> ms host    : portald
    -> ms port    : 3601
    -> OS libs    : E:\usr\sap\D01\JC00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
    -> files [01] : E:\usr\sap\D01\JC00\SDM\program\config\sdm_jstartup.properties
    Instance properties
    -> ms host    : portald
    -> ms port    : 3601
    -> os libs    : E:\usr\sap\D01\JC00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID9391400  : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID9391450  : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID9391400            : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
    -> [01] ID9391450            : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
    -> [02] sdm                  : E:\usr\sap\D01\JC00\SDM\program\config\sdm_jstartup.properties
    [Thr 2144] Mon Dec 19 11:14:46 2005
    [Thr 2144] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
    [Thr 2144] [Node: bootstrap] java home is set by profile parameter
         Java Home: c:\j2sdk1.4.2_08
    JStartupIReadSection: read node properties [bootstrap]
    -> node name       : bootstrap
    -> node type       : bootstrap
    -> java path       : c:\j2sdk1.4.2_08
    -> java parameters : -Djco.jarm=1 -Djco.jarm=1
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 128M
    -> root path       : E:\usr\sap\D01\JC00\j2ee\cluster
    -> class path      : .\bootstrap\launcher.jar
    -> OS libs path    : E:\usr\sap\D01\JC00\j2ee\os_libs
    -> main class      : com.sap.engine.offline.OfflineToolStart
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : E:\usr\sap\D01\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0093914
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
    -> arg[02] = -DSAPINFO=D01_00_bootstrap
    -> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=bootstrap
    -> arg[05] = -nodeId=-1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
    -> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_bootstrap.out
    -> arg[08] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_bootstrap.out
    -> arg[09] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_bootstrap
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
    -> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
    -> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
    [Thr 2144] Mon Dec 19 11:14:52 2005
    [Thr 2144] JControlExecuteBootstrap: read instance values after global bootstrap
    JStartupReadInstanceProperties: read instance properties [E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties;E:\usr\sap\D01\JC00\SDM\program\config\sdm_jstartup.properties]
    -> ms host    : portald
    -> ms port    : 3601
    -> OS libs    : E:\usr\sap\D01\JC00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    [Thr 2144] JControlExecuteBootstrap: enumerate the nodes after global bootstrap
    Used property files
    -> files [00] : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
    -> files [01] : E:\usr\sap\D01\JC00\SDM\program\config\sdm_jstartup.properties
    Instance properties
    -> ms host    : portald
    -> ms port    : 3601
    -> os libs    : E:\usr\sap\D01\JC00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID9391400  : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID9391450  : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID9391400            : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
    -> [01] ID9391450            : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
    -> [02] sdm                  : E:\usr\sap\D01\JC00\SDM\program\config\sdm_jstartup.properties
    [Thr 2144] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID9391400]
    [Thr 2144] INFO: Invalid property value [JLaunchParameters/]
    [Thr 2144] [Node: dispatcher bootstrap] java home is set by profile parameter
         Java Home: c:\j2sdk1.4.2_08
    JStartupIReadSection: read node properties [bootstrap_ID9391400]
    -> node name       : dispatcher bootstrap
    -> node type       : bootstrap
    -> java path       : c:\j2sdk1.4.2_08
    -> java parameters : -Djco.jarm=1 -Djco.jarm=1
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 170M
    -> root path       : E:\usr\sap\D01\JC00\j2ee\cluster
    -> class path      : .\bootstrap\launcher.jar
    -> OS libs path    : E:\usr\sap\D01\JC00\j2ee\os_libs
    -> main class      : com.sap.engine.offline.OfflineToolStart
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : E:\usr\sap\D01\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID009391400
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
    -> arg[02] = -DSAPINFO=D01_00_bootstrap
    -> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=bootstrap_ID9391400
    -> arg[05] = -nodeId=-1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
    -> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_bootstrap_ID9391400.out
    -> arg[08] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_bootstrap_ID9391400.out
    -> arg[09] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_bootstrap_ID9391400
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
    -> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
    -> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
    [Thr 2144] Mon Dec 19 11:14:58 2005
    [Thr 2144] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID9391450]
    [Thr 2144] INFO: Invalid property value [JLaunchParameters/]
    [Thr 2144] [Node: server0 bootstrap] java home is set by profile parameter
         Java Home: c:\j2sdk1.4.2_08
    JStartupIReadSection: read node properties [bootstrap_ID9391450]
    -> node name       : server0 bootstrap
    -> node type       : bootstrap
    -> java path       : c:\j2sdk1.4.2_08
    -> java parameters : -Djco.jarm=1 -Djco.jarm=1
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 1024M
    -> root path       : E:\usr\sap\D01\JC00\j2ee\cluster
    -> class path      : .\bootstrap\launcher.jar
    -> OS libs path    : E:\usr\sap\D01\JC00\j2ee\os_libs
    -> main class      : com.sap.engine.offline.OfflineToolStart
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : E:\usr\sap\D01\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID009391450
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
    -> arg[02] = -DSAPINFO=D01_00_bootstrap
    -> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=bootstrap_ID9391450
    -> arg[05] = -nodeId=-1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
    -> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_bootstrap_ID9391450.out
    -> arg[08] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_bootstrap_ID9391450.out
    -> arg[09] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_bootstrap_ID9391450
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
    -> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
    -> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
    [Thr 2144] Mon Dec 19 11:15:05 2005
    [Thr 2144] JControlIBuildProcessList: Maximum error count is set to 4
    [Thr 1424] JControlRequestFunc: Thread 1424 started as listener thread for np messages.
    [Thr 2144] INFO: Invalid property value [JLaunchParameters/]
    [Thr 2144] [Node: dispatcher] java home is set by profile parameter
         Java Home: c:\j2sdk1.4.2_08
    JStartupIReadSection: read node properties [ID9391400]
    -> node name       : dispatcher
    -> node type       : dispatcher
    -> java path       : c:\j2sdk1.4.2_08
    -> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Djco.jarm=1 -XX:NewSize=28m -XX:MaxNewSize=28m -XX:+DisableExplicitGC -Drdbms.driverLocation=D:/oracle/D01/920/jdbc/lib/classes12.jar -Dsys.global.dir=E:/usr/sap/D01/SYS/global/
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 170M
    -> root path       : E:\usr\sap\D01\JC00\j2ee\cluster\dispatcher
    -> class path      : .\bin\boot\boot.jar;.\bin\system\bytecode.jar;.
    -> OS libs path    : E:\usr\sap\D01\JC00\j2ee\os_libs
    -> main class      : com.sap.engine.boot.Start
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : E:\usr\sap\D01\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      :
    -> debuggable      : no
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    [Thr 2144] INFO: Invalid property value [JLaunchParameters/]
    [Thr 2144] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx512M [jstartxx.c   2282]
    [Thr 2144] [Node: server0] java home is set by profile parameter
         Java Home: c:\j2sdk1.4.2_08
    JStartupIReadSection: read node properties [ID9391450]
    -> node name       : server0
    -> node type       : server
    -> java path       : c:\j2sdk1.4.2_08
    -> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:UseParNewGC -XX:MaxNewSize=85M -XX:NewSize=85M -XX:DisableExplicitGC -XX:MaxPermSize=192M -XX:PermSize=192M -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Drdbms.driverLocation=D:/oracle/D01/920/jdbc/lib/classes12.jar -Dsys.global.dir=E:/usr/sap/D01/SYS/global/
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 512M
    -> init heap size  : 512M
    -> root path       : E:\usr\sap\D01\JC00\j2ee\cluster\server0
    -> class path      : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path    : E:\usr\sap\D01\JC00\j2ee\os_libs
    -> main class      : com.sap.engine.boot.Start
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : E:\usr\sap\D01\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      :
    -> debuggable      : no
    -> debug mode      : no
    -> debug port      : 50021
    -> shutdown timeout: 120000
    [Thr 2144] [Node: SDM] java home is set by profile parameter
         Java Home: c:\j2sdk1.4.2_08
    JStartupIReadSection: read node properties [sdm]
    -> node name       : SDM
    -> node type       : sdm
    -> java path       : c:\j2sdk1.4.2_08
    -> java parameters :
    -> java vm version : 1.4.2_08-b03
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 128M
    -> root path       : E:\usr\sap\D01\JC00\SDM\program
    -> class path      : E:\usr\sap\D01\JC00\SDM\program\bin\SDM.jar
    -> OS libs path    : E:\usr\sap\D01\JC00\j2ee\os_libs
    -> main class      : SDMInternal
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : E:\usr\sap\D01\JC00\j2ee\os_libs\jstartup.jar
    -> shutdown class  : com.sap.sdm.jstartup.shutdown.InternalShutDown
    -> parameters      : server sdmhome=E:\usr\sap/D01/JC00/SDM/program
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    [Thr 2144] JControlMSConnect: attached to message server (portald/3601)
    [Thr 892] JControlMSMessageFunc: Thread 892 started as listener thread for ms messages.
    JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
    -> arg[02] = -DSAPINFO=D01_00_dispatcher
    -> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=ID9391400
    -> arg[05] = -nodeId=0
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
    -> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_dispatcher.out
    -> arg[08] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_dispatcher.out
    -> arg[09] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_dispatcher
    -> arg[10] = -mode=JCONTROL
    -> arg[11] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
    -> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
    -> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
    [Thr 2144] JControlICheckProcessList: process dispatcher started (PID:1432)
    JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
    -> arg[02] = -DSAPINFO=D01_00_server
    -> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=ID9391450
    -> arg[05] = -nodeId=1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
    -> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_server0.out
    -> arg[08] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_server0.out
    -> arg[09] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_server0
    -> arg[10] = -mode=JCONTROL
    -> arg[11] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
    -> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
    -> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
    [Thr 2144] JControlICheckProcessList: process server0 started (PID:1436)
    JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
    -> arg[02] = -DSAPINFO=D01_00_sdm
    -> arg[03] = -file=E:\usr\sap\D01\JC00\SDM\program\config\sdm_jstartup.properties
    -> arg[04] = -nodeName=sdm
    -> arg[05] = -nodeId=2
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
    -> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_sdm.out
    -> arg[08] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_sdm.out
    -> arg[09] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_sdm
    -> arg[10] = -mode=JCONTROL
    -> arg[11] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
    -> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
    -> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
    [Thr 2144] JControlICheckProcessList: process SDM started (PID:1452)
    [Thr 892] Mon Dec 19 11:15:35 2005
    [Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
    [Thr 2144] Mon Dec 19 11:16:00 2005
    [Thr 2144] JControlICheckProcessList: process server0 (pid:1436) died (RUN-FLAG)
    [Thr 2144] JControlIResetProcess: reset process server0
    [Thr 2144] JControlIResetProcess: [server0] not running -> increase error count (1)
    JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
    -> arg[02] = -DSAPINFO=D01_00_server
    -> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=ID9391450
    -> arg[05] = -nodeId=1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
    -> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_server0.out
    -> arg[08] = -jvmOutMode=append
    -> arg[09] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_server0.out
    -> arg[10] = -stdOutMode=append
    -> arg[11] = -traceMode=append
    -> arg[12] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_server0
    -> arg[13] = -mode=JCONTROL
    -> arg[14] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
    -> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
    -> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
    [Thr 2144] JControlICheckProcessList: process server0 started (PID:4092)
    [Thr 2144] Mon Dec 19 11:16:40 2005
    [Thr 2144] JControlICheckProcessList: process server0 (pid:4092) died (RUN-FLAG)
    [Thr 2144] JControlIResetProcess: reset process server0
    [Thr 2144] JControlIResetProcess: [server0] not running -> increase error count (2)
    JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
    -> arg[02] = -DSAPINFO=D01_00_server
    -> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=ID9391450
    -> arg[05] = -nodeId=1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
    -> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_server0.out
    -> arg[08] = -jvmOutMode=append
    -> arg[09] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_server0.out
    -> arg[10] = -stdOutMode=append
    -> arg[11] = -traceMode=append
    -> arg[12] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_server0
    -> arg[13] = -mode=JCONTROL
    -> arg[14] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
    -> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
    -> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
    [Thr 2144] JControlICheckProcessList: process server0 started (PID:5456)
    [Thr 2144] Mon Dec 19 11:17:25 2005
    [Thr 2144] JControlICheckProcessList: process server0 (pid:5456) died (RUN-FLAG)
    [Thr 2144] JControlIResetProcess: reset process server0
    [Thr 2144] JControlIResetProcess: [server0] not running -> increase error count (3)
    JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
    -> arg[02] = -DSAPINFO=D01_00_server
    -> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=ID9391450
    -> arg[05] = -nodeId=1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
    -> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_server0.out
    -> arg[08] = -jvmOutMode=append
    -> arg[09] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_server0.out
    -> arg[10] = -stdOutMode=append
    -> arg[11] = -traceMode=append
    -> arg[12] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_server0
    -> arg[13] = -mode=JCONTROL
    -> arg[14] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
    -> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
    -> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
    [Thr 2144] JControlICheckProcessList: process server0 started (PID:4948)
    [Thr 2144] Mon Dec 19 11:18:10 2005
    [Thr 2144] JControlICheckProcessList: process server0 (pid:4948) died (RUN-FLAG)
    [Thr 2144] JControlIResetProcess: reset process server0
    [Thr 2144] JControlIResetProcess: [server0] not running -> increase error count (4)

    Dear Ashutosh,
    Thanks for guiding us to correct location.
    What we identified is we connected portal to the LDAP
    of EP 5.0 while migrating the content.After migration we
    have formatted the 5.0 system.
    Now that portal is connected to that LDAP which is
    not existing the problem is coming.
    Is there any way through CONFIGURATION tool I can remove
    that connectivity to LDAP?
    I am trying to configure LDAP again on the same server
    but before to that if some one can hint me how to
    remove the LDAP configuration from the Portal I would
    be very much thankful..
    regards
    Mrutyunjay

  • Mapping of Source System Names

    Hello,
    Has some body done the mapping of Source System for <b>"Transport"</b> to go through which is done using the following steps:
    RSA1 --> Tools --> Mapping of Source System Names(Conversion of source system name after transport)
    You have to enter the source system name and target source source.
    So if I have following Landscape
    1) R3DEV  -> R3QA --> R3QPROD --> R3Prod
    2) BWDEV  -> BWQA  --> BWQPROD --> BWPROD.
    What should be entries in the table
      OrSource           TargSrceSy
    1) R3DEV             R3QA
    2) R3DEV             R3QPROD
    3) R3DEV             R3Prod
    4) BWDDEV            BWQA
    Thanks,
    -Hari
    5) BWDDEV            BWQPROD
    6) BWDDEV            BWPROD
    or
    1) R3DEV             R3QA
    2) R3QA              R3QPROD
    3) R3QPROD           R3Prod
    4) BWDDEV            BWQA
    5) BWQA              BWQPROD
    6) BWQPROD           BWPROD

    Thanks A.H.P. So just a click clarification. My question is
    So BWQPROD will contian
    <b>OrSource     TargSrceSy</b>
       R3DEV        R3QPROD
    <b>OR</b>  
       R3QA          R3QPROD.
    Because my basis the transport path is as shown below.
       R3DEV --> R3QA
       R3DEV --> R3QRPOD
       R3DEV --> R3PROD
    So dev will transport to QA,QPROD,PROD
    Thanks,
    -Hari

Maybe you are looking for