Support pack objects identified by SPAU
HI,
Can somebody tell me whether we can "set to original" the support pack objects identified by SPAU or not?
How will this impact our testing if the code updates are not fully applied yet?
Thanks & regards,
Pavan.
Hi,
This you have to find out with project team or in project documentation.
If there any changes identified by SPAU, then there must be a reason for that.
You have to analyze that and make a decision if you can change them to standard. You can't just blindly change everything to standard, this can srew up some implemented functionility.
Cheers
Similar Messages
-
Objects are locked in open change requests during support packs update
Hi All,
We are applying support packs in the ECC Dev system. Its giving error in phase OBJECTS LOCKED..? after that i checked with ABAP consultant he given requests which i unlocked the objects from SE03. Still the same error Objects are locked in open change requests is coming.
If i checked requests which are not released, those are in hundreds which we can not release. How can i find a specific object which i need to unlock or any chance to skip the phase and continue. Because 15 days back i have updated the support packs without any of the issue.
Please suggest me whether i can find the specific objects to unlock or any other process.
Thanks & Regards,
Sreekanthsreekanth jd wrote:
Still the same error Objects are locked in open change requests is coming.
>
Hello,
Normally when we double click on that error message 'objects are locked', system takes us to the transport requests containing those objects in question.
And did you try SE03 --> Objects in Requests --> Search for Objects in Requests/Tasks ?
Thanks -
Support Pack Level Upgrade in BI 7.0
Hi all,
Can anyone let me know what are the possible issues that would occur after upgrading support pack level in BI 7.0.
As far as I know a BI consultant would participate in the upgrade activities like BI objects check, SPAU, query check, etc. Can anyone let me know if there are are any other activities to be performed.
I would appreciate your help.
Thanks,
Sunny.Hi
There is any customer specific development done by SAP in the previous system. If so, the time to act is just after the pre upgrade study only. The customer would only want to retain the customer specific module developed by SAP. We need to get SAPu2019s intervention in the project before we start the upgrade. SAP would develop certain patches to be run on the previous system to capture all the customer specific development and then they would run some patches on ECC system u2013 this would release the customer specific development in the new system (ECC./BI). This is a very crucial and important check of the step. If not taken care of at the proper time, it might hamper the Customer Specific development on the new system.
It is to be assured that the new system is at the latest stack level for ABAP, XI, BI etc before we start the SPDD and SPAU phase
Only one request is to be made for SPDD. For SPAU too, only one request should be made.
Previous system sandbox should be available for reference during the entire upgrade project and should not be scrapped before the Go Live.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0c9c8be-346f-2a10-2081-cd99177c1fb9
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/304b9de6-f84f-2b10-94af-e5ff7461c18c
http://www.thespot4sap.com/upgrade_guide_v2.pdf
Hope it helps. -
We recently upgraded from ECC 6.0 support pack 9 to support pack 15. At the same time, we installed EHP4 support pack 5. A few questions:
1. Will we upgrade our ECC 6.0 support pack 15 system to the next support pack, for example to support pack16 or 17, OR will our support packs follow the EHP4 support pack update path, for example upgrading our current environment by moving from EHP4 support pack 5 to support pack 6?
2. We have not yet enabled any of the new EHP4 functions in our landscape. Is it recommended that if we upgrade EHP4 support pack 5 to support pack 6 we do a full integration test? If we haven't enabled any EHP4 support pack 5 functions, I wasn't sure if an integration test was needed.
thank you,
JonathanHello Jonathan,
I hope you are aware of SPDD/SPAU.
Point to be notes is support package will not overwrite your own customizing (Z, Y).
and if you modified any Standard object for your purpose and its been overwritten by the Support package then you will definately get a prompt in SPDD and SPAU and you have a chance to take decision how would you like to go. whether you want to keep your customizing to the standard objects or you want the new standard code to overwrite it.
So, you will not need to do integration testing for complete things in your system.
Let me know if you need more clarifications.
Best Regards
Niraj -
Issue while apply support pack SAP_BASIS SAPKB70013 -18
Hi Gurus,
We have issue while apply support pack to Development system, we have implemented SAPKB70012 pack first and then we have implemented SPAU and saved in Trasport request . while applying other patch SAPKB70013 -18 in one go system asked us to release SPAU transport and then we released that transport after that same transport with auotomatic job it has got implemneted to Quality system and then after that we got below error in quality system :-
The function module "EXTENDED_AUTH_CHECK_FOR_REPS" is called, but
cannot be found in its function group.
Error in the ABAP Application Program
The current ABAP program "SAPLS38E" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Please suggest now both system is not working .
Regards,
JeetendraAlso you can check object modifications in transaction SE03 looking for request that touched object SAPLS38E.
Could you please share the syntax error message ?
Best regards -
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 ?
-
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=7280We installed teh objects through SDM .
this solved the issue -
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 ConsultantHi,
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 -
Open data extraction orders - Applying Support Packs
Dear All,
I have done the IDES 4.6C SR2 installation.
While updating the support packs, i get the message saying
CHECK_REQUIREMENTS phase.
Open data extraction orders
There are still open data extraction orders in the system
process these before the start of the object import because changes to the ABAP Dictionary structures could lead to data extraction orders not being able to be read after the import and their processing terminating
For more details about this problem, see Note 328181.
Go to the Customizing cockpit for data extraction and start the processing of all open extraction orders.
I have checked the Note.
But this is something m facing for the first time.
Any suggestion!!!
Rgds,
NKThe exact message is :
Phase CHECK_REQUIREMENTS: Explanation of the Errors
Open Data Extraction Requests
The system has found a number of open data extraction requests. These
should be processed before starting the object import process, as
changes to DDIC structures could prevent data extraction requests from
being read after the import, thus causing them to terminate. You can
find more information about this problem in SAP Note 328181.
Call the Customizing Cockpit data extraction transaction and process all
open extraction requests. -
Problem with object view with primary-key based object identifier
Hello!
I met such problem.
t1 is persinstent-capable class:
class t1 : public PObject { .... };
T1OV is object view, based on object table T1OT
I1 is primary key of the table T1OT.
Next code:
t1* t = new (conn, "T1OV") t1(...);
conn->commit();
try
t->markDelete();
conn->commit(); // exception throws here
Works fine if T1OV defined as:
create view t1ov of t1 with object identifier default
as select * from t1ot;
And throws an exception
"ORA-22883: object deletion failed"
if:
create view t1ov of t1 with object identifier (I1)
as select * from t1ot;
Such problem also occurs when object view is based on relational table/view (OID is primary-key based).
Also it occurs when
t->markModified() used insted of t->markDelete()
I am using Oracle 9i second release for windows and
MS VC++
Thank Youhttp://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96540/statements_85a.htm#2065512
You can specify constraints on views and object views. You define the constraint at the view level using the out_of_line_constraint clause. You define the constraint as part of column or attribute specification using the inline_constraint clause after the appropriate alias.
Oracle does not enforce view constraints. However, operations on views are subject to the integrity constraints defined on the underlying base tables. This means that you can enforce constraints on views through constraints on base tables.
Restrictions on View Constraints
View constraints are a subset of table constraints and are subject to the following restrictions:
You can specify only unique, primary key, and foreign key constraints on views. However, you can define the view using the WITH CHECK OPTION clause, which is equivalent to specifying a check constraint for the view.
Because view constraints are not enforced directly, you cannot specify INITIALLY DEFERRED or DEFERRABLE.
View constraints are supported only in DISABLE NOVALIDATE mode. You must specify the keywords DISABLE NOVALIDATE when you declare the view constraint, and you cannot specify any other mode.
You cannot specify the using_index_clause, the exceptions_clause clause, or the ON DELETE clause of the references_clause.
You cannot define view constraints on attributes of an object column.
Rgds. -
Hello Support,
I have CRM 2005 in my landscape.It has the following patch level.
for ABAP stack it is at Stack 8
for JAVA stak it is at Stack 4.
And we are going for both (ABAP and JAVA) to STACK 15 which is latest.
I have the following query
1.) Can i directlly upgrade the JAVA stack from 4 to 15. Since i guess the present stack is too low.
Will we face any issue in doing so. What is the general practise?.
2.) For the ABAP stack , can i put the whole stack from 9 to 15 in the queue at a time or do one stack at a time.
Example
first upgrade it to 9 then 10 and so on
or directly in one queue to 15, so that we can have only one SPDD and SPAU.
3.) what is the main SNOTE for the CRM support pack.
4.) What all pre-requisite are ther perticulary for the CRM support packs.
Regards
AnthonyHi mohit ,
Thanks for the reply ..
Yes , i will try convicing the client for going to latest -1 patches.
Now you have suggest that we must go for the ABAP to first SP12 and then to the latest -1.
I have the following query regarding this.
1.) How should i go to SP12 stack.
a.) by directly adding all the stacks till 12 in one go. (that is starting the queue from stack 8 to 12 ).
b.) going one stack at a time (i.e first will bring it to stack 9 then 10 then 11 and then 12)
c.) going component wise ( eg , first the BASIS till 12 , then the ABAP , then BW and so on.)
Regards
Anthony -
BSP application not being pulled after the application of support packs
Hi all,
Support packs SP 35-42 were applied last week end and after that one of the three BSP applications in production server is not being pulled through SAP gui. If I take the URL and paste it in IE the same application is being pulled. We are suspecting that to be a web dispature issue or firewall issue. The land scape is like this. P20 is our production server and C20 is our QA server.P20 has Sun109 as a web dispature and C20 has Sun108 as webdispature. There is a firewall in between P20 and Sun 109 but there is no firewall in between C20 and Sun 108. We redirected P20 to Sun 108 to test and all the three applications pulled up. so we concluded that it could be an issue with SUN 109 or a firewall issue. I am new to this webdispature stuff. I need help in identifying which files I have to look in to identify any kind of such errors. it is confusing why other two applications are being pulled and only one is not being pulled into SAP gui. We debugged the code and every thing is working fine. this is an urgent issue to be resolved.These application were developed long back and the developer did not leave any documentation how the hand shake is done between the web dispature and the SAP system.We are supporting the production system now. I appreciate any one responding as soon as posible.
Thank you very much,
GiriYou mustn't have looked very hard.
Try https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=954792 as a starter. -
PI System Support Pack Upgraded from 04 to 07
Hi Guys,
In PI system basis people upgraded support pack 04 to 07.
how i will check the PI system functionality after upgrading support package 04 to 07...
first basis people upgrated in PI Development system. after they will do in PI Quality and PI Production.
is there any effect on PI existing interfaces once it comes to live system production..
can any one please help me on this.
Thanks,
Siva.first basis people upgrated in PI Development system. after they will do in PI Quality and PI Production.
is there any effect on PI existing interfaces once it comes to live system production..
backward compatibility is provided so if you upgrade a SP then your existing interfaces will continue to run without any issue/ modification.
The only thing that you need to take care is that all your environments (DEV, QA, PROD) should be on same level so that transport of objects is not affected. -
Anywhere to find newly added countries in enhancement pack and support pack
Our HR wants to proactively identify the new countries being introduced through enhancement pack and support pack, so configurations such as V_T503Z (country assignment for employee group/subgroup) can be updated accordingly.
How can I find such a list?
Thanks.
JoanHi Qiong
If you have ever tried downloading the notes delivered under CLC or HRSP for SAP-HR Component, you would see that the sub-component names are generally based on country abbreviations example PY-AU, PY-SG etc. Also the country names are mentioned there. So if any new country comes up you would know it from the sub-component name. However, whether you need to configure anything in your system for these new countries depends on the fact whether your client has operations in that country or not and whether your project is supporting that country operations for the client or not.
It is more likely that we keep checking the CLC and HRSP for any new functionalities introduced by SAP for the countries that we are supporting for the client instead of checking for new countries altogether. -
Hi All,
Is there a difference between Service Pack and Support Pack ?
Thanks,
PrashanthHi,
I think. This are synonyms.
Microsoft takes the name ServicePack.
In SAP there are same objects to changes the system:
note: to correct one program. to correct one mistake.
support package: change a list programs.
support package stack: group of patches for all software components. SAP tests this combination of corrections intensive.
Sven
Maybe you are looking for
-
I suddenly have one bookmark missing...only one! which just so happens to be the one containing all the research I am currently working on. And it contains months and months of compiled data, websites, etc...WHICH IS needed to finish my project. was
-
File Adapter - Debatching & ChunkedRead
Hi , Can anybody please tell me what is the difference between File Debatching & ChunkedRead in File Adapter . How the error handling mechanism differs in these two . Thanks in Advance .. Regards, Surfraz
-
Where is the file menu on Itunes for PCs?
I just did the latest itunes update and I can't find any menus...I see my songs and apps, but where is View, File, etc? I want to be able to choose what songs are on my iphone but it doesn't show up anywhere so I have to keep plugging it in and unpl
-
Hi All, I have the following doubt in assessment cycle :- Consider the following scenario. There are three cost centres :- D015, D020 and D025 . An assessment cycle is being created where D015 is the sender and D020, D025 are the receivers . A cost
-
Error while executing logical data service:XP0006
Hi, <br><br> I have one physical dataservice which is caps.ds based on oracle database. I created one method in caps.ds by name gatCap(String param). basically this method will fetch the data from the database based on input parameter. This method is