Change Receiving System Name in BD64

Hi folks,
               We have our production instance and QA instance; we have copied all data from Production to QA ENV (Client Copy). After that when I login in to QA system I saw in BD64 all the system pointing to receiving production system. I  ran  BDLS ( transaction ) which convert production logical system name to QA logical system name in tables and as well as in SCC4 transaction.
I again went to BD64 and I noticed after running BDLS my production system name replace to QA system name. But Receiving systems names are still pointing to production systems. I know that BDLS just change the sending system logical name not receiving.
My question is that how I can change or modify the receiving system production names to testing name. Is there any way or program?
I try to change the receiving system name but it’s not letting me change. You guys have any idea how to change the receiving system production name to test name.
I don’t want to create all distribution model names with test systems as I have 30 distribution models and client copy is keep on going after every 1 or 2 months.
Please help me in this regards.
Thanks

The OSS notes just tell about the BDLS. I already done with BDLS… Scenarios is like that say we have one distribution model name in Production
Model name = ZXYZ
(Sender system) Production system name = PRD_123
(Receiving production System in UK)      = PRD_UK
These above are the setting for Production client.
We copy data from Production to Quality, so its copy all the data and Distribution name in QA ENV…
So now my QA looks like
Model name = ZXYZ
Sender system) Production system name = PRD_123
Receiving production System in UK)      = PRD_UK
After that I ran T-code BDLS and give logical system name = QA_123, then when I go back to BD64 the model is looks like following
Model name = ZXYZ
Sender system) Production system name = QA_123
Receiving production System in UK)      = <b>PRD_UK </b>
But PRD_UK isn’t change because it’s the production system for receiving one , so Now I need to modify <b>PRD_UK to QA_UK in BD64</b> , How I’ll do it ?
I am trying to change receiving system but it doesn’t allowing me.
I hope, now I made my self more clear.
Thanks in Advanced.
Bye
Message was edited by: Suleman Javed

Similar Messages

  • 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

  • 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.

  • 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.

  • 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

  • How to change logical system name

    hi,
    there is no logical system name for business system in sld on integration tab.
    this bus sys is based on tech sys which is configured as integration server.
    plz tell me how to give the logical sys name there.
    plz reply me it is urgent.
    vijender

    Jochen Gugel wrote:
    > Hi @ll;
    >
    > at the tab in technical system the logical system name was correct.
    > But it wasn´t shown at the integration tab of the business system.
    > I solved this problem by deselecting the integration server, save this settings and reselect it afterwards.
    >
    > Kind regards
    > Jochen
    hello all,
    I'm actually having the same issue.  This issue is NOT the popular adapter-specific identifier problem where the business system in the ID needs to be compared with the SLD.  This issue is that the within the SLD on PI 7.0 the Logical System Name of a given business system is not present although the logical system name of the specified technical system does appear.  You cannot change the LSN of the business system since it relies completely on the LSN of the associated technical system.
    I used Jochen's approach before and it worked, but i've tried this again since i'm having the same issue.  Only now it doesn't work.
      i solved this issue by deleting the old BS and recreating it
    Thanks,
    Edited by: Jason Ray on Jun 24, 2008 5:47 PM

  • Changing Logical System Names

    Currently, each instance(SID) in an entire landscape all have the same logical system name and the RFC name that corresponds is all the same.  You really don't know what system the RFC is pointing to until you open it up and see which server, etc. is listed in the RFC.  So, we are working on a project so that each instance has it's own unique logical system name.  The biggest problem we are concerned about is making sure that we change all the places where these definitions exist.  I have a small list of transactions that need these items changed (SM59, SALE, SCC4, RSA1, SMQR, SMQS, SBIW, SPRO (this is a tough one)).  We realize we will depend on our application teams heavily to know where they changed any configuration to use logical systems.  My question is to see if anybody has done this type of change, if they have any tips/guidance, to see if anybody can give some good direction on where to find all the places these LS names are used, and if anybody else can throw out any other transaction suggestions that we should check.  Thanks in advance.
    -Marsha

    Marsha,
    I think you should examine the reasons why it would not work before asking if you can do it.  One reason for us was archiving.  We regularly archive off data only keeping the last 3-7 years of data in the system for some tables.  Changing the logical system ID for us would mean it would be impossible to reload some of that archived data, without customizing or a new development effort.
    So if your questions is can you do it?  Yes, you can do it. 
    If the question is should you do it?  .....Well, then you need to examine why or why not in your own environment.  There are likely to be pitfalls especially if its usage is widespread at your company as you indicate.
    -jwise

  • Changing logical system name on ECC

    Hi,
    We have made copy of production to our test environment.  Next, we created a number of copies of the test environment.  We now want to hook the copies up to BI, XI etc. where we don't have multiple test environments, which means that a single BI test instance will support several ECC test instances as an example.  This means that our ECC instances will have to have their logical system name changes changed in addition to the obvious SID change.  We have a fairly comprehensive landscape with GRC, XRPM, BI, SolMan, CRM connected to our ECC instance.  What areas of concern would you consider important to test once the logical system name changes are done?  We are looking at the ALE, RFC connections, BI connections.  We included the [help.sap.com information |http://help.sap.com/saphelp_nw04/helpdata/en/33/c823dbaea911d6b29500508b6b8a93/content.htm] in our thinking, but since that did not really explore landscape wide issues....
    Thank you,
    Mike

    Hi
    As prelim checks:
    Check if these changes are maintained in SCC4 client details as well, and check if all the RFCs are working fine.
    Regards
    Rahul

  • How to transfer a module between systems and change the system name?

    Hello,
    I would like to transfer a module I've built from one server to another, my questions are:
    1. What will be the best way to do it?
    2. The 2nd Server contains a System with the same queries but the system has a different alias. Suppose I don't want to add to the system and the 2nd server the alias from the 1st system, is it possible to change the system in the module queries once it has been compiled and deployed?
    Roy

    Hi,
    1) You can use the export/import features of VC to transfer models.
    2) The requirement is not clear. I guess your alias name is different in the second system and you want the imported model to work fine with the current alias in second system.
    To change the alias, goto Menu Tools ->Alias manager, select your system and replace it with the new alias. Then compile and deploy it.
    Hope it helps
    Regards,
    Sooraj

  • Change business systems name

    Hello,
    I am sure this question has already been asked but I can't find anything in the forums...
    We have PI 7.0 SP13, and I would like to know if there is a way of renaming a business system without deleting/recreating it ?
    Many thanks for your help,
    Best regards,
    GL

    Guislain,
    Do you want to re-name the Logical System name or Business System name?
    raj.

  • Logical system name change

    Hi all,
    Now my BI development is pointing to R/3 development. R/3 logical sytem name is bbbclnt100. Now all my datasources are pointing to this logical system. Our basis people are going to change the logical system of R/3. Please tell me the repercussions? what will happen to my datasources?
    Thanks in advance

    Anni,
    Change logical system name and run BDLS job to adjust. Do not change souce system. If you change source system all transfer rules will get deactivated.
    Check: [Conversion of Logical Systems|http://help.sap.com/saphelp_nw70/helpdata/en/33/c823dbaea911d6b29500508b6b8a93/frameset.htm]
    Search forum for more links.
    Srini

  • Logical system name has been changed for this system

    Hi gurus,
    I am fasing problem in BI7 system. we created a new client in the system & want to set it for BI development.
    System Response
    The transaction is canceled.
    Procedure
    Change the name of the logical system (table T000) for client  back to BID500. This enables you to continue working with the system.
    If you really want to change the logical name, than you can, if and when you:
    change the system name back to BID500,
    delete all existing connections between this system and other systems,
    delete all transfer structures that still exist, and
    do not use ALE or Workflow.
    Regards,
    Darshan..

    Sorry, BI is a one client system. You cannot have a prod client and a dev client within one SAP system.
    But...
    ...NO, you can't!
    Best regards
    Michael
    EDIT: just to add, there is an exception if you have a SCM/APO type system [522569 - BW: Working in several clients (especially APO 4.x/SCM 4.x)|https://service.sap.com/sap/bc/bsp/spn/sapnotes/index2.htm?numm=522569]

  • Can the system name of the Fabric Interconnects be changed

    I need to change the system name of the Fabric interconnects
    I have given eg. EDCD
    the FI now have EDCD-A
    EDCD-B
    I need to change it to ... ECCD-A
    ECCD-B..
    is it possible ?

    Shyam,
    You can definitely do it and for sure is not disruptive and take effect right away.    Just go to the Admin tab> All> Management Interfaces> Name > Edit it with what you need > Apply.
    It is so easy and fast that if at the same time you have an SSH session, as soon as you change the name, the system makes the change on your SSH session too.
    Note: There is no need to look for the way to do this on each fabric. The name you are changing is for both FIs and the system will then add the xya-A or xya-B by itself.
    Rate ALL helpful answers.
    -Kenny

  • Changing system name in copied function

    Hi Guys, I have copied a bunch of functions, however the system is not allowing me to change the System Name in Actions tab.
    Can anyone help?
    Thanks

    First and foremost: I'd say this is not right - please open a customer message.
    I'm guessing what you want to do is have the same TCodes and Objects used in risk analysis for  a new system you're adding.
    If this is the case, copying the function is not the right approach. You's either do that by adding the TCodes for the new system to the existing function, or - MUCH better - use a logical system and just add the new system there.
    Copying a function may be useful for building organizational risks, i.e. risks&funktions that have a direct link to a certain part in the organization.
    Frank.

Maybe you are looking for

  • ADOBE FLASH

    how do i download and install adobe flash player? every page i go to says i cannot proceed without adobe flash player and i have tried for hours to do it . i am on a h p windows 8 laptop. h e l p .

  • How do i stop i tunes opening and duplicating everything i want to play please

    Every time i try to play a song that is either stored on my MacBook air  ( mid 2011, still on Lion ) or i try to access it from a drive, if i click twice by accident i tunes opens and duplicates the song. That is really annoying. I do not want i tune

  • How to build online help for froms

    dear colleague, i need to build an on online help based on word file, meanwhile i need to facilate the search ability in this help and table of content also, can anyone help in how to devlope this function??

  • Problem releasing workbench transports

    We had created a number of changelists in our workbench and are trying to release these to transport them into out test system.  When we release the transports which are created without issue in the development workbench we get the following message:

  • Transferring images out of Aperture library

    I recently acquired Aperture and plan to import my existing library into the Aperture library. My existing library consists of a lot of .nefs and almost as many jpgs. Once my existing library is imported I plan to let Aperture manage and backup the i