Deleting aborted support pack

Hi SAP Gurus,
When I was trying to install an application support package in SAP Basis 4.7 EE, it was aborted due to TMS mis configuration and showing RED symbol in SPAM Tcode.  Plz. help me in deleting this aborted package and install it properly.  I configured TMS and tried to install the support pack, but failed in doing so.  Plz. help.

HI
If u not in any phase then simply select display/define and select queue delete.
If u r  in DDIC_ACTIVATION phase u can deleted the entries from PAT01 and PAT03 tables.
Feel free to revert back
Pls provide the points if u get answer.
---venkat.

Similar Messages

  • Roll Back Support Packs

    HI Experts,
    I have applied add-on ST and I want delete it. As of I know I think some of the things needs to be deleted from on table PAT01, PAT03 AND TEPSIN. Unfortunately, I have never done it. So, Can any one help me regarding this with some helpful steps?
    Thanks,
    I will reward points

    Hi Afi,
    With the Support Pack, many objects have been updated or added.
    I assume, that there is no easy way to delete an already implemented support package.
    If it's required, I assume, that you need make a point in time recovery.
    Why do you want the delete the support pack?
    Best regards,
    Ruediger

  • Error in JSPM Support Pack update

    Hi,
    i am in the process of doing java support packs form level 9 to 14.
    I am doing 3 at a time
    After the sap-jee support pack got deployed the server0 for j2ee is not starting.
    Pls hlep
    The following is the log of disp_server0
    trc file: "F:\usr\sap\BWD\DVEBMGS01\work\dev_server0", trc level: 1, release: "700"
    node name   : ID13786450
    pid         : 7296
    system name : BWD
    system nr.  : 01
    started at  : Tue Jun 17 16:30:40 2008
    arguments       :
    *       arg[00] : F:\usr\sap\BWD\DVEBMGS01\exe\jlaunch.exe*
    *       arg[01] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[02] : -DSAPINFO=BWD_01_server*
    *       arg[03] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[04] : -DSAPSTART=1*
    *       arg[05] : -DCONNECT_PORT=3227*
    *       arg[06] : -DSAPSYSTEM=01*
    *       arg[07] : -DSAPSYSTEMNAME=BWD*
    *       arg[08] : -DSAPMYNAME=WDBSSAPBWD01_BWD_01*
    *       arg[09] : -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[10] : -DFRFC_FALLBACK=ON*
    *       arg[11] : -DFRFC_FALLBACK_HOST=localhost*
    [Thr 4660] Tue Jun 17 16:30:40 2008
    *[Thr 4660] *** WARNING => INFO: Unknown property [instance.box.number=BWDDVEBMGS01wdbssapbwd01] [jstartxx.c   841]*
    *[Thr 4660] *** WARNING => INFO: Unknown property [instance.en.host=WDBSSAPBWD01] [jstartxx.c   841]*
    *[Thr 4660] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]*
    *[Thr 4660] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]*
    JStartupReadInstanceProperties: read instance properties [F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties]
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> OS libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Used property files
    -> files [00] : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> os libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID13786400 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID13786450 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID13786400           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] ID13786450           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    [Thr 4660] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 4660] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 6916] JLaunchRequestFunc: Thread 6916 started as listener thread for np messages.
    [Thr 4836] WaitSyncSemThread: Thread 4836 started as semaphore monitor thread.
    [Thr 4660] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 4660] CPIC (version=700.2006.09.13)
    [Thr 4660] [Node: server0] java home is set by profile parameter
    *     Java Home: F:\java*
    [Thr 4660] JStartupICheckFrameworkPackage: can't find framework package F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID13786450]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : F:\java
    -> java parameters    : -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -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 -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
    -> java vm version    : 1.4.2_16-b05
    -> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 1024M
    -> init heap size     : 1024M
    -> root path          : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : F:\usr\sap\BWD\DVEBMGS01\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     : F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50121
    -> shutdown timeout   : 120000
    [Thr 4660] JLaunchISetDebugMode: set debug mode [no]
    [Thr 6772] JLaunchIStartFunc: Thread 6772 started as Java VM thread.
    [Thr 6772] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
    *     Java Parameters: -Xss2m*
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djco.jarm=1
    -> arg[  4]: -XX:MaxPermSize=256M
    -> arg[  5]: -XX:PermSize=256M
    -> arg[  6]: -XX:NewSize=171M
    -> arg[  7]: -XX:MaxNewSize=171M
    -> arg[  8]: -XX:+DisableExplicitGC
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Xloggc:GC.log
    -> arg[ 11]: -XX:+PrintGCDetails
    -> arg[ 12]: -XX:+PrintGCTimeStamps
    -> arg[ 13]: -Djava.awt.headless=true
    -> arg[ 14]: -Dsun.io.useCanonCaches=false
    -> arg[ 15]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 16]: -XX:SurvivorRatio=2
    -> arg[ 17]: -XX:TargetSurvivorRatio=90
    -> arg[ 18]: -Djava.security.policy=./java.policy
    -> arg[ 19]: -Djava.security.egd=file:/dev/urandom
    -> arg[ 20]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[ 21]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[ 22]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[ 23]: -Dstartup.mode=SAFE
    -> arg[ 24]: -Dstartup.action=UPGRADE
    -> arg[ 25]: -Dsys.global.dir=F:\usr\sap\BWD\SYS\global
    -> arg[ 26]: -Dapplication.home=F:\usr\sap\BWD\DVEBMGS01\exe
    -> arg[ 27]: -Djava.class.path=F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 28]: -Djava.library.path=F:\java\jre\bin\server;F:\java\jre\bin;F:\java\bin;F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs;C:\Perl\site\bin;C:\Perl\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;F:\java\bin;F:\usr\sap\BWD\SYS\exe\uc\NTAMD64
    -> arg[ 29]: -Dmemory.manager=1024M
    -> arg[ 30]: -Xmx1024M
    -> arg[ 31]: -Xms1024M
    -> arg[ 32]: -DLoadBalanceRestricted=no
    -> arg[ 33]: -Djstartup.mode=JCONTROL
    -> arg[ 34]: -Djstartup.ownProcessId=7296
    -> arg[ 35]: -Djstartup.ownHardwareId=T1648851106
    -> arg[ 36]: -Djstartup.whoami=server
    -> arg[ 37]: -Djstartup.debuggable=no
    -> arg[ 38]: -Xss2m
    -> arg[ 39]: -DSAPINFO=BWD_01_server
    -> arg[ 40]: -DSAPSTART=1
    -> arg[ 41]: -DCONNECT_PORT=3227
    -> arg[ 42]: -DSAPSYSTEM=01
    -> arg[ 43]: -DSAPSYSTEMNAME=BWD
    -> arg[ 44]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
    -> arg[ 45]: -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01
    -> arg[ 46]: -DFRFC_FALLBACK=ON
    -> arg[ 47]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 48]: -DSAPSTARTUP=1
    -> arg[ 49]: -DSAPSYSTEM=01
    -> arg[ 50]: -DSAPSYSTEMNAME=BWD
    -> arg[ 51]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
    -> arg[ 52]: -DSAPDBHOST=WDBSSDBBWD01
    -> arg[ 53]: -Dj2ee.dbhost=WDBSSDBBWD01
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    [Thr 6772] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 4752] Tue Jun 17 16:30:41 2008
    [Thr 4752] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 4752] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 4752] JLaunchISetClusterId: set cluster id 13786450
    [Thr 4752] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 4752] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 7688] Tue Jun 17 16:30:52 2008
    [Thr 7688] JLaunchIExitJava: exit hook is called (rc = -11113)
    *[Thr 7688] ***********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.*
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'*
    for additional information and trouble shooting.*
    [Thr 7688] JLaunchCloseProgram: good bye (exitcode = -11113)
    trc file: "F:\usr\sap\BWD\DVEBMGS01\work\dev_server0", trc level: 1, release: "700"
    node name   : ID13786450
    pid         : 4560
    system name : BWD
    system nr.  : 01
    started at  : Tue Jun 17 16:30:55 2008
    arguments       :
    *       arg[00] : F:\usr\sap\BWD\DVEBMGS01\exe\jlaunch.exe*
    *       arg[01] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[02] : -DSAPINFO=BWD_01_server*
    *       arg[03] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[04] : -DSAPSTART=1*
    *       arg[05] : -DCONNECT_PORT=3227*
    *       arg[06] : -DSAPSYSTEM=01*
    *       arg[07] : -DSAPSYSTEMNAME=BWD*
    *       arg[08] : -DSAPMYNAME=WDBSSAPBWD01_BWD_01*
    *       arg[09] : -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[10] : -DFRFC_FALLBACK=ON*
    *       arg[11] : -DFRFC_FALLBACK_HOST=localhost*
    [Thr 5300] Tue Jun 17 16:30:55 2008
    *[Thr 5300] *** WARNING => INFO: Unknown property [instance.box.number=BWDDVEBMGS01wdbssapbwd01] [jstartxx.c   841]*
    *[Thr 5300] *** WARNING => INFO: Unknown property [instance.en.host=WDBSSAPBWD01] [jstartxx.c   841]*
    *[Thr 5300] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]*
    *[Thr 5300] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]*
    JStartupReadInstanceProperties: read instance properties [F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties]
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> OS libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Used property files
    -> files [00] : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> os libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID13786400 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID13786450 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID13786400           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] ID13786450           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    [Thr 5300] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 5300] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 7140] JLaunchRequestFunc: Thread 7140 started as listener thread for np messages.
    [Thr 6892] WaitSyncSemThread: Thread 6892 started as semaphore monitor thread.
    [Thr 5300] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 5300] CPIC (version=700.2006.09.13)
    [Thr 5300] [Node: server0] java home is set by profile parameter
    *     Java Home: F:\java*
    [Thr 5300] JStartupICheckFrameworkPackage: can't find framework package F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID13786450]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : F:\java
    -> java parameters    : -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -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 -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
    -> java vm version    : 1.4.2_16-b05
    -> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 1024M
    -> init heap size     : 1024M
    -> root path          : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : F:\usr\sap\BWD\DVEBMGS01\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     : F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50121
    -> shutdown timeout   : 120000
    [Thr 5300] JLaunchISetDebugMode: set debug mode [no]
    [Thr 6352] JLaunchIStartFunc: Thread 6352 started as Java VM thread.
    [Thr 6352] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
    *     Java Parameters: -Xss2m*
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djco.jarm=1
    -> arg[  4]: -XX:MaxPermSize=256M
    -> arg[  5]: -XX:PermSize=256M
    -> arg[  6]: -XX:NewSize=171M
    -> arg[  7]: -XX:MaxNewSize=171M
    -> arg[  8]: -XX:+DisableExplicitGC
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Xloggc:GC.log
    -> arg[ 11]: -XX:+PrintGCDetails
    -> arg[ 12]: -XX:+PrintGCTimeStamps
    -> arg[ 13]: -Djava.awt.headless=true
    -> arg[ 14]: -Dsun.io.useCanonCaches=false
    -> arg[ 15]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 16]: -XX:SurvivorRatio=2
    -> arg[ 17]: -XX:TargetSurvivorRatio=90
    -> arg[ 18]: -Djava.security.policy=./java.policy
    -> arg[ 19]: -Djava.security.egd=file:/dev/urandom
    -> arg[ 20]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[ 21]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[ 22]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[ 23]: -Dstartup.mode=SAFE
    -> arg[ 24]: -Dstartup.action=UPGRADE
    -> arg[ 25]: -Dsys.global.dir=F:\usr\sap\BWD\SYS\global
    -> arg[ 26]: -Dapplication.home=F:\usr\sap\BWD\DVEBMGS01\exe
    -> arg[ 27]: -Djava.class.path=F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 28]: -Djava.library.path=F:\java\jre\bin\server;F:\java\jre\bin;F:\java\bin;F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs;C:\Perl\site\bin;C:\Perl\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;F:\java\bin;F:\usr\sap\BWD\SYS\exe\uc\NTAMD64
    -> arg[ 29]: -Dmemory.manager=1024M
    -> arg[ 30]: -Xmx1024M
    -> arg[ 31]: -Xms1024M
    -> arg[ 32]: -DLoadBalanceRestricted=no
    -> arg[ 33]: -Djstartup.mode=JCONTROL
    -> arg[ 34]: -Djstartup.ownProcessId=4560
    -> arg[ 35]: -Djstartup.ownHardwareId=T1648851106
    -> arg[ 36]: -Djstartup.whoami=server
    -> arg[ 37]: -Djstartup.debuggable=no
    -> arg[ 38]: -Xss2m
    -> arg[ 39]: -DSAPINFO=BWD_01_server
    -> arg[ 40]: -DSAPSTART=1
    -> arg[ 41]: -DCONNECT_PORT=3227
    -> arg[ 42]: -DSAPSYSTEM=01
    -> arg[ 43]: -DSAPSYSTEMNAME=BWD
    -> arg[ 44]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
    -> arg[ 45]: -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01
    -> arg[ 46]: -DFRFC_FALLBACK=ON
    -> arg[ 47]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 48]: -DSAPSTARTUP=1
    -> arg[ 49]: -DSAPSYSTEM=01
    -> arg[ 50]: -DSAPSYSTEMNAME=BWD
    -> arg[ 51]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
    -> arg[ 52]: -DSAPDBHOST=WDBSSDBBWD01
    -> arg[ 53]: -Dj2ee.dbhost=WDBSSDBBWD01
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    [Thr 6352] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 5836] Tue Jun 17 16:30:56 2008
    [Thr 5836] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 5836] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 5836] JLaunchISetClusterId: set cluster id 13786450
    [Thr 5836] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 5836] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 6128] Tue Jun 17 16:31:06 2008
    [Thr 6128] JLaunchIExitJava: exit hook is called (rc = -11113)
    *[Thr 6128] ***********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.*
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'*
    for additional information and trouble shooting.*
    [Thr 6128] JLaunchCloseProgram: good bye (exitcode = -11113)
    trc file: "F:\usr\sap\BWD\DVEBMGS01\work\dev_server0", trc level: 1, release: "700"
    node name   : ID13786450
    pid         : 8152
    system name : BWD
    system nr.  : 01
    started at  : Tue Jun 17 16:31:10 2008
    arguments       :
    *       arg[00] : F:\usr\sap\BWD\DVEBMGS01\exe\jlaunch.exe*
    *       arg[01] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[02] : -DSAPINFO=BWD_01_server*
    *       arg[03] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[04] : -DSAPSTART=1*
    *       arg[05] : -DCONNECT_PORT=3227*
    *       arg[06] : -DSAPSYSTEM=01*
    *       arg[07] : -DSAPSYSTEMNAME=BWD*
    *       arg[08] : -DSAPMYNAME=WDBSSAPBWD01_BWD_01*
    *       arg[09] : -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[10] : -DFRFC_FALLBACK=ON*
    *       arg[11] : -DFRFC_FALLBACK_HOST=localhost*
    [Thr 6468] Tue Jun 17 16:31:10 2008
    *[Thr 6468] *** WARNING => INFO: Unknown property [instance.box.number=BWDDVEBMGS01wdbssapbwd01] [jstartxx.c   841]*
    *[Thr 6468] *** WARNING => INFO: Unknown property [instance.en.host=WDBSSAPBWD01] [jstartxx.c   841]*
    *[Thr 6468] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]*
    *[Thr 6468] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]*
    JStartupReadInstanceProperties: read instance properties [F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties]
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> OS libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Used property files
    -> files [00] : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> os libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID13786400 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID13786450 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID13786400           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] ID13786450           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    [Thr 6468] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 6468] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 7576] JLaunchRequestFunc: Thread 7576 started as listener thread for np messages.
    [Thr 7312] WaitSyncSemThread: Thread 7312 started as semaphore monitor thread.
    [Thr 6468] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 6468] CPIC (version=700.2006.09.13)
    [Thr 6468] [Node: server0] java home is set by profile parameter
    *     Java Home: F:\java*
    [Thr 6468] JStartupICheckFrameworkPackage: can't find framework package F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID13786450]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : F:\java
    -> java parameters    : -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -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 -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
    -> java vm version    : 1.4.2_16-b05
    -> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 1024M
    -> init heap size     : 1024M
    -> root path          : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : F:\usr\sap\BWD\DVEBMGS01\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     : F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50121
    -> shutdown timeout   : 120000
    [Thr 6468] JLaunchISetDebugMode: set debug mode [no]
    [Thr 7456] JLaunchIStartFunc: Thread 7456 started as Java VM thread.
    [Thr 7456] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
    *     Java Parameters: -Xss2m*
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djco.jarm=1
    -> arg[  4]: -XX:MaxPermSize=256M
    -> arg[  5]: -XX:PermSize=256M
    -> arg[  6]: -XX:NewSize=171M
    -> arg[  7]: -XX:MaxNewSize=171M
    -> arg[  8]: -XX:+DisableExplicitGC
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Xloggc:GC.log
    -> arg[ 11]: -XX:+PrintGCDetails
    -> arg[ 12]: -XX:+PrintGCTimeStamps
    -> arg[ 13]: -Djava.awt.headless=true
    -> arg[ 14]: -Dsun.io.useCanonCaches=false
    -> arg[ 15]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 16]: -XX:SurvivorRatio=2
    -> arg[ 17]: -XX:TargetSurvivorRatio=90
    -> arg[ 18]: -Djava.security.policy=./java.policy
    -> arg[ 19]: -Djava.security.egd=file:/dev/urandom
    -> arg[ 20]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[ 21]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[ 22]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[ 23]: -Dstartup.mode=SAFE
    -> arg[ 24]: -Dstartup.action=UPGRADE
    -> arg[ 25]: -Dsys.global.dir=F:\usr\sap\BWD\SYS\global
    -> arg[ 26]: -Dapplication.home=F:\usr\sap\BWD\DVEBMGS01\exe
    -> arg[ 27]: -Djava.class.path=F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 28]: -Djava.library.path=F:\java\jre\bin\server;F:\java\jre\bin;F:\java\bin;F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs;C:\Perl\site\bin;C:\Perl\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;F:\java\bin;F:\usr\sap\BWD\SYS\exe\uc\NTAMD64
    -> arg[ 29]: -Dmemory.manager=1024M
    -> arg[ 30]: -Xmx1024M
    -> arg[ 31]: -Xms1024M
    -> arg[ 32]: -DLoadBalanceRestricted=no
    -> arg[ 33]: -Djstartup.mode=JCONTROL
    -> arg[ 34]: -Djstartup.ownProcessId=8152
    -> arg[ 35]: -Djstartup.ownHardwareId=T1648851106
    -> arg[ 36]: -Djstartup.whoami=server
    -> arg[ 37]: -Djstartup.debuggable=no
    -> arg[ 38]: -Xss2m
    -> arg[ 39]: -DSAPINFO=BWD_01_server
    -> arg[ 40]: -DSAPSTART=1
    -> arg[ 41]: -DCONNECT_PORT=3227
    -> arg[ 42]: -DSAPSYSTEM=01
    -> arg[ 43]: -DSAPSYSTEMNAME=BWD
    -> arg[ 44]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
    -> arg[ 45]: -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01
    -> arg[ 46]: -DFRFC_FALLBACK=ON
    -> arg[ 47]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 48]: -DSAPSTARTUP=1
    -> arg[ 49]: -DSAPSYSTEM=01
    -> arg[ 50]: -DSAPSYSTEMNAME=BWD
    -> arg[ 51]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
    -> arg[ 52]: -DSAPDBHOST=WDBSSDBBWD01
    -> arg[ 53]: -Dj2ee.dbhost=WDBSSDBBWD01
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    [Thr 7456] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 7648] Tue Jun 17 16:31:11 2008
    [Thr 7648] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 7648] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 7648] JLaunchISetClusterId: set cluster id 13786450
    [Thr 7648] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 7648] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 7432] Tue Jun 17 16:31:21 2008
    [Thr 7432] JLaunchIExitJava: exit hook is called (rc = -11113)
    *[Thr 7432] ***********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.*
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'*
    for additional information and trouble shooting.*
    [Thr 7432] JLaunchCloseProgram: good bye (exitcode = -11113)
    trc file: "F:\usr\sap\BWD\DVEBMGS01\work\dev_server0", trc level: 1, release: "700"
    node name   : ID13786450
    pid         : 7280
    system name : BWD
    system nr.  : 01
    started at  : Tue Jun 17 16:31:25 2008
    arguments       :
    *       arg[00] : F:\usr\sap\BWD\DVEBMGS01\exe\jlaunch.exe*
    *       arg[01] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[02] : -DSAPINFO=BWD_01_server*
    *       arg[03] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[04] : -DSAPSTART=1*
    *       arg[05] : -DCONNECT_PORT=3227*
    *       arg[06] : -DSAPSYSTEM=01*
    *       arg[07] : -DSAPSYSTEMNAME=BWD*
    *       arg[08] : -DSAPMYNAME=WDBSSAPBWD01_BWD_01*
    *       arg[09] : -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[10] : -DFRFC_FALLBACK=ON*
    *       arg[11] : -DFRFC_FALLBACK_HOST=localhost*
    [Thr 5400] Tue Jun 17 16:31:25 2008
    *[Thr 5400] *** WARNING => INFO: Unknown property [instance.box.number=BWDDVEBMGS01wdbssapbwd01] [jstartxx.c   841]*
    *[Thr 5400] *** WARNING => INFO: Unknown property [instance.en.host=WDBSSAPBWD01] [jstartxx.c   841]*
    *[Thr 5400] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]*
    *[Thr 5400] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]*
    JStartupReadInstanceProperties: read instance properties [F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties]
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> OS libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Used property files
    -> files [00] : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> os libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID13786400 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID13786450 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID13786400           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] ID13786450           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    [Thr 5400] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 5400] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 4264] WaitSyncSemThread: Thread 4264 started as semaphore monitor thread.
    [Thr 4488] JLaunchRequestFunc: Thread 4488 started as listener thread for np messages.
    [Thr 5400] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 5400] CPIC (version=700.2006.09.13)
    [Thr 5400] [Node: server0] java home is set by profile parameter
    *     Java Home: F:\java*
    [Thr 5400] JStartupICheckFrameworkPackage: can't find framework package F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID13786450]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : F:\java
    -> java parameters    : -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -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 -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
    -> java vm version    : 1.4.2_16-b05
    -> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 1024M
    -> init heap size     : 1024M
    -> root path          : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : F:\usr\sap\BWD\DVEBMGS01\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     : F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50121
    -> shutdown timeout   : 120000
    [Thr 5400] JLaunchISetDebugMode: set debug mode [no]
    [Thr 4872] JLaunchIStartFunc: Thread 4872 started as Java VM thread.
    [Thr 4872] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
    *     Java Parameters: -Xss2m*
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djco.jarm=1
    -> arg[  4]: -XX:MaxPermSize=256M
    -> arg[  5]: -XX:PermSize=256M
    -> arg[  6]: -XX:NewSize=171M
    -> arg[  7]: -XX:MaxNewSize=171M
    -> arg[  8]: -XX:+DisableExplicitGC
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Xloggc:GC.log
    -> arg[ 11]: -XX:+PrintGCDetails
    -> arg[ 12]: -XX:+PrintGCTimeStamps
    -> arg[ 13]: -Djava.awt.headless=true
    -> arg[ 14]: -Dsun.io.useCanonCaches=false
    -> arg[ 15]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 16]: -XX:SurvivorRatio=2
    -> arg[ 17]: -XX:TargetSurvivorRatio=90
    -> arg[ 18]: -Djava.security.policy=./java.policy
    -> arg[ 19]: -Djava.security.egd=file:/dev/urandom
    -> arg[ 20]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[ 21]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[ 22]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[ 23]: -Dstartup.mode=SAFE
    -> arg[ 24]: -Dstartup.action=UPGRADE
    -> arg[ 25]: -Dsys.global.dir=F:\usr\sap\BWD\SYS\global
    -> arg[ 26]: -Dapplication.home=F:\usr\sap\BWD\DVEBMGS01\exe
    -> arg[ 27]: -Djava.class.path=F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 28]: -Djava.library.path=F:\java\jre\bin\server;F:\java\jre\bin;F:\java\bin;F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs;C:\Perl\site\bin;C:\Perl\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;F:\java\bin;F:\usr\sap\BWD\SYS\exe\uc\NTAMD64
    -> arg[ 29]: -Dmemory.manager=1024M
    -> arg[ 30]: -Xmx1024M
    -> arg[ 31]: -Xms1024M
    -> arg[ 32]: -DLoadBalanceRestricted=no
    -> arg[ 33]: -Djstartup.mode=JCONTROL
    -> arg[ 34]: -Djstartup.ownProcessId=7280

    We installed teh objects through SDM .
    this solved the issue

  • Support pack taking more time

    Dear Team,
    When I am applying Basis Support pack KB70010 in my IDES.
    It is executing last 4 hours  in Import Queue
    and bottum side is comming
    EXECUTING OF REPORTS  AFTER PUT.
    What to do Now.
    Manu

    Hi Manu,
    did u saw what I posted in the last note:
    couple of things
    1. in SM50,is the background job doing some actions like updating,deleting or is it stuck up on one action only
    2. I would suggest you to login in 000 and check for all the scheduled and released jobs with R*.
    If they are in released status just start them and I assure you ur support pack will run through
    If these things dont help let me know
    Rohit

  • Web AS 6.4 Support Pack upgrade from stack 9 to stack 10

    Hi,
    Did any one apply support pack from stack 9 to stack 10 for Web AS 6.4, which installed on windows 2003 and Oracle 9.2?
    I got error on step 9 over 19 steps, MUT-02041. In callSdmViaSapinst.log, I found following:
    Apr 19, 2005 3:21:39 PM  Info: SDM configuration: Do not determine state of J2EE Engine now.
    Apr 19, 2005 3:21:39 PM  Info: SDM configuration: Do not save/restore state of J2EE Engine now.
    Apr 19, 2005 3:21:39 PM  Info: Error handling strategy: OnErrorStop
    Apr 19, 2005 3:21:39 PM  Info: Update strategy: UpdateLowerVersions
    Apr 19, 2005 3:21:39 PM  Info: Starting: Update: Selected development component 'keystore'/'sap.com'/'SAP AG'/'6.4010.00.0000.20041222145329.0000' updates currently deployed development component 'keystore'/'sap.com'/'SAP AG'/'6.4009.00.0000.20041117092012.0000'.
    Apr 19, 2005 3:21:39 PM  Info: SDA to be deployed: D:\usr\sap\VDT\JC00\SDM\root\origin\sap.com\keystore\SAP AG\6.4010.00.0000.20041222145329.0000\keystore.sda
    Apr 19, 2005 3:21:39 PM  Info: Software type of SDA: primary-service
    Apr 19, 2005 3:21:39 PM  Info: ***** Begin of SAP J2EE Engine Offline Deployment (Service component of SAP J2EE Engine) *****
    Apr 19, 2005 3:21:40 PM  Info: ***** End of SAP J2EE Engine Offline Deployment (Service component of SAP J2EE Engine) *****
    Apr 19, 2005 3:21:40 PM  Error: Aborted: development component 'keystore'/'sap.com'/'SAP AG'/'6.4010.00.0000.20041222145329.0000':
    Caught exception during deployment from SAP J2EE Engine's offline deploy API:
    com.sap.engine.tools.offlinedeploy.rdb.ODeploymentException: WARNING: Can't deploy component with sda D:\usr\sap\VDT\JC00\SDM\root\origin\sap.com\keystore\SAP AG\6.4010.00.0000.20041222145329.0000\keystore.sda
    com.sap.engine.lib.io.hash.CorruptedHashException
         at com.sap.engine.lib.io.hash.IndexUtils.verifyCRC(IndexUtils.java:73)
         at com.sap.engine.lib.io.hash.MultipleHash.decodeFromByteArray(MultipleHash.java:73)
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineOfflineDeployerImpl.performAction(DeploymentActionTypes).ODEXC)
    Apr 19, 2005 3:21:40 PM  Info: -
    Deployment was successful -
    Apr 19, 2005 3:21:40 PM  Info: Summarizing the deployment results:
    Apr 19, 2005 3:21:40 PM  Error: Admitted: D:\J2EE-RUNT-CD\J2EE-ENG\OFFLINE\SAPJEECOR10_0.SCA
    Apr 19, 2005 3:21:40 PM  Error: Admitted: D:\J2EE-RUNT-CD\J2EE-ENG\OFFLINE\JRFC.SDA
    Apr 19, 2005 3:21:40 PM  Error: Processing error. Return code: 4
    Anybody has a clue how to solve it? Thanks in advance!!

    solved it myself. Re-install J2EE, and re-apply patch again. Everything is good now.

  • DDIC_ACTIVATION Error during application of Support Pack SAPKH47007

    Hi All,
    We were trying to apply Support Pack SAPKH47007 and it gave us an error in DDIC_Activation Phase and when i checked the logs it gave us this error
    Relationship TMFK-TDID for table TTXS does not exist
    Check dependent search help S_TMFK_SETTLE
    Search help S_TMFK_SETTLE is consistent
    I searched and found one Relevant Note for this SAP Note Num : 625098 and it tells us to delete the following fields
    Delete the fields FLG_AK_PAYM_FICA and FLG_AK_PAYM_FIAR from the table
    I went to SE11 and i dont see this fields there, and even though if i see them i dont think i can delete them coz it is asking Developer Key.
    Upon further checking i found that if we delete the Contents in  Pat01 and Pat03 we can go ahead and redo the support packs from begining. Can anyone throw some light on this as to how safe is this?
    Regards,
    Ershad Ahmed.

    Did you read the note I gave you?
    The note says:
    Symptom: An error occurs in the DDIC_ACTIVATION phase when you import Support Package SAPKH47007. The DDIC activation log records the following error messages:
      Relationship TMFK-TDID for table TTXS does not exist
    <...>
    Solution: A general solution to the problem is available with R/3 Support Package SAPKH47010. To avoid the error, import the Support Packages SAPKH47007 and SAPKH47010 together in a queue.
    If you have already encountered this error, the queue must be reset and extended to include Support Package SAPKH47010. Since you cannot reset the queue from the DDIC_ACTIVATION phase using normal means, this must be done by SAP Support (Component BC-UPG-OCS).
    Markus

  • Stuck during applying support pack SAPKB70012

    Hi,
    I am stuck with  applying a support pack level SAPKB70012  in solution manager during IMPORT_PROPER phase.There is no error message displaying rather than simply showing SPAM red status at the screen.Please suggest me for the next course of action.following is the log TP log.
    System Log Entries
    START imp single           SM4        20081124150722              BASIS        MB1ES1012 20081124150721
    INFO  TBATG CONVERSION OF  SM4 N      not needed                  BASIS        MB1ES1012 20081124150721
    START MOVE NAMETABS        SM4 6      20081124150723              BASIS        MB1ES1012 20081124150721
    START tp_getprots          SM4 P      20081124150723              BASIS        MB1ES1012 20081124150721
    STOP  tp_getprots          SM4 P      20081124150724              BASIS        MB1ES1012 20081124150721
    STOP  MOVE NAMETABS        SM4 6      20081124150724              BASIS        MB1ES1012 20081124150721
    START MAIN IMPORT          SM4 I      20081124150724              BASIS        MB1ES1012 20081124150721
    WARNING:
    MB1ES1012\sapmnt\trans\tmp\SAPKKA70012.SM4 is already in use (10), I'm waiting 4 sec (20081124150752). My name: pid 34692
    WARNING:
    MB1ES1012\sapmnt\trans\tmp\SAPKKA70012.SM4 is already in use (20), I'm waiting 1 sec (20081124150816). My name: pid 34692
    WARNING:
    MB1ES1012\sapmnt\trans\tmp\SAPKKA70012.SM4 is already in use (30), I'm waiting 4 sec (20081124150840). My name: pid 34692
    WARNING:
    MB1ES1012\sapmnt\trans\tmp\SAPKKA70012.SM4 is already in use (40), I'm waiting 2 sec (20081124150911). My name: pid 34692

    it seems tranport is hung & inconsistant refer the note below  ...... u need to manually kill the tranport or  kill TP from the OS level and delete *.lob file 
    As per SAP NOTE 12746 - this is the solution for this - The first line of the semaphore file contains the host name of the computer where the tp that reserved that semaphore file is running. First use operating system means to check whether the corresponding tp is still active - for example, whether the process still exists. If the process no longer exists, you can safely delete the semaphore file.
    re-apply the support pack
    Hope this will help you
    Regards
    dEE

  • BW SUPPORT PACK 13,14,15

    hi all,
    can any one give some info and the link where I can find information about BW support pack 13, 14 ,15

    hi ajay,
    i think these oss notes should sufficient, they contain info what error corrected, possible new errors, new features added in the support packages. do you need other info ?
    Symptom
    Support Package 13 for BW Release 3.5.
    Other terms
    SAPBWNEWS, Support Packages for 3.5, BW 3.5, BW 3.50, BW Patches
    Solution
    This note contains the SAPBWNews for Support Package 13 for BW Release 3.5. This note lists all the notes that describe the corrections or enhancements contained in Support Package 13 (SAPKW35013). This note is updated as soon as other notes are added.
    The information is divided into the following areas:
    Manual actions that may be necessary:
    Factors you must take into account when you import the Support Package
    Errors that may occur after you import the Support Package
    For general information:
    This Support Package corrects the following errors
    Enhancements contained in this Support Package
    Support Package 13 for BW 3.5 corresponds to the technological status of Support Packages 28 for BW 3.0B (SAPBWNews 783170) and 22 BW 3.1 Content (SAPBWNews 783252).
    Also see the following release and information notes
    Support Package 13 SAP_UDI 350 Note 765119
    Factors you must take into account when you import the Support Package:
    Note that Support Package 4 is required as of NetWeaver Support Package Stack 14, that is, BW Server Support Package 14 PI_BASIS 2005. For information about upgrading to PI_BASIS 2005, refer to Note 821148.
    Errors that may occur after you import the Support Package:
    Querys on MultiCubes in read mode A. For information about this, read Note 896066.
    Data is missing in individual aggregates.
    The error is not corrected by reconstructing the aggregate. For information about this, read Note 898508.
    When you display a note in the Note Assistant, the following error may occur: 'Output device A000 is not defined'. For more information, see Note 868905.
    Under certain circumstances, the MultiProvider F4 help does not use aggregates that have also been used during the query execution. For more information, see Note 870557.
    When you execute a MultiProvider query, a termination may occur. For more information, see Note 870505.
    When you go from one query to another query or to a Web template, the system fills value variables for compound characteristics, which you can also change during query navigation, with the initial value ("#"). For more information, see Note 867616.
    In certain situations when you execute a query, a termination (GETWA_NOT_ASSIGNED in SAPSRRK0 field symbol <L_S_SNID>) may occur or data may be missing from columns or structural elements. For more information, see Notes 851086 and 848340.
    Some columns or structure items may remain empty in a query. For more information, see Note 863745.
    When you check a query, the system may issue error message Brain A 039 (telling you that node &3 &4 does not exist in hierarchy &2 for the InfoObject &1), although the node exists and you can execute the query. For more information, see Note 855258.
    A query with an exclude in the dynamic filter may not display any data under certain conditions. For more information, see Note 856495.
    In some very exceptional cases, a query may terminate with error message X299(BRAIN) System error in program SAPLRRKH and form SELDER_INTERSECT_BUF-01. For more information, see Note 851754.
    You can execute a query that does not use any key figures even if you do not have the necessary authorizations. For more information, see Note 856144.
    List of notes:
    868905
    870557
    870505
    867616
    851086
    848340
    855258
    856495
    851754
    856144
    This Support Package corrects the following errors:
    Corrections in the end user technology area:
    When you called the filter dialog in the BEx Broadcaster and the ad-hoc Query Designer, the system issued error message CX_SY_REF_IS_INITIAL. For more information, see Note 857393.
    Corrections in the OLAP technology area:
    In a query, some columns or structural elements remained empty. For more information, see Note 848340.
    You were no longer able to create authorizations (profiles) in Transaction RSSM if the user name did not contain a period. The system ignored the authorization assignment using Transaction PFCG (roles) and the generation from ODS. For more information, see Note 849194.
    When you executed a query, the ETWA_NOT_ASSIGNED runtime error occurred in the SAPSRRK0 program in the APPEND_KHANDLE_1 form; field symbol <L_S_SNID>. For more information, see Note 851086.
    When you executed a query, it terminated with the X299(BRAIN) error message telling you that there was a system error in the SAPLRRKH program and the SELDER_INTERSECT_BUF-01- form. For more information, see Note 851754.
    A query that contains both a fixed and dynamic restriction for a characteristic and that is evaluated on a remote cube may terminate (program SAPLRRK0; form CHECK_NAV_INIT_NEW-03- ). For more information, see Note 849969.
    Corrections in the Warehouse Management area:
    After you imported Support Package 12, it took a very long time to create and delete InfoPackages in a content creating BW system because Note 844739 delivered corrections for writing shadow InfoPackages, and these corrections may run for a relatively long time in several source systems that are connected to BW as well as several existing shadow InfoPackages. For more information, see Note 847030.
    When you loaded data, data sometimes disappeared. Refer to Note 849857 for further information.
    If you executed a where-used list for an InfoObject in the D version, a termination sometimes occurred. For more information, see Note 844007.
    When you deleted master data, a termination sometimes occurred. For more information, see Note 856546.
    Enhancements delivered with this Support Package:
    Also refer to the Documentation Enhancements on the SAP Service Marketplace (http://service.sap.com/bi --> Documentation --> SAP BW 3.5 Documentation Enhancements), which describe the enhancements delivered with this Support Package.
    Improvements in the OLAP technology area:
    General performance improvements for OLAP. For more information, see Note 825396.
    The performance of MultiCubes has been improved. For more information, see Notes 869487 and 903559.
    Symptom
    Support Package 14 for BW Release 3.5
    Other terms
    SAPBWNEWS, Support Packages for 3.5, BW 3.5, BW 3.50, BW Patches
    Solution
    This note contains the SAPBWNews for Support Package 14 for BW Release 3.5. It contains a list of all notes that describe the corrections or enhancements in Support Package 14 (SAPKW35014). The note will be updated as soon as other notes are added.
    The information is divided into the following areas:
    Manual activities that may be necessary:
    Factors you must take into account when you import the Support Package
    Errors that may occur after you import the Support Package
    For general information:
    This Support Package corrects the following errors
    Enhancements delivered with this Support Package
    Support Package 14 for BW 3.5 corresponds to the technological status of Support Packages 29 for BW 3.0B (SAPBWNews 783251) and 23 BW 3.1 Content (SAPBWNews 783253).
    Also refer to the following release and information note:
    SP14 SAP_UDI 350 Note 839096
    Factors you must take into account when you import the Support Package:
    Note that as of NetWeaver Support Package Stack 14, that is BW Server Support Package 14, you require PI_BASIS 2005 Support Package 4. For information about upgrading to PI_BASIS 2005, see Note 821148.
    Note 855424 leads to syntax errors during the generation of update rules. Read the note for more information.
    Errors that may occur after you import the Support Package:
    A query displays additional rows or columns. For more information, see Note 901097.
    Querys on MultiCubes in read mode A. For more information, see Note 896066.
    The update from the PSA using the 'Update' indicator in the scheduler no longer works for normal master data that is not flexible and text DataSources that were updated using 'PSA only' - Reason: The problem is caused by the correction that is contained in Note 889160, Note 905105 corrects the problem.
    A syntax error occurs in class CL_RSMD_CONVERSION, method DROP_TMPTABLES. For more information, see Note 905168.
    F4 and authorization: SQL error in SAPLRSDM_F4. For more information, see Note 907337.
    This Support Package corrects the following errors:
    Corrections in the end user technology area:
    When you go from a query to another query or to a Web template, value variables on compound characteristics, which can be changed simultaneously during the query navigation, are filled with the initial value ("#"). For more information, see Note 867616.
    Corrections in the OLAP technology area:
    In certain cases, when you execute a query, a termination (GETWA_NOT_ASSIGNED in the SAPSRRK0 <L_S_SNID> field symbol) occurs or data is missing in columns or structural components. For more information, see Notes 851086 and 848340.
    In certain cases, when you execute a query, a termination occurs and the system issues message X299(BRAIN) 'System error: Program SAPLRRKH; form SELDER_INTERSECT_BUF-01-'. For more information, see Note 851754.
    You can execute a query that does not use any key figures at all even if you do not have the necessary authorizations. For more information, see Note 856144.
    When you check a query, the system may issue error message Brain A 039 (Node &3 &4 is not in hierarchy &2 for InfoObject &1) even though the node exists and you can execute the query. For more information, see Note 855258.
    In certain cases, a query with an exclude in the dynamic filter may not display any data. For more information, see Note 856495.
    In certain cases, the Multiprovider F4 help does not use aggregates that were also used during the query execution. For more information, see Note 870557.
    A termination may occur when you execute a MultiProvider query. For more information, see Note 870505.
    Corrections in the Warehouse Management area:
    The UNCAUGHT_EXCEPTION runtime error occurs during the upload. For more information, see Note 855424.
    Enhancements delivered with this Support Package:
    Also refer to the Documentation Enhancements on the SAP Service Marketplace (http://service.sap.com/bi --> Documentation --> SAP BW 3.5 Documentation Enhancements), which describe the enhancements that are delivered with this Support Package.
    Improvements in the OLAP technology area:
    General performance improvements for OLAP. For more information, see Note 825396.
    The runtime in the REMOVE_SELDR_0INFOPROV_NEW form is very long. For more information, see Note 887801.
    Unnecessary reading of partprovider. For more information, see Note 885733.
    The performance in form SAPLRRK0; loc_rechnen has been improved. For more information, see Note 884482.
    Problems occur with hierarchy selections in MultiProviders. For more information, see Note 879290.
    Query runtime if there are several nested formulas. For more information, see Note 872904.
    Symptom
    Support Package 15 for BW Release 3.5
    Other terms
    SAPBWNEWS, Support Packages for 3.5, BW 3.5, BW 3.50, BW patches
    Solution
    This note contains the SAPBWNews for Support Package 15 for BW Release 3.5. It contains a list of all notes that describe the corrections or enhancements in Support Package 15 (SAPKW35015). The note will be updated as soon as other notes are added.
    The information is divided into the following areas:
    Manual activities that may be necessary:
    Factors you must take into account when you import the Support Package
    Errors that may occur after you import the Support Package
      For general information:
    This Support Package corrects the following errors
    Enhancements delivered with this Support Package
    Support Package 15 for BW 3.5 corresponds to the technological status of Support Packages 30 for BW 3.0B (SAPBWNews 872271) and 24 BW 3.1 Content (SAPBWNews 872273).
    Also refer to the following release and information note:
    Support Package 15 SAP_UDI 350 Note 839097
    Factors you must take into account when you import the Support Package:
    Errors that may occur after you import the Support Package:
    The query displays more rows. For more information about this, see Note 901097.
    This Support Package corrects the following errors:
    Enhancements delivered with this Support Package:
    Also refer to the Documentation Enhancements on the SAP Service Marketplace (http://service.sap.com/bi   > Documentation   > SAP BW 3.5 Documentation Enhancements), which describe the enhancements that are delivered with this Support Package.
    Improvements in the OLAP technology area:
    General performance improvements for OLAP. For more information, see Note 825396.
    Performance improvements when you are searching for filter values. For more information, see Note 900728.
    Performance improvements when you start the query. For more information, see Note 905375.
    Improvements in the Warehouse Management area:
    The system also issues error messages during parallel reading. For more information, see Note 905083.

  • Support pack application - downtime minimized

    Hi,
    We have a large number of support packs to apply, including EhP3, to our ECC 6 system (Currently EhP2).  To minimize downtime during support pack application we want to utilize the downtime minimized method (http://help.sap.com/saphelp_nw04/helpdata/EN/12/5ec33a6e386436e10000000a11402f/content.htm).  One of our concerns is around user session.  Specifically, the person who is doing the SP application and activation may lose connectivity to the SAP system.  We are therefore not sure how to ensure that the activation process is either uninterrupted or can be restarted if connectivity to the SAP system would be lost.
    Please provide your feedback/comments on how you have addressed this or perhaps is it just an education thing.
    Thank you,
    Mike

    Hi Mike,
    If I have understood your concern correctly, triggering SP import to run in background ([Defining Start options|http://help.sap.com/saphelp_nw04/helpdata/EN/12/5ec33a6e386436e10000000a11402f/frameset.htm]) should take care it.
    In any case, if the import gets aborted you can always restart it from SPAM or even [reset the queue|http://help.sap.com/saphelp_nw04/helpdata/EN/a7/a7a932845c11d2b421006094b9ea64/frameset.htm] if you have not crossed the Preparation module.
    -roshan

  • Unwnated files after IMPORT SUPPORT PACKS ..

    Hi Gurus ,
                Kindly let me know how to remove the unwanted files and logs from the \usr\sap\trans folder after IMPORT SUPPORT PACKS .
    Regads
    selvan

    Hi,
    it is better to take a backup of log file before delete that form \usr\sap\trans\log
    file name with sap******.SID contain import log for respective support package,
    you can take backup(for future use in other system) and delete files from \usr\sap\trans\EPS\in folder,
    perform this operation on os level.
    regards,
    kaushal

  • Testing BI's Support Packs

    Hi all,
    We will be implementing BI's Support Packs next month, the question is, what kind of testing do we need to do and do we need to refresh the date coming from ECC? Is there anything else that we need to know specific to BI's support packs?
    The only thing I can think of is we need finish all the extraction which has been performed and clean the queues.
    Thanks all,
    Samer

    Hi Samer,
    I don't think you have to refresh data from ECC because generally the cube/ods tables are not changed. So just keep the data, it's OK.
    What the important is you need to test functionalities. For example, create/modify/delete InfoObject/ODS/Cube/MultiProvider/Query/Workbook/table/structure/program etc, and test load data, delete data ... Because with new support package implemented, such programs are usually updated.
    Also you need to pay attention to the sequence. In my company we first on implement SP on test machine, then develop, and last production. For every machine we do a SGEN and all above tests.
    Hope this helps!
    Regards,
    Frank

  • Support Pack Testing

    Hi all ,
                Can any one share or give their inputs on How the testing should be handled for BW support packs ? Basicaaly the test cases for both BW backend and BW frond end ?
    Any input will be greatly appreciated.

    I generally perform a triage process when looking thru the Notes.  If you haven;t already implemented Hot Fix and High Priority notes, I would review them first.  Then you make a pass through the other Notes:
    - there may be components of BW that you don't use, e.g. SEM, MDX, or maybe notes for certain extractors you don't use.  Those Notes can pretty much be set aside - you shouln't have to do anything else with them.
    - identify any notes that require you to do something as a prerequisite, e.g. perhapss there is an RSADMIN entry you need to make, or some other option that must be set somewhere. 
    - identify any notes that require you to do something to take advantage of a new feature - this is different than the previous group of Notes that were required changes.  These would be broken up into two groups, Notes that sound like they deleiver somehting you really need/want right away, and those Notes that provide features that are less critical.
    - identify the Notes that sound likethey make change that are important to your installation.  
    -  there are Notes that fix really obscure problems that you have not encounted, and thos go into a low priority group.
    - you'll probably have some Notes that require some reseacrh to gauge their impact.
    I think once you have grouped the Notes, you should start to be able to get a feel for what needs a thorough test and review, and what might only warrant a quick check to make sure it still seems to work.
    You'll need to perform basic config testing - can I create/change InfoProviders, InfoObjects, queries etc.
    Test a representative sample of qureies, wkbks - BEx and web.
    Test daily data load preocess which should include all the regular functions such as compression, rollup, change run, etc.
    Test important BW Admin functions that you might not run every day, e.g PSA deletion, RSRV, etc.
    Also review any more recent Notes that have been published for a future SP to make sure there is nothing in them that is of concern.

  • Inits/Deltas during Uprgrades and support packs

    How are people handling the deltas and initializations when upgrades and support packs are applied to the source system. We had to delete our delta queues and reload everything!!! I know that's not right. ( At least I hope that's not right!!!). Please advise...

    Ye s- you should not have to reload targets a a result of an SP/Upgrade.
    When there are changes to the PI_BASIS plugin (extraction from ERP), you need to clear your V3 and Delta queues.
    When SAP Service API (internal and BI Data mart extraction) is changed, you need to clear the BW delta queues.  This can require two complete extraction and laod processes.
    As a matter of practice, we always clear all queues prior to an SP/upgrade.
    See the How to... Checklist: Rapid SAP Netweaver 7.0 BI Technical Upgrade document which is where you can fins this info page 11or 12.

  • Support Pack error in SPAM

    Hi
    I am importing a group of Support Packs into our DEV environment to bring the landscape uptodate, we are running NW04 on Windows 2003 64 bit & SQL Server 2000, I've updated to the latest SPAM and Kernel before the Support Packs.
    When importing in SPAM I have used the calculate queue method, all looks ok, when I perform the import, in the phase TEST IMPORT i get the following error for Support Pack SP 12 for EA-FINSERV 5.00 :
    <b>
    Function MAP2I_BAPICMS_STR_MOV_INS_CRT (CMS_BUSISB104_MAPPI does not fit into the existing function group ((CMS_BUSISB10)</b>
    The only option I am given is to repeat the phase, I've repeated this a few times and get the same error on TEST IMPORT. I'm new to NW04 640 BASIS, but I know from running 4.6X system that you can re-run phases and quite often they work correctly 2nd time round, is it worth changing SPAM to not stop on test import errors ? as I know objects required can be in earlier support packs (i'm applying supports pack EA-FINSERV 5.00 08 to 11 as part of the queue before 12 which is giving me the error.
    I've checked on OSS and cannot find any notes on this error/support pack.
    Thanks.

    nope, not tried with ignore test errors yet, wanted to check opinions here to see if thats the next step to try, or if there's anything else I could try ?

  • Support Pack upgrade error in Import Phase

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

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

Maybe you are looking for

  • I have an unknown shared server in Finder. What is it and how can I get rid of it?

    Hi, I just noticed there is a shared server/ network listed in Finder, but I do not recognise it and cannot connect to it. Could anybody tell me what it is and how I can remove it? Thanks! This is what it looks like:

  • How to decrease the spamming defunct processes by run_service.sh script

    Hi I am running OWB applications. I got a alert showing defunct process are incresed to 40 by the script run_services.sh and now they are increased to 68 -rwxrwxr-x 1 oracle dba 1473 Mar 28 2005 run_service.sh /opt/oracle/products/OWB/owb/bin/unix/ru

  • Hyperlinks in apple mail not working

    Upgaded to Mountain Lion 10.8.2 Build 12C60 and was working fine. Just recently (maybe 2 weeks) all website links in mail just go to my browser Google Chrome Version 23.0.1271.101, they do not open the page. So, I click on the link, it changes to the

  • Price List Update Error through DTW

    Hi Experts,     I am importing Price List in SAP B1 9.0 PL6 but it gives me error "This Entry Already Exist in the following Tables(ODBC-2035) 65171"     I ready on SCN but not get proper solution.     Can anybody can help me... Regards, Sandesh Shin

  • Select Volume when connecting to servers

    I have a workflow I've been running as a start up item to update an excel file on my HD to a server everyday. It works pretty well, I just have one gripe. I have to manually select the server volume when the workflow runs. I also have to click an oka