hi community,

when installing a new printer in SPAD the hostname of the backup network shows up in GUI.

Which means the field "Host" shows the servers backup network hostname. The backup network has its own IP range and is not routed to any other network. How can I force SAP to use the correct hostname?

I believe this happens because the backup hostname starts with the letter 's' rather than the 'original' hostname starting with 'v'.

Cheers,

Helmut

Hi,

I want to understand in which phase of the SPS Update of SAP NW 7.4 , do i need to ask developers to go to SPDD and SPAU tcodes and make adjustments. I read the SUM Guide and there are two places where we can do , one in the "CONFIGURATION" Phase where it gives us two check boxes to enter the Transport number for SPDD & SPAU, do I ask developer at this stage to goto SPDD and SPAU tcode to adjust objects or should I ask them in "PREPROCESSING" Road map step?

In "PREPROCESSING" Road map step we have 2 sub phases: 

1) SPAU Fill Level Display (Phase PREP_PARSETUP/SPAU_FILL_LEVEL_DEC)

2) Automatic Reset of Non-Adjusted Repository Objects to SAP Original Version (Phase RUN_SUM_SPDD_RESET_CANDIDATES or RUN_SUM_SPDD_RESET_CANDIDATES_TRANS)

Phase answer as to in which step should the developer go and adjust the objects in SPDD and SPAU and capture to the Transport request?

This update is in Dev System.

Best Regards!.

SAU

Hello All,

I'm trying to prepare a query to UME_STRINGS table to find users that are not locked in NetWeaver. I check field ATTR for islocked parameter and then according to the value of this parameter (true or false) I know if the status of user's acount.

Unfortunatelly I've found an example of account that has islocked set to true, but when I check the same account in NetWeaver, it is not locked. I wander why database and NetWeaver UI show different values.

Do you have any idea?

1. Check if ADS User is set to technical and whether it has expired or not. (This user is used for basic authentication in the Java Environment)

2. Check if ConfigPort_Document has been correctly created under SOA Management -> Technical Configuration à Destination Template Management

If the Destination “ConfigPort_Document” is missing or the user has been expired you will get the following error in the Log Viewer:

  handleCommunicationError( ErrorContextData, Throwable, TransitionTicket ): A technical error occurred.
Interface namespace = <Name>
Interface name = <Name>
Operation name = <Name>
Connectivity type = WS
Application name = <Name>
Reference name = fdfbcb99-232c-4e27-8811-31d2ddfc84c3
Message Id = null
WS style = DOC
Start time of WS call = 2015-07-30 13:56:03.972
Return time of WS call = 2015-07-30 13:56:04.172
Principal name = SAP_BPM_Service

3. Check if all adobe services are started

4. Check if credential attributes have been registered correctly

Info: Configuring the credential attributes consists of registering the password and the alias of each credential which is used by Adobe document services, as well as setting other attributes such as the sha1 value.

. In theAliasfield, enter the alias of the credential you installed. Enter the following:

○ ReaderRights, when you configure a Reader right credential for usage rights.

○ DocumentCertification, when you configure a credential for certification.

○ ServerSignature, when you configure a credential for digital signatures.

http://help.sap.com/saphelp_nwpi711/helpdata/en/2d/223cac65804e03b9044059c4f59201/content.htm?frameset=/en/fe/e8cc48abee49f082dfbd5b45d98dd4/frameset.htm&current_toc=/en/45/a3c3f543cb0cf0e10000000a114a6b/plain.htm&node_id=194

1. Create a class like the one below, containing a method for starting BPM process, using BPM Api

package<Package_Name>;
 
import java.net.URI;
import java.util.Map;
import java.util.Set;
import com.sap.bpm.api.BPMFactory;
import com.sap.bpm.pm.api.ProcessDefinition;
import com.sap.bpm.pm.api.ProcessDefinitionManager;
import com.sap.bpm.pm.api.ProcessStartEvent;
import com.sap.bpm.pm.api.ProcessStartManager;
import commonj.sdo.DataObject;
import commonj.sdo.Property;
 
publicclass ProcessStarter {
 
private ProcessDefinitionManager processDefinitionManager;
private ProcessDefinition processDefinition;
private ProcessStartManager processStartManager;
private Set<ProcessStartEvent> processStartEvents;
private ProcessStartEvent processStartEvent;
public ProcessStarter(String vendor, String dcName, String processTechnicalName) {
this.processDefinitionManager = BPMFactory.getProcessDefinitionManager();
this.processStartManager = BPMFactory.getProcessStartManager();
this.processDefinition = processDefinitionManager.getActiveProcessDefinition(vendor, dcName, processTechnicalName);
 
 }
 
public DataObject getProcessStartDataObject(){
this.processStartEvents = processStartManager.getProcessStartEvents(processDefinition.getId());
this.processStartEvent = processStartEvents.iterator().next();
 
 DataObject sdo = processStartManager.createDataObjectForStartEvent(this.processStartEvent); 
 
return sdo;
 }
 
 
public URI startProcess(DataObject dataObject) throws BPMProcessStartException{
try {
return processStartManager.startProcess(this.processStartEvent, dataObject);
 } catch (Exception e) {
thrownew BPMProcessStartException("Could not start process: "+ e.getMessage() , e);
 }
 }
}

2. Create an instance from the above class:

ProcessStarter starter = new ProcessStarter("<Vendor-Name>", "<DC-Name>", "<Process-Name>");

3. Set process input data:

DataObject startSDO = starter.getProcessStartDataObject();
DataObject processInput = startSDO.getDataObject("StartProcess");
 processInput.set("engDepartment",”VALUE”);
 processInput.set("itemNo", “VALUE”);
 processInput.set("orderNo", “VALUE”);

processInput.set("organization",”VALUE”);
 processInput.set("processType", “VALUE”);
 processInput.set("requestNo", “VALUE”);

processInput.set("requestorId", “VALUE”);
URI processInstanceId = starter.startProcess(startSDO);

Hi All,

We are taking the license's for SAP ECC & BOBI Platform 4.1 from SAP HANA Cloud Platform Innovation Packs.

So we wanted to install SAP ERP & SAP BOBI Platform 4.1 in the same hardware with a common database as a MaxDB.

Is it technically possible to do it.

Dear all,

Over time,the number of userson my system SAPis growing. Whatattractsthe cost of managingthem.

Anybody integrates SAP CUA withAD?And howyou control the fired employees?

Hi community,

In the SE09 transaction and in stms tail there are accumulated a lot of old orders.

Can somebody tell me how I can remove these old orders without destroying the system?

The system would need to continue working as until now but deleting these unnecessary orders.

Thanks in advance.

Best regards

Cristina

Hello,

onlytohelpotherusers:

I amloggedinto the system andcallthe transaction "/IWFND/MAINT_SERVICE".

The following error messageappears:

Solution of the problem:

Callthe transactionas follows "/n/IWFND/MAINT_SERVICE"

Best Regards,

Ulrike

In this document you will find the latest information about the SAP kernel such as

• Announcements of SP stack kernel deliveries
• Other news related to the development, maintenance and usage of the SAP kernel versions 72X (720, 720_EXT, 721, 721_EXT, 722, 722_EXT) and 74X (741, 742, 745)

If you are interested in getting notifications when this document is updated, please activate the "Receive email notifications" feature. To unsubscribe from receiving notifications, click on "Stop email notifications".

News

18.12.2015: SAP Kernel 721 PL 618 and SAP Kernel 722 PL 20 and PL 21 revoked

As a precaution the Kernel (dw.sar) for 721 PL 618 and 722 PL 20 and 21 have been revoked from the SAP Support Portal.

For further details see SAP Note 2259736. We are working a patch highest priority.

13.11.2015: Heads up on Kernel 745 for NetWeaver 7.4

During Q1/2016 SAP Kernel 745 will be made available as Downward Compatible Kernel for SAP NetWeaver 7.4.

SAP Kernel 745 will eventually succeed SAP Kernel 742 (and 741 and 740).

SAP Kernel 742 will be retired in Q1/2017, one year later than the availability of SAP Kernel 745 as DCK. No more patches will be provided for SAP Kernel 742 after that date.

See also Understanding Kernel Releases for the SAP NetWeaver AS ABAP and SAP Note 1969546 - Release Roadmap Kernel 740

09.11.2015: SP Stack Kernel 742 PL#300 Released

SP stack kernel 742 PL #300 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in SAP Note 2237353.

Information on known issues in the stack kernel 742 PL #300 can be found in SAP Note 2231749. This note will be updated on a regular basis.

16.10.2015: Kernel 722 PL14, PL15 and enserver PL 14 revoked

As a precaution Enqueue Server 722 PL 14 (enserver.sar) and Kernel (dw.sar) 722 PL 14 and PL 15 have been revoked from the SAP Support Portal.
The new patch of the Enqueue Server might not be 100% compatible to older clients (e.g. disp+work PL 13) and the newer disp+work starting PL 14 might not be 100% compatible with old Enqueue Servers (prior patch 14). Standard operations Enque, Dequeue and DequeueAll are NOT affected. Details can be found in SAP Note 2239931

13.10.2015: SP Stack Kernel 721 PL#600 Released

SP stack kernel 721 PL #600 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in SAP Note 2214191.

Information on known issues in the stack kernel 721 PL #600 can be found in SAP Note 2214680. This note will be updated on a regular basis.

02.10.2015: issue with Oracle lib_DBSL 722 PL 13

Please do not use patch 13 for the 722 Oracle lib_DBSL

Further details can be found in note 2220724. A fix is expected early next week.

14.09.2015: SP Stack Kernel 741 PL#300 Released

The last SP stack kernel for the 741 kernel version has been released today. Kernel 741 PL #300 can be downloaded from the archive area of SAP Support Portal. Refer to release note 2207362 for information on fixes included in this stack kernel.

As announced previously, kernel 741 has reached its end of maintenance, see note 1969546 for more detail. Future 74* kernel corrections will be delivered through 742 kernel patches.

08.07.2015: SP Stack Kernel 742 PL#200 Released

SP stack kernel 742 PL #200 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in Note 2178917.

Information on known issues in the stack kernel 742 PL #200 can be found in Note 2176515. This note will be updated on a regular basis.

07.07.2015 SAP Kernel 741 maintenance

The SAP Kernel 741 reached its end of maintenance, see note 1969546. We will continue to deliver regression fixes during July and a final stack kernel 741 PL#300 in August. After that corrections will be delivered through kernel 742 patches.

12.06.2015 SAP Kernel Archive

SAP Kernels which are out of maintenance like SAP Kernel 720 can be found in the archive https://support.sap.com/software/patches/archive.html

For SAP Kernel 720 the last version is patch level 800. Please read the release note 2158874  - SAP Support Package Stack Kernel 7.20 (EXT) Patch Level 800. Corresponding note for regression found in the future is 2138737.

20.05.2015 SAP Kernel 722 Released

SAP kernel 722 has been released for customers today. The first shipment (Kernel 722 PL#4) can now be downloaded from SAP Support Portal. With this a new release cycle has been established for 72X kernel versions that can be used with all SAP NetWeaver releases 7.00-7.31:

• Kernel 720 reached its end of maintenance, no further corrections will be provided for this kernel version
• Kernel 721 becomes the standard kernel containing only corrections/bug fixes
• Kernel 722 replaces Kernel 721 in its role as Innovation Kernel. Besides regular corrections, new features/enhancements/improvements will be delivered with Kernel 722.

Refer to SAP Note 2133909 for general information on Kernel 722 including new features and current limitations. This note will be updated on regular basis.

Kernel 722 can be applied manually as a kernel patch, see Note 2115344 - Installation of Kernel 722 (EXT) for detailed instructions. Options to apply Kernel 722 during upgrade/update are outlined in Note 2133909.

04.05.2015: SP Stack Kernel 721 PL#500 Released

A new SP stack kernel 721 PL #500 is now available on SAP Support Portal.

SAP Note 2158856 contains the list of changes and enhancements introduced in this stack kernel compared to the previous stack kernel PL #402.

All regressions known in the PL #402 have been fixed.

Review SAP Note 2155366 for known issues in the stack kernel 721 PL #500. This note will be continuously updated.

14.04.2015: Kernel 742 Released as DCK to Kernels 740 and 741

After an extended validation phase kernel 742 PL#101 has been released as a downward compatible kernel (DCK) to kernels 741 and 740 and can be used instead of these with SAP NetWeaver 7.4. Refer to Note 2128122 for details on installation and usage of kernel 742 as DCK. The release roadmap for 74* kernels is presented in Note 1969546.

31.03.2015: SP Stack Kernels 741 PL#201 and 742 PL#101 are delivered

As announced previously, SP Stack kernels for 741 and 742 kernel versions have been updated. 741 PL#201 replaces 741 PL#200 and 742 PL#101 replaces 742 PL#100. New SP stack kernels can be now downloaded from SAP Support Portal, following fixes are included:

• Regression in the Oracle DBSL Library (Note 2118448, Point 2 - Termination during secondary database connection; LRAW length error) is removed.
• CommonCryptoLib has been updated to the version 8.4.35 (see Note 2134460.)

For more details on 741 PL#201 refer to Notes 2150081 - SAP Support Package Stack Kernel 7.41 Patch Level 201 and 2100429 - Known regressions in kernel 7.41 patch level 201.

Fixes and enhancements in the SP stack kernel 742 PL#101 are listed in the note 2145156. Information on known issues with this stack kernel can be found in the Note 2134238.

19.03.2015: Update on SP Stack Kernels 741 PL#200 and 742 PL#100

The latest SP stack kernels 741 (PL#200) and 742 (PL#100) contain a regression in the Oracle DBSL Library, see Note 2118448 -Termination during secondary database connection; LRAW length error, Point 2.

As a solution you may use the latest ORA lib_dbsl available on SAP Support portal. For kernel 741 on Windows, please be aware of the issue 2142073 - Application server in Windows NT with Oracle does not start.

Updated stack kernels will be provided as soon as possible.

11.03.2015: SP Stack Kernel 721 PL#402 Released

SP Stack kernel 721 PL #402 has been released and can be downloaded from SAP Support Portal. The issues from PL#400 (Note 2118382) and PL#401 (Note 2138260) are fixed.

Refer to Note 2138680 - SAP Support Package Stack Kernel 7.21 (EXT) Patch Level 402 for overview of new features, enhancements and improvements added since PL#300. Known regressions are documented in Note 2138678.

09.03.2015: SP Stack Kernel 742 PL#100 Released

SP stack kernel 742 PL #100 is now available on SAP Support Portal. It contains various improvements and enhancements that are outlined in detail in Note 2136550.

Information on known issues in the stack kernel 742 PL #100 can be found in Note 2129327. This note will be updated on regular basis.

04.03.2015: SP Stack Kernel 721 PL#401 Revoked

SP Stack kernel 721 PL #401 has been revoked from SAP Support Portal for all platforms except for MS Windows because the kernel archives contained some files with wrong versions.

In most cases it is not necessary to replace the kernel in a system running with PL#401 because the issue has a limited impact and does not affect the kernel itself. Details are outlined in Note 2138260.

SP stack kernel PL#402 will be released as soon as possible; this document will be updated accordingly.

06.02.2015: SP Stack Kernel 741 PL#200 Released

A new SP stack kernel 741 PL #200 has been released today and can be downloaded from SAP Support Portal.

For a summary of enhancements and improvements included into this stack kernel, see SAP Note 2101802 - SAP Support Package Stack Kernel 7.41 Patch Level 200.

30.01.2015: SP Stack Kernel 721 PL#401 Replaces PL#400

Current SP stack kernel 721 PL#400 has been replaced with PL#401, see Note 2121693 - SAP Support Package Stack Kernel 7.21 (EXT) Patch Level 401.

It fixes a file permission issue that has a very limited impact:

• It occurs with 721_EXT kernel on Windows platforms only
• It has no effect at runtime, only for future system maintenance
• Workaround is easy.

This means: even if above criteria apply, it is not always necessary to replace already installed 721 kernel PL#400. Refer to Note 2118382 for more information.

Note 2084437 contains the list of known regressions in the stack kernel 721 PL #401. This note will be continuously updated.

16.12.2014: SP Stack Kernel 721 PL#400 Released

A new SP stack kernel 721 PL #400 is now available on SAP Service Marketplace.

SAP Note 2101779 contains the list of changes and enhancements introduced in this stack kernel compared to the previous stack kernel PL #300.

All regressions known in the PL #300 have been fixed.

Review SAP Note 2084436 for known issues in the stack kernel 721 PL #400. This note will be continuously updated.

Hello Community,

i've got a problem with the Logoff Url on my AS Java NetWeaver 7.3

I set the parameter ume.logoff.redirect.url, but in NWA this LogOff URL is not working.

I'm alway redirect back to NWA.

best regards

Bastian Gschrey

Hi Guys,

jspm -errorr - nw 7.3 as java - windows 2008,

-completed - kernel upgradeusing jspm

-sapjvm , jspm update,

after that gettgin these errors,

kidnly tell how to resolve this,

pasting log files required ,

dev_server log

---------------------------------------------------

trc file: "dev_server0", trc level: 1, release: "720"

---------------------------------------------------

sysno      02

sid        J73

systemid   562 (PC with Windows NT)

relno      7200

patchlevel 0

patchno    63

intno      20020600

make       multithreaded, Unicode, 64 bit, optimized

profile    \\host\sapmnt\J73\SYS\profile\J73_J02_

pid        696

*

*  ACTIVE TRACE LEVEL           1

*  ACTIVE TRACE COMPONENTS      All, egi

*

Sun Feb 17 14:06:14 2013

*

*  trace logging activated, max size = 52428800 bytes, 2 versions

*

arguments :

  arg[ 0] : E:\usr\sap\J73\J02\exe\jstart.EXE

  arg[ 1] : -appTrc

  arg[ 2] : -nodeId=2

  arg[ 3] : pf=\\\sapmnt\J73\SYS\profile\J73_J02_

  arg[ 4] : -DSAPINFO=J73_02_server0

  arg[ 5] : -hostvm

  arg[ 6] : -nodeName=ID22924050

  arg[ 7] : -file=E:\usr\sap\J73\J02\j2ee\cluster\instance.properties

  arg[ 8] : -jvmFile=E:\usr\sap\J73\J02\work\jstart.jvm

  arg[ 9] : -traceFile=E:\usr\sap\J73\J02\work\dev_server0

  arg[10] : -javaOutFile=E:\usr\sap\J73\J02\work\jvm_server0.out

F 

F Sun Feb 17 14:06:14 2013

F  ********************************************************************************

F  Java environment properties

F    root directory    : E:\usr\sap\J73\J02\exe\sapjvm_6

F    vendor            : SAP AG

F    version           : 1.6.0_37

F    cpu               : amd64

F    java vm type      : server

F    java vm version   : 6.1.045 21.1-b06

F    jvm library name  : jvm.dll

F    library path      : E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin\server;E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin

F    executable path   : E:\usr\sap\J73\J02\exe\sapjvm_6\bin

F    SAP extensions    : available

F  ********************************************************************************

I  [Thr 3944] MtxInit: 10002 0 2

I  [Thr 3944] MPI: dynamic quotas disabled.

I  [Thr 3944] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%

M  [Thr 3944] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)

M  [Thr 3944] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.

M  [Thr 3944] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.

M  [Thr 3944] CCMS: CCMS Monitoring Initialization finished, rc=0.

F 

F Sun Feb 17 14:06:14 2013

F  ********************************************************************************

F  SAP Java VM arguments:

F    arg[ 0] = vfprintf

F    arg[ 1] = abort

F    arg[ 2] = exit

F    arg[ 3] = -XmonGcCallback

F    arg[ 4] = -XdebugStateChangeCallback

F    arg[ 5] = -DSAPJStartVersion=720, patch 401, changelist 0, NTAMD64, optU (EXT) (Jan 16 2013, 16:44:32)

F    arg[ 6] = -Xjvmx

F    arg[ 7] = -XsapSystem:02

F    arg[ 8] = -DSAPSTARTUP=1

F    arg[ 9] = -DSAPSYSTEM=02

F    arg[10] = -DSAPSYSTEMNAME=J73

F    arg[11] = -DSAPMYNAME=_J73_02

F    arg[12] = -DSAPDBHOST=

F    arg[13] = -DSAPINFO=J73_02_server0

F    arg[14] = -Dj2ee.dbhost=

F    arg[15] = -Dsun.java.launcher=jstart

F    arg[16] = -Dsun.java.command=com.sap.engine.boot.Start 

F    arg[17] = -Djstartup.mode=JSTART

F    arg[18] = -Djstartup.whoami=server

F    arg[19] = -Djstartup.ownProcessId=696

F    arg[20] = -Djstartup.ownHardwareId=R0115937657

F    arg[21] = -Djstartup.debuggable=yes

F    arg[22] = -DLoadBalanceRestricted=no

F    arg[23] = -XdebugPortRange:50221-50221

F    arg[24] = -Denv.class.path=

F    arg[25] = -Dsys.global.dir=E:\usr\sap\J73\SYS\global

F    arg[26] = -Dapplication.home=E:\usr\sap\J73\J02\exe

F    arg[27] = -Djava.class.path=E:\usr\sap\J73\J02\exe\jstart71.jar;E:\usr\sap\J73\J02\exe\sapjvm_6\lib\jvmx.jar;E:\usr\sap\J73\J02\exe\sapjvm_6\lib\jvmx_tools.jar;E:\usr\sap\J73\J02\exe\jre\lib\iqlib.jar;E:\usr\sap\J73\J02\exe\sapjvm_6\lib\tools.jar;E:\usr\sap\J73\J02\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;E:\usr\sap\J73\J02\j2ee\cluster\bin\boot\jaas.jar;E:\usr\sap\J73\J02\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;E:\usr\sap\J73\J02\j2ee\cluster\bin\boot\memoryanalyzer.jar

F    arg[28] = -Djava.library.path=E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin\server;E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin;E:\usr\sap\J73\J02\j2ee\os_libs;E:\usr\sap\J73\J02\exe\sapjvm_6\bin;E:\usr\sap\J73\J02\exe;C:\Program Files (x86)\Intel\iCLS Client;C:\Program Files\Intel\iCLS Client;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE;C:\Program Files

(x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn;E:\usr\sap\J73\SYS\exe\uc\NTAMD64

F    arg[29] = -XX:PermSize=1024m

F    arg[30] = -Xmx4096m

F    arg[31] = -XX:MaxNewSize=1365m

F    arg[32] = -XX:MaxPermSize=1024m

F    arg[33] = -Xms4096m

F    arg[34] = -XX:NewSize=1365m

F    arg[35] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy

F    arg[36] = -Djavax.management.builder.initial=com.sap.pj.jmx.server.interceptor.InterceptorChainBuilder

F    arg[37] = -Djmx.invoke.getters=true

F    arg[38] = -Djava.security.policy=./../bin/kernel/java.policy

F    arg[39] = -Djava.security.egd=file:/dev/urandom

F    arg[40] = -Djava.awt.headless=true

F    arg[41] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy

F    arg[42] = -Drdbms.driverLocation=E:\usr\sap\J73\J02\exe\mssjdbc\jdbc4\sqljdbc4.jar

F    arg[43] = -Djava.io.tmpdir=./temp

F    arg[44] = -Dsun.lang.ClassLoader.allowArraySyntax=true

F    arg[45] = -Djava.protocol.handler.pkgs=com.sap.engine.httpdsrclient.protocols|iaik.protocol

F    arg[46] = -Dnetworkaddress.cache.ttl=10

F    arg[47] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler

F    arg[48] = -Djco.jarm=1

F    arg[49] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy

F    arg[50] = -XX:+UseConcMarkSweepGC

F    arg[51] = -XX:TargetSurvivorRatio=90

F    arg[52] = -verbose:gc

F    arg[53] = -XX:+DumpDetailedClassStatisticOnOutOfMemory

F    arg[54] = -XX:+PrintGCDetails

F    arg[55] = -XX:MaxErrorQueueLength=200

F    arg[56] = -XX:+PrintGCTimeStamps

F    arg[57] = -XX:+DisableExplicitGC

F    arg[58] = -XX:SoftRefLRUPolicyMSPerMB=1

F    arg[59] = -XX:-StringInternTableInPermGen

F    arg[60] = -XX:SurvivorRatio=6

F    arg[61] = -Xss2m

F    arg[62] = -XX:+HeapDumpOnOutOfMemoryError

F    arg[63] = -XX:HeapDumpPath=OOM.hprof

F    arg[64] = -XX:-TraceClassUnloading

F  ignore unrecognized options : no

F  ********************************************************************************

J  JVMX version - Dec  5 2012 00:34:13 - 61_REL - optU - windows amd64 - 6 - bas2:184594 (mixed mode)

J  (CompilerOracle read from file E:\usr\sap\J73\J02\exe\sapjvm_6\jre\.hotspot_compiler)

F  [Thr 5796] *** LOG => SfCJavaVm: Java VM started.

F  ********************************************************************************

F  Main method call:

F  com/sap/engine/boot/Start.main()

F  ********************************************************************************

J 

J Sun Feb 17 14:06:15 2013

J  1.806: [GC 1.806: [ParNew: 1048320K->5846K(1223040K), 0.0296941 secs] 1048326K->5852K(4019584K), 0.0297815 secs] [Times: user=0.13 sys=0.00, real=0.03 secs]

F 

F [Thr 5796] Sun Feb 17 14:06:16 2013

F  [Thr 5796] *** LOG => State changed from 0 (Initial) to 1 (Waiting to start).

F  [Thr 5796] *** LOG    state real time: 3.025 CPU time: 0.514 sys, 4.882 usr

F  [Thr 5796] *** LOG    total real time: 3.025 CPU time: 0.514 sys, 4.882 usr

F  [Thr 5796]

F  [Thr 5796] *** LOG => State changed from 1 (Waiting to start) to 2 (Starting framework).

F  [Thr 5796] *** LOG    state real time: 0.001 CPU time: 0.000 sys, 0.000 usr

F  [Thr 5796] *** LOG    total real time: 3.026 CPU time: 0.514 sys, 4.882 usr

F  [Thr 5796]

J 

J Sun Feb 17 14:06:24 2013

J  Heap

J   par new generation   reserved 1397760K, committed 1397760K, used 889764K [0x0000000180010000, 0x00000001d5510000, 0x00000001d5510000)

J    eden space 1048320K,  84% used [0x0000000180010000, 0x00000001b5f43890, 0x00000001bffd0000)

J    from space 174720K,   3% used [0x00000001caa70000, 0x00000001cb0258a0, 0x00000001d5510000)

J    to   space 174720K,   0% used [0x00000001bffd0000, 0x00000001bffd0000, 0x00000001caa70000)

J   concurrent mark-sweep generation reserved 2796544K, committed 2796544K, used 926K [0x00000001d5510000, 0x0000000280010000, 0x0000000280010000)

J   concurrent-mark-sweep perm gen reserved 1048576K, committed 1048576K, used 54095K [0x0000000280010000, 0x00000002c0010000, 0x00000002c0010000)

F 

F [Thr 4516] Sun Feb 17 14:06:24 2013

F  [Thr 4516] *** LOG => SfCJavaVm: exit hook is called. (rc = 2150)

F 

F  ********************************************************************************

F  *** ERROR => Java node 'server0' terminated with exit code 2150.

F  ***

F  *** Please see section 'Java program exit codes'

F  *** in SAP Note 1316652 for additional information and trouble shooting advice.

F  ********************************************************************************

F 

F  [Thr 4516] *** LOG => exiting (exitcode 2150, retcode 1).

M  [Thr 4516] CCMS: CCMS Monitoring Cleanup finished successfully.

---------------------------------------------------

trc file: "dev_server0", trc level: 1, release: "720"

---------------------------------------------------

sysno      02

sid        J73

systemid   562 (PC with Windows NT)

relno      7200

patchlevel 0

patchno    63

intno      20020600

make       multithreaded, Unicode, 64 bit, optimized

profile    \\\sapmnt\J73\SYS\profile\J73_J02_

pid        4356

*

*  ACTIVE TRACE LEVEL           1

*  ACTIVE TRACE COMPONENTS      All, egi

*

Sun Feb 17 14:06:35 2013

*

*  trace logging activated, max size = 52428800 bytes, 2 versions

*

arguments :

  arg[ 0] : E:\usr\sap\J73\J02\exe\jstart.EXE

  arg[ 1] : -appTrc

  arg[ 2] : -nodeId=2

  arg[ 3] : pf=\\\sapmnt\J73\SYS\profile\J73_J02_

  arg[ 4] : -DSAPINFO=J73_02_server0

  arg[ 5] : -hostvm

  arg[ 6] : -nodeName=ID22924050

  arg[ 7] : -file=E:\usr\sap\J73\J02\j2ee\cluster\instance.properties

  arg[ 8] : -jvmFile=E:\usr\sap\J73\J02\work\jstart.jvm

  arg[ 9] : -traceFile=E:\usr\sap\J73\J02\work\dev_server0

  arg[10] : -javaOutFile=E:\usr\sap\J73\J02\work\jvm_server0.out

F 

F Sun Feb 17 14:06:35 2013

F  ********************************************************************************

F  Java environment properties

F    root directory    : E:\usr\sap\J73\J02\exe\sapjvm_6

F    vendor            : SAP AG

F    version           : 1.6.0_37

F    cpu               : amd64

F    java vm type      : server

F    java vm version   : 6.1.045 21.1-b06

F    jvm library name  : jvm.dll

F    library path      : E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin\server;E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin

F    executable path   : E:\usr\sap\J73\J02\exe\sapjvm_6\bin

F    SAP extensions    : available

F  ********************************************************************************

I  [Thr 5260] MtxInit: 10002 0 2

I  [Thr 5260] MPI: dynamic quotas disabled.

I  [Thr 5260] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%

M  [Thr 5260] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)

M  [Thr 5260] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.

M  [Thr 5260] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.

M  [Thr 5260] CCMS: CCMS Monitoring Initialization finished, rc=0.

F 

F Sun Feb 17 14:06:35 2013

F  ********************************************************************************

F  SAP Java VM arguments:

F    arg[ 0] = vfprintf

F    arg[ 1] = abort

F    arg[ 2] = exit

F    arg[ 3] = -XmonGcCallback

F    arg[ 4] = -XdebugStateChangeCallback

F    arg[ 5] = -DSAPJStartVersion=720, patch 401, changelist 0, NTAMD64, optU (EXT) (Jan 16 2013, 16:44:32)

F    arg[ 6] = -Xjvmx

F    arg[ 7] = -XsapSystem:02

F    arg[ 8] = -DSAPSTARTUP=1

F    arg[ 9] = -DSAPSYSTEM=02

F    arg[10] = -DSAPSYSTEMNAME=J73

F    arg[11] = -DSAPMYNAME=_J73_02

F    arg[12] = -DSAPDBHOST=

F    arg[13] = -DSAPINFO=J73_02_server0

F    arg[14] = -Dj2ee.dbhost=

F    arg[15] = -Dsun.java.launcher=jstart

F    arg[16] = -Dsun.java.command=com.sap.engine.boot.Start 

F    arg[17] = -Djstartup.mode=JSTART

F    arg[18] = -Djstartup.whoami=server

F    arg[19] = -Djstartup.ownProcessId=4356

F    arg[20] = -Djstartup.ownHardwareId=R0115937657

F    arg[21] = -Djstartup.debuggable=yes

F    arg[22] = -DLoadBalanceRestricted=no

F    arg[23] = -XdebugPortRange:50221-50221

F    arg[24] = -Denv.class.path=

F    arg[25] = -Dsys.global.dir=E:\usr\sap\J73\SYS\global

F    arg[26] = -Dapplication.home=E:\usr\sap\J73\J02\exe

F    arg[27] = -Djava.class.path=E:\usr\sap\J73\J02\exe\jstart71.jar;E:\usr\sap\J73\J02\exe\sapjvm_6\lib\jvmx.jar;E:\usr\sap\J73\J02\exe\sapjvm_6\lib\jvmx_tools.jar;E:\usr\sap\J73\J02\exe\jre\lib\iqlib.jar;E:\usr\sap\J73\J02\exe\sapjvm_6\lib\tools.jar;E:\usr\sap\J73\J02\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;E:\usr\sap\J73\J02\j2ee\cluster\bin\boot\jaas.jar;E:\usr\sap\J73\J02\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;E:\usr\sap\J73\J02\j2ee\cluster\bin\boot\memoryanalyzer.jar

F    arg[28] = -Djava.library.path=E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin\server;E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin;E:\usr\sap\J73\J02\j2ee\os_libs;E:\usr\sap\J73\J02\exe\sapjvm_6\bin;E:\usr\sap\J73\J02\exe;C:\Program Files (x86)\Intel\iCLS Client;C:\Program Files\Intel\iCLS Client;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE;C:\Program Files

(x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn;E:\usr\sap\J73\SYS\exe\uc\NTAMD64

F    arg[29] = -XX:PermSize=1024m

F    arg[30] = -Xmx4096m

F    arg[31] = -XX:MaxNewSize=1365m

F    arg[32] = -XX:MaxPermSize=1024m

F    arg[33] = -Xms4096m

F    arg[34] = -XX:NewSize=1365m

F    arg[35] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy

F    arg[36] = -Djavax.management.builder.initial=com.sap.pj.jmx.server.interceptor.InterceptorChainBuilder

F    arg[37] = -Djmx.invoke.getters=true

F    arg[38] = -Djava.security.policy=./../bin/kernel/java.policy

F    arg[39] = -Djava.security.egd=file:/dev/urandom

F    arg[40] = -Djava.awt.headless=true

F    arg[41] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy

F    arg[42] = -Drdbms.driverLocation=E:\usr\sap\J73\J02\exe\mssjdbc\jdbc4\sqljdbc4.jar

F    arg[43] = -Djava.io.tmpdir=./temp

F    arg[44] = -Dsun.lang.ClassLoader.allowArraySyntax=true

F    arg[45] = -Djava.protocol.handler.pkgs=com.sap.engine.httpdsrclient.protocols|iaik.protocol

F    arg[46] = -Dnetworkaddress.cache.ttl=10

F    arg[47] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler

F    arg[48] = -Djco.jarm=1

F    arg[49] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy

F    arg[50] = -XX:+UseConcMarkSweepGC

F    arg[51] = -XX:TargetSurvivorRatio=90

F    arg[52] = -verbose:gc

F    arg[53] = -XX:+DumpDetailedClassStatisticOnOutOfMemory

F    arg[54] = -XX:+PrintGCDetails

F    arg[55] = -XX:MaxErrorQueueLength=200

F    arg[56] = -XX:+PrintGCTimeStamps

F    arg[57] = -XX:+DisableExplicitGC

F    arg[58] = -XX:SoftRefLRUPolicyMSPerMB=1

F    arg[59] = -XX:-StringInternTableInPermGen

F    arg[60] = -XX:SurvivorRatio=6

F    arg[61] = -Xss2m

F    arg[62] = -XX:+HeapDumpOnOutOfMemoryError

F    arg[63] = -XX:HeapDumpPath=OOM.hprof

F    arg[64] = -XX:-TraceClassUnloading

F  ignore unrecognized options : no

F  ********************************************************************************

J  JVMX version - Dec  5 2012 00:34:13 - 61_REL - optU - windows amd64 - 6 - bas2:184594 (mixed mode)

J  (CompilerOracle read from file E:\usr\sap\J73\J02\exe\sapjvm_6\jre\.hotspot_compiler)

F  [Thr 8980] *** LOG => SfCJavaVm: Java VM started.

F  ********************************************************************************

F  Main method call:

F  com/sap/engine/boot/Start.main()

F  ********************************************************************************

J 

J Sun Feb 17 14:06:36 2013

J  1.725: [GC 1.725: [ParNew: 1048320K->5689K(1223040K), 0.0272506 secs] 1048326K->5696K(4019584K), 0.0273566 secs] [Times: user=0.09 sys=0.00, real=0.03 secs]

F 

F [Thr 8980] Sun Feb 17 14:06:37 2013

F  [Thr 8980] *** LOG => State changed from 0 (Initial) to 1 (Waiting to start).

F  [Thr 8980] *** LOG    state real time: 2.906 CPU time: 0.436 sys, 4.602 usr

F  [Thr 8980] *** LOG    total real time: 2.906 CPU time: 0.436 sys, 4.602 usr

F  [Thr 8980]

F  [Thr 8980] *** LOG => State changed from 1 (Waiting to start) to 2 (Starting framework).

F  [Thr 8980] *** LOG    state real time: 0.000 CPU time: 0.000 sys, 0.000 usr

F  [Thr 8980] *** LOG    total real time: 2.906 CPU time: 0.436 sys, 4.602 usr

F  [Thr 8980]

J 

J Sun Feb 17 14:06:47 2013

J  Heap

J   par new generation   reserved 1397760K, committed 1397760K, used 937458K [0x0000000180010000, 0x00000001d5510000, 0x00000001d5510000)

J    eden space 1048320K,  88% used [0x0000000180010000, 0x00000001b8dfe588, 0x00000001bffd0000)

J    from space 174720K,   3% used [0x00000001caa70000, 0x00000001caffe660, 0x00000001d5510000)

J    to   space 174720K,   0% used [0x00000001bffd0000, 0x00000001bffd0000, 0x00000001caa70000)

J   concurrent mark-sweep generation reserved 2796544K, committed 2796544K, used 928K [0x00000001d5510000, 0x0000000280010000, 0x0000000280010000)

J   concurrent-mark-sweep perm gen reserved 1048576K, committed 1048576K, used 54085K [0x0000000280010000, 0x00000002c0010000, 0x00000002c0010000)

F 

F [Thr 9004] Sun Feb 17 14:06:47 2013

F  [Thr 9004] *** LOG => SfCJavaVm: exit hook is called. (rc = 2150)

F 

F  ********************************************************************************

F  *** ERROR => Java node 'server0' terminated with exit code 2150.

F  ***

F  *** Please see section 'Java program exit codes'

F  *** in SAP Note 1316652 for additional information and trouble shooting advice.

F  ********************************************************************************

F 

F  [Thr 9004] *** LOG => exiting (exitcode 2150, retcode 1).

M  [Thr 9004] CCMS: CCMS Monitoring Cleanup finished successfully.

---------------------------------------------------

trc file: "dev_server0", trc level: 1, release: "720"

---------------------------------------------------

sysno      02

sid        J73

systemid   562 (PC with Windows NT)

relno      7200

patchlevel 0

patchno    63

intno      20020600

make       multithreaded, Unicode, 64 bit, optimized

profile    \\\sapmnt\J73\SYS\profile\J73_J02_

pid        8460

*

*  ACTIVE TRACE LEVEL           1

*  ACTIVE TRACE COMPONENTS      All, egi

*

Sun Feb 17 14:06:57 2013

*

*  trace logging activated, max size = 52428800 bytes, 2 versions

*

arguments :

  arg[ 0] : E:\usr\sap\J73\J02\exe\jstart.EXE

  arg[ 1] : -appTrc

  arg[ 2] : -nodeId=2

  arg[ 3] : pf=\\sapmnt\J73\SYS\profile\J73_J02_

  arg[ 4] : -DSAPINFO=J73_02_server0

  arg[ 5] : -hostvm

  arg[ 6] : -nodeName=ID22924050

  arg[ 7] : -file=E:\usr\sap\J73\J02\j2ee\cluster\instance.properties

  arg[ 8] : -jvmFile=E:\usr\sap\J73\J02\work\jstart.jvm

  arg[ 9] : -traceFile=E:\usr\sap\J73\J02\work\dev_server0

  arg[10] : -javaOutFile=E:\usr\sap\J73\J02\work\jvm_server0.out

F 

F Sun Feb 17 14:06:57 2013

F  ********************************************************************************

F  Java environment properties

F    root directory    : E:\usr\sap\J73\J02\exe\sapjvm_6

F    vendor            : SAP AG

F    version           : 1.6.0_37

F    cpu               : amd64

F    java vm type      : server

F    java vm version   : 6.1.045 21.1-b06

F    jvm library name  : jvm.dll

F    library path      : E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin\server;E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin

F    executable path   : E:\usr\sap\J73\J02\exe\sapjvm_6\bin

F    SAP extensions    : available

F  ********************************************************************************

I  [Thr 3948] MtxInit: 10002 0 2

I  [Thr 3948] MPI: dynamic quotas disabled.

I  [Thr 3948] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%

M  [Thr 3948] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)

M  [Thr 3948] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.

M  [Thr 3948] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.

M  [Thr 3948] CCMS: CCMS Monitoring Initialization finished, rc=0.

F 

F Sun Feb 17 14:06:57 2013

F  ********************************************************************************

F  SAP Java VM arguments:

F    arg[ 0] = vfprintf

F    arg[ 1] = abort

F    arg[ 2] = exit

F    arg[ 3] = -XmonGcCallback

F    arg[ 4] = -XdebugStateChangeCallback

F    arg[ 5] = -DSAPJStartVersion=720, patch 401, changelist 0, NTAMD64, optU (EXT) (Jan 16 2013, 16:44:32)

F    arg[ 6] = -Xjvmx

F    arg[ 7] = -XsapSystem:02

F    arg[ 8] = -DSAPSTARTUP=1

F    arg[ 9] = -DSAPSYSTEM=02

F    arg[10] = -DSAPSYSTEMNAME=J73

F    arg[11] = -DSAPMYNAME=_J73_02

F    arg[12] = -DSAPDBHOST=

F    arg[13] = -DSAPINFO=J73_02_server0

F    arg[14] = -Dj2ee.dbhost=

F    arg[15] = -Dsun.java.launcher=jstart

F    arg[16] = -Dsun.java.command=com.sap.engine.boot.Start 

F    arg[17] = -Djstartup.mode=JSTART

F    arg[18] = -Djstartup.whoami=server

F    arg[19] = -Djstartup.ownProcessId=8460

F    arg[20] = -Djstartup.ownHardwareId=R0115937657

F    arg[21] = -Djstartup.debuggable=yes

F    arg[22] = -DLoadBalanceRestricted=no

F    arg[23] = -XdebugPortRange:50221-50221

F    arg[24] = -Denv.class.path=

F    arg[25] = -Dsys.global.dir=E:\usr\sap\J73\SYS\global

F    arg[26] = -Dapplication.home=E:\usr\sap\J73\J02\exe

F    arg[27] = -Djava.class.path=E:\usr\sap\J73\J02\exe\jstart71.jar;E:\usr\sap\J73\J02\exe\sapjvm_6\lib\jvmx.jar;E:\usr\sap\J73\J02\exe\sapjvm_6\lib\jvmx_tools.jar;E:\usr\sap\J73\J02\exe\jre\lib\iqlib.jar;E:\usr\sap\J73\J02\exe\sapjvm_6\lib\tools.jar;E:\usr\sap\J73\J02\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;E:\usr\sap\J73\J02\j2ee\cluster\bin\boot\jaas.jar;E:\usr\sap\J73\J02\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;E:\usr\sap\J73\J02\j2ee\cluster\bin\boot\memoryanalyzer.jar

F    arg[28] = -Djava.library.path=E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin\server;E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin;E:\usr\sap\J73\J02\j2ee\os_libs;E:\usr\sap\J73\J02\exe\sapjvm_6\bin;E:\usr\sap\J73\J02\exe;C:\Program Files (x86)\Intel\iCLS Client;C:\Program Files\Intel\iCLS Client;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE;C:\Program Files

(x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn;E:\usr\sap\J73\SYS\exe\uc\NTAMD64

F    arg[29] = -XX:PermSize=1024m

F    arg[30] = -Xmx4096m

F    arg[31] = -XX:MaxNewSize=1365m

F    arg[32] = -XX:MaxPermSize=1024m

F    arg[33] = -Xms4096m

F    arg[34] = -XX:NewSize=1365m

F    arg[35] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy

F    arg[36] = -Djavax.management.builder.initial=com.sap.pj.jmx.server.interceptor.InterceptorChainBuilder

F    arg[37] = -Djmx.invoke.getters=true

F    arg[38] = -Djava.security.policy=./../bin/kernel/java.policy

F    arg[39] = -Djava.security.egd=file:/dev/urandom

F    arg[40] = -Djava.awt.headless=true

F    arg[41] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy

F    arg[42] = -Drdbms.driverLocation=E:\usr\sap\J73\J02\exe\mssjdbc\jdbc4\sqljdbc4.jar

F    arg[43] = -Djava.io.tmpdir=./temp

F    arg[44] = -Dsun.lang.ClassLoader.allowArraySyntax=true

F    arg[45] = -Djava.protocol.handler.pkgs=com.sap.engine.httpdsrclient.protocols|iaik.protocol

F    arg[46] = -Dnetworkaddress.cache.ttl=10

F    arg[47] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler

F    arg[48] = -Djco.jarm=1

F    arg[49] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy

F    arg[50] = -XX:+UseConcMarkSweepGC

F    arg[51] = -XX:TargetSurvivorRatio=90

F    arg[52] = -verbose:gc

F    arg[53] = -XX:+DumpDetailedClassStatisticOnOutOfMemory

F    arg[54] = -XX:+PrintGCDetails

F    arg[55] = -XX:MaxErrorQueueLength=200

F    arg[56] = -XX:+PrintGCTimeStamps

F    arg[57] = -XX:+DisableExplicitGC

F    arg[58] = -XX:SoftRefLRUPolicyMSPerMB=1

F    arg[59] = -XX:-StringInternTableInPermGen

F    arg[60] = -XX:SurvivorRatio=6

F    arg[61] = -Xss2m

F    arg[62] = -XX:+HeapDumpOnOutOfMemoryError

F    arg[63] = -XX:HeapDumpPath=OOM.hprof

F    arg[64] = -XX:-TraceClassUnloading

F  ignore unrecognized options : no

F  ********************************************************************************

J  JVMX version - Dec  5 2012 00:34:13 - 61_REL - optU - windows amd64 - 6 - bas2:184594 (mixed mode)

J  (CompilerOracle read from file E:\usr\sap\J73\J02\exe\sapjvm_6\jre\.hotspot_compiler)

F  [Thr 8020] *** LOG => SfCJavaVm: Java VM started.

F  ********************************************************************************

F  Main method call:

F  com/sap/engine/boot/Start.main()

F  ********************************************************************************

J 

J Sun Feb 17 14:06:59 2013

J  1.682: [GC 1.682: [ParNew: 1048320K->5859K(1223040K), 0.0227028 secs] 1048326K->5866K(4019584K), 0.0227889 secs] [Times: user=0.13 sys=0.00, real=0.02 secs]

F 

F [Thr 8020] Sun Feb 17 14:06:59 2013

F  [Thr 8020] *** LOG => State changed from 0 (Initial) to 1 (Waiting to start).

F  [Thr 8020] *** LOG    state real time: 2.879 CPU time: 0.452 sys, 4.617 usr

F  [Thr 8020] *** LOG    total real time: 2.879 CPU time: 0.452 sys, 4.617 usr

F  [Thr 8020]

F  [Thr 8020] *** LOG => State changed from 1 (Waiting to start) to 2 (Starting framework).

F  [Thr 8020] *** LOG    state real time: 0.001 CPU time: 0.000 sys, 0.000 usr

F  [Thr 8020] *** LOG    total real time: 2.880 CPU time: 0.452 sys, 4.617 usr

F  [Thr 8020]

J 

J Sun Feb 17 14:07:07 2013

J  Heap

J   par new generation   reserved 1397760K, committed 1397760K, used 850721K [0x0000000180010000, 0x00000001d5510000, 0x00000001d5510000)

J    eden space 1048320K,  80% used [0x0000000180010000, 0x00000001b391f768, 0x00000001bffd0000)

J    from space 174720K,   3% used [0x00000001caa70000, 0x00000001cb028e18, 0x00000001d5510000)

J    to   space 174720K,   0% used [0x00000001bffd0000, 0x00000001bffd0000, 0x00000001caa70000)

J   concurrent mark-sweep generation reserved 2796544K, committed 2796544K, used 927K [0x00000001d5510000, 0x0000000280010000, 0x0000000280010000)

J   concurrent-mark-sweep perm gen reserved 1048576K, committed 1048576K, used 54103K [0x0000000280010000, 0x00000002c0010000, 0x00000002c0010000)

F 

F [Thr 8628] Sun Feb 17 14:07:08 2013

F  [Thr 8628] *** LOG => SfCJavaVm: exit hook is called. (rc = 2150)

F 

F  ********************************************************************************

F  *** ERROR => Java node 'server0' terminated with exit code 2150.

F  ***

F  *** Please see section 'Java program exit codes'

F  *** in SAP Note 1316652 for additional information and trouble shooting advice.

F  ********************************************************************************

F 

F  [Thr 8628] *** LOG => exiting (exitcode 2150, retcode 1).

M  [Thr 8628] CCMS: CCMS Monitoring Cleanup finished successfully.

---------------------------------------------------

trc file: "dev_server0", trc level: 1, release: "720"

---------------------------------------------------

sysno      02

sid        J73

systemid   562 (PC with Windows NT)

relno      7200

patchlevel 0

patchno    63

intno      20020600

make       multithreaded, Unicode, 64 bit, optimized

profile    \\\sapmnt\J73\SYS\profile\J73_J02_

pid        5852

*

*  ACTIVE TRACE LEVEL           1

*  ACTIVE TRACE COMPONENTS      All, egi

*

Sun Feb 17 14:07:18 2013

*

*  trace logging activated, max size = 52428800 bytes, 2 versions

*

arguments :

  arg[ 0] : E:\usr\sap\J73\J02\exe\jstart.EXE

  arg[ 1] : -appTrc

  arg[ 2] : -nodeId=2

  arg[ 3] : pf=\\\sapmnt\J73\SYS\profile\J73_J02_

  arg[ 4] : -DSAPINFO=J73_02_server0

  arg[ 5] : -hostvm

  arg[ 6] : -nodeName=ID22924050

  arg[ 7] : -file=E:\usr\sap\J73\J02\j2ee\cluster\instance.properties

  arg[ 8] : -jvmFile=E:\usr\sap\J73\J02\work\jstart.jvm

  arg[ 9] : -traceFile=E:\usr\sap\J73\J02\work\dev_server0

  arg[10] : -javaOutFile=E:\usr\sap\J73\J02\work\jvm_server0.out

F 

F Sun Feb 17 14:07:18 2013

F  ********************************************************************************

F  Java environment properties

F    root directory    : E:\usr\sap\J73\J02\exe\sapjvm_6

F    vendor            : SAP AG

F    version           : 1.6.0_37

F    cpu               : amd64

F    java vm type      : server

F    java vm version   : 6.1.045 21.1-b06

F    jvm library name  : jvm.dll

F    library path      : E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin\server;E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin

F    executable path   : E:\usr\sap\J73\J02\exe\sapjvm_6\bin

F    SAP extensions    : available

F  ********************************************************************************

I  [Thr 8844] MtxInit: 10002 0 2

I  [Thr 8844] MPI: dynamic quotas disabled.

I  [Thr 8844] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%

M  [Thr 8844] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)

M  [Thr 8844] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.

M  [Thr 8844] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.

M  [Thr 8844] CCMS: CCMS Monitoring Initialization finished, rc=0.

F 

F Sun Feb 17 14:07:18 2013

F  ********************************************************************************

F  SAP Java VM arguments:

F    arg[ 0] = vfprintf

F    arg[ 1] = abort

F    arg[ 2] = exit

F    arg[ 3] = -XmonGcCallback

F    arg[ 4] = -XdebugStateChangeCallback

F    arg[ 5] = -DSAPJStartVersion=720, patch 401, changelist 0, NTAMD64, optU (EXT) (Jan 16 2013, 16:44:32)

F    arg[ 6] = -Xjvmx

F    arg[ 7] = -XsapSystem:02

F    arg[ 8] = -DSAPSTARTUP=1

F    arg[ 9] = -DSAPSYSTEM=02

F    arg[10] = -DSAPSYSTEMNAME=J73

F    arg[11] = -DSAPMYNAME=_J73_02

F    arg[12] = -DSAPDBHOST=

F    arg[13] = -DSAPINFO=J73_02_server0

F    arg[14] = -Dj2ee.dbhost=

F    arg[15] = -Dsun.java.launcher=jstart

F    arg[16] = -Dsun.java.command=com.sap.engine.boot.Start 

F    arg[17] = -Djstartup.mode=JSTART

F    arg[18] = -Djstartup.whoami=server

F    arg[19] = -Djstartup.ownProcessId=5852

F    arg[20] = -Djstartup.ownHardwareId=R0115937657

F    arg[21] = -Djstartup.debuggable=yes

F    arg[22] = -DLoadBalanceRestricted=no

F    arg[23] = -XdebugPortRange:50221-50221

F    arg[24] = -Denv.class.path=

F    arg[25] = -Dsys.global.dir=E:\usr\sap\J73\SYS\global

F    arg[26] = -Dapplication.home=E:\usr\sap\J73\J02\exe

F    arg[27] = -Djava.class.path=E:\usr\sap\J73\J02\exe\jstart71.jar;E:\usr\sap\J73\J02\exe\sapjvm_6\lib\jvmx.jar;E:\usr\sap\J73\J02\exe\sapjvm_6\lib\jvmx_tools.jar;E:\usr\sap\J73\J02\exe\jre\lib\iqlib.jar;E:\usr\sap\J73\J02\exe\sapjvm_6\lib\tools.jar;E:\usr\sap\J73\J02\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;E:\usr\sap\J73\J02\j2ee\cluster\bin\boot\jaas.jar;E:\usr\sap\J73\J02\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;E:\usr\sap\J73\J02\j2ee\cluster\bin\boot\memoryanalyzer.jar

F    arg[28] = -Djava.library.path=E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin\server;E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin;E:\usr\sap\J73\J02\j2ee\os_libs;E:\usr\sap\J73\J02\exe\sapjvm_6\bin;E:\usr\sap\J73\J02\exe;C:\Program Files (x86)\Intel\iCLS Client;C:\Program Files\Intel\iCLS Client;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE;C:\Program Files

(x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn;E:\usr\sap\J73\SYS\exe\uc\NTAMD64

F    arg[29] = -XX:PermSize=1024m

F    arg[30] = -Xmx4096m

F    arg[31] = -XX:MaxNewSize=1365m

F    arg[32] = -XX:MaxPermSize=1024m

F    arg[33] = -Xms4096m

F    arg[34] = -XX:NewSize=1365m

F    arg[35] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy

F    arg[36] = -Djavax.management.builder.initial=com.sap.pj.jmx.server.interceptor.InterceptorChainBuilder

F    arg[37] = -Djmx.invoke.getters=true

F    arg[38] = -Djava.security.policy=./../bin/kernel/java.policy

F    arg[39] = -Djava.security.egd=file:/dev/urandom

F    arg[40] = -Djava.awt.headless=true

F    arg[41] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy

F    arg[42] = -Drdbms.driverLocation=E:\usr\sap\J73\J02\exe\mssjdbc\jdbc4\sqljdbc4.jar

F    arg[43] = -Djava.io.tmpdir=./temp

F    arg[44] = -Dsun.lang.ClassLoader.allowArraySyntax=true

F    arg[45] = -Djava.protocol.handler.pkgs=com.sap.engine.httpdsrclient.protocols|iaik.protocol

F    arg[46] = -Dnetworkaddress.cache.ttl=10

F    arg[47] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler

F    arg[48] = -Djco.jarm=1

F    arg[49] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy

F    arg[50] = -XX:+UseConcMarkSweepGC

F    arg[51] = -XX:TargetSurvivorRatio=90

F    arg[52] = -verbose:gc

F    arg[53] = -XX:+DumpDetailedClassStatisticOnOutOfMemory

F    arg[54] = -XX:+PrintGCDetails

F    arg[55] = -XX:MaxErrorQueueLength=200

F    arg[56] = -XX:+PrintGCTimeStamps

F    arg[57] = -XX:+DisableExplicitGC

F    arg[58] = -XX:SoftRefLRUPolicyMSPerMB=1

F    arg[59] = -XX:-StringInternTableInPermGen

F    arg[60] = -XX:SurvivorRatio=6

F    arg[61] = -Xss2m

F    arg[62] = -XX:+HeapDumpOnOutOfMemoryError

F    arg[63] = -XX:HeapDumpPath=OOM.hprof

F    arg[64] = -XX:-TraceClassUnloading

F  ignore unrecognized options : no

F  ********************************************************************************

J  JVMX version - Dec  5 2012 00:34:13 - 61_REL - optU - windows amd64 - 6 - bas2:184594 (mixed mode)

J  (CompilerOracle read from file E:\usr\sap\J73\J02\exe\sapjvm_6\jre\.hotspot_compiler)

F 

F [Thr 8788] Sun Feb 17 14:07:19 2013

F  [Thr 8788] *** LOG => SfCJavaVm: Java VM started.

F  ********************************************************************************

F  Main method call:

F  com/sap/engine/boot/Start.main()

F  ********************************************************************************

J 

J Sun Feb 17 14:07:20 2013

J  1.646: [GC 1.646: [ParNew: 1048320K->5989K(1223040K), 0.0247252 secs] 1048326K->5995K(4019584K), 0.0248185 secs] [Times: user=0.11 sys=0.01, real=0.03 secs]

F 

F [Thr 8788] Sun Feb 17 14:07:21 2013

F  [Thr 8788] *** LOG => State changed from 0 (Initial) to 1 (Waiting to start).

F  [Thr 8788] *** LOG    state real time: 2.869 CPU time: 0.499 sys, 4.492 usr

F  [Thr 8788] *** LOG    total real time: 2.869 CPU time: 0.499 sys, 4.492 usr

F  [Thr 8788]

F  [Thr 8788] *** LOG => State changed from 1 (Waiting to start) to 2 (Starting framework).

F  [Thr 8788] *** LOG    state real time: 0.000 CPU time: 0.000 sys, 0.000 usr

F  [Thr 8788] *** LOG    total real time: 2.869 CPU time: 0.499 sys, 4.492 usr

F  [Thr 8788]

J 

J Sun Feb 17 14:07:29 2013

J  Heap

J   par new generation   reserved 1397760K, committed 1397760K, used 870833K [0x0000000180010000, 0x00000001d5510000, 0x00000001d5510000)

J    eden space 1048320K,  82% used [0x0000000180010000, 0x00000001b4ca3098, 0x00000001bffd0000)

J    from space 174720K,   3% used [0x00000001caa70000, 0x00000001cb049438, 0x00000001d5510000)

J    to   space 174720K,   0% used [0x00000001bffd0000, 0x00000001bffd0000, 0x00000001caa70000)

J   concurrent mark-sweep generation reserved 2796544K, committed 2796544K, used 926K [0x00000001d5510000, 0x0000000280010000, 0x0000000280010000)

J   concurrent-mark-sweep perm gen reserved 1048576K, committed 1048576K, used 54100K [0x0000000280010000, 0x00000002c0010000, 0x00000002c0010000)

F 

F [Thr 8840] Sun Feb 17 14:07:30 2013

F  [Thr 8840] *** LOG => SfCJavaVm: exit hook is called. (rc = 2150)

F 

F  ********************************************************************************

F  *** ERROR => Java node 'server0' terminated with exit code 2150.

F  ***

F  *** Please see section 'Java program exit codes'

F  *** in SAP Note 1316652 for additional information and trouble shooting advice.

F  ********************************************************************************

F 

F  [Thr 8840] *** LOG => exiting (exitcode 2150, retcode 1).

M  [Thr 8840] CCMS: CCMS Monitoring Cleanup finished successfully.

dev_deployment log

---------------------------------------------------

trc file: "dev_deployment", trc level: 1, release: "720"

---------------------------------------------------

sysno      02

sid        J73

systemid   562 (PC with Windows NT)

relno      7200

patchlevel 0

patchno    63

intno      20020600

make       multithreaded, Unicode, 64 bit, optimized

profile    \\\sapmnt\J73\SYS\profile\J73_J02_

pid        3832

*

*  ACTIVE TRACE LEVEL           1

*  ACTIVE TRACE COMPONENTS      All, egi

*

Sun Feb 17 14:06:06 2013

*

*  trace logging activated, max size = 52428800 bytes, 2 versions

*

arguments :

  arg[ 0] : E:\usr\sap\J73\J02\exe\jstart.EXE

  arg[ 1] : -appTrc

  arg[ 2] : -nodeId=0

  arg[ 3] : pf=\\\sapmnt\J73\SYS\profile\J73_J02_

  arg[ 4] : -hostvm

  arg[ 5] : -nodeName=deployment

  arg[ 6] : -file=E:\usr\sap\J73\J02\exe\startup.properties

  arg[ 7] : -jvmFile=E:\usr\sap\J73\J02\work\jstart.jvm

  arg[ 8] : -traceFile=E:\usr\sap\J73\J02\work\dev_deployment

  arg[ 9] : -javaOutFile=E:\usr\sap\J73\J02\work\jvm_deployment.out

F 

F Sun Feb 17 14:06:06 2013

F  ********************************************************************************

F  Java environment properties

F    root directory    : E:\usr\sap\J73\J02\exe\sapjvm_6

F    vendor            : SAP AG

F    version           : 1.6.0_37

F    cpu               : amd64

F    java vm type      : server

F    java vm version   : 6.1.045 21.1-b06

F    jvm library name  : jvm.dll

F    library path      : E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin\server;E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin

F    executable path   : E:\usr\sap\J73\J02\exe\sapjvm_6\bin

F    SAP extensions    : available

F  ********************************************************************************

I  [Thr 4256] MtxInit: 10000 0 2

M  [Thr 4256] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)

M  [Thr 4256] CCMS: Initialized monitoring segment of size 60000000.

M  [Thr 4256] CCMS: Initialized CCMS Headers in the shared monitoring segment.

M  [Thr 4256] CCMS: Checking Downtime Configuration of Monitoring Segment.

M  [Thr 4256] CCMS: AlMsUpload called by wp 1004.

M  [Thr 4256] CCMS: AlMsUpload successful for E:\usr\sap\J73\J02\log\ALMTTREE.DAT (394 MTEs).

M  [Thr 4256] CCMS: CCMS Monitoring Initialization finished, rc=0.

F 

F Sun Feb 17 14:06:06 2013

F  ********************************************************************************

F  SAP Java VM arguments:

F    arg[ 0] = vfprintf

F    arg[ 1] = abort

F    arg[ 2] = exit

F    arg[ 3] = -XmonGcCallback

F    arg[ 4] = -XdebugStateChangeCallback

F    arg[ 5] = -DSAPJStartVersion=720, patch 401, changelist 0, NTAMD64, optU (EXT) (Jan 16 2013, 16:44:32)

F    arg[ 6] = -verbose:gc

F    arg[ 7] = -XX:+HeapDumpOnOutOfMemoryError

F    arg[ 8] = -DSAPSTARTUP=1

F    arg[ 9] = -DSAPSYSTEM=02

F    arg[10] = -DSAPSYSTEMNAME=J73

F    arg[11] = -DSAPMYNAME=_J73_02

F    arg[12] = -DSAPDBHOST=

F    arg[13] = -DSAPINFO=J73_02_deployment

F    arg[14] = -Dj2ee.dbhost=

F    arg[15] = -Dsun.java.launcher=jstart

F    arg[16] = -Dsun.java.command=com.sap.engine.offline.OfflineToolStart com.sap.engine.services.dc.cm.offline_phase.Runner ./bootstrap

F    arg[17] = -Djstartup.mode=JSTART

F    arg[18] = -Djstartup.whoami=bootstrap

F    arg[19] = -Djstartup.ownProcessId=3832

F    arg[20] = -Djstartup.ownHardwareId=R0115937657

F    arg[21] = -Djstartup.debuggable=no

F    arg[22] = -DLoadBalanceRestricted=no

F    arg[23] = -Denv.class.path=

F    arg[24] = -Dsys.global.dir=E:\usr\sap\J73\SYS\global

F    arg[25] = -Dapplication.home=E:\usr\sap\J73\J02\exe

F    arg[26] = -Djava.class.path=E:\usr\sap\J73\J02\exe\jstart71.jar;E:\usr\sap\J73\J02\exe\sapjvm_6\lib\jvmx.jar;E:\usr\sap\J73\J02\exe\sapjvm_6\lib\jvmx_tools.jar;E:\usr\sap\J73\J02\exe\jre\lib\iqlib.jar;E:\usr\sap\J73\J02\exe\sapjvm_6\lib\tools.jar;.\bootstrap\sap.com~tc~bl~offline_launcher~impl.jar;E:\usr\sap\J73\J02\exe\jstartupapi.jar;E:\usr\sap\J73\J02\exe\jstartupimpl.jar

F    arg[27] = -Djava.library.path=E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin\server;E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin;E:\usr\sap\J73\J02\j2ee\os_libs;E:\usr\sap\J73\J02\exe\sapjvm_6\bin;E:\usr\sap\J73\J02\exe;C:\Program Files (x86)\Intel\iCLS Client;C:\Program Files\Intel\iCLS Client;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn;E:\usr\sap\J73\SYS\exe\uc\NTAMD64

F    arg[28] = -Xmx512m

F    arg[29] = -Xss2097152

F  ignore unrecognized options : no

F  ********************************************************************************

F  [Thr 7828] *** LOG => SfCJavaVm: Java VM started.

F  ********************************************************************************

F  Main method call:

F  com/sap/engine/offline/OfflineToolStart.main()

F    arg[ 0] = com.sap.engine.services.dc.cm.offline_phase.Runner

F    arg[ 1] = ./bootstrap

F  ********************************************************************************

J 

J Sun Feb 17 14:06:07 2013

J  [GC 4032K->1300K(9984K), 0.0034730 secs]

J  [GC 5332K->3624K(9984K), 0.0024289 secs]

J  [Full GC 3624K->3599K(16512K), 0.0101467 secs]

J  [GC 7591K->5849K(16512K), 0.0020756 secs]

J  [GC 9881K->8234K(19200K), 0.0085805 secs]

J  [GC 14938K->12222K(19200K), 0.0026438 secs]

J  [Full GC 12222K->8765K(28544K), 0.0159562 secs]

F 

F [Thr 7828] Sun Feb 17 14:06:07 2013

F  [Thr 7828] *** LOG => State changed from 0 (Initial) to 2 (Starting framework).

F  [Thr 7828] *** LOG    state real time: 1.879 CPU time: 0.218 sys, 2.667 usr

F  [Thr 7828] *** LOG    total real time: 1.879 CPU time: 0.218 sys, 2.667 usr

F  [Thr 7828]

J  [GC 15485K->11688K(34048K), 0.0024930 secs]

F  [Thr 7828] *** LOG => State changed from 2 (Starting framework) to 5 (Stopping).

F  [Thr 7828] *** LOG    state real time: 0.143 CPU time: 0.015 sys, 0.249 usr

F  [Thr 7828] *** LOG    total real time: 2.022 CPU time: 0.234 sys, 2.917 usr

F  [Thr 7828]

F  [Thr 6208] *** LOG => SfCJavaVm: exit hook is called. (rc = 0)

F  [Thr 6208] *** LOG => exiting (exitcode 0, retcode 0).

M  [Thr 6208] CCMS: CCMS Monitoring Cleanup finished successfully.

dev_bootsrtap log

---------------------------------------------------

trc file: "dev_bootstrap", trc level: 1, release: "720"

---------------------------------------------------

sysno      02

sid        J73

systemid   562 (PC with Windows NT)

relno      7200

patchlevel 0

patchno    63

intno      20020600

make       multithreaded, Unicode, 64 bit, optimized

profile    \\\sapmnt\J73\SYS\profile\J73_J02_

pid        5388

*

*  ACTIVE TRACE LEVEL           1

*  ACTIVE TRACE COMPONENTS      All, egi

*

Sun Feb 17 14:06:08 2013

*

*  trace logging activated, max size = 52428800 bytes, 2 versions

*

arguments :

  arg[ 0] : E:\usr\sap\J73\J02\exe\jstart.EXE

  arg[ 1] : -appTrc

  arg[ 2] : -nodeId=0

  arg[ 3] : pf=\\\sapmnt\J73\SYS\profile\J73_J02_

  arg[ 4] : -hostvm

  arg[ 5] : -nodeName=bootstrap

  arg[ 6] : -file=E:\usr\sap\J73\J02\exe\startup.properties

  arg[ 7] : -jvmFile=E:\usr\sap\J73\J02\work\jstart.jvm

  arg[ 8] : -traceFile=E:\usr\sap\J73\J02\work\dev_bootstrap

  arg[ 9] : -javaOutFile=E:\usr\sap\J73\J02\work\jvm_bootstrap.out

F 

F Sun Feb 17 14:06:08 2013

F  ********************************************************************************

F  Java environment properties

F    root directory    : E:\usr\sap\J73\J02\exe\sapjvm_6

F    vendor            : SAP AG

F    version           : 1.6.0_37

F    cpu               : amd64

F    java vm type      : server

F    java vm version   : 6.1.045 21.1-b06

F    jvm library name  : jvm.dll

F    library path      : E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin\server;E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin

F    executable path   : E:\usr\sap\J73\J02\exe\sapjvm_6\bin

F    SAP extensions    : available

F  ********************************************************************************

I  [Thr 3704] MtxInit: 10000 0 2

M  [Thr 3704] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)

M  [Thr 3704] CCMS: Initialized monitoring segment of size 60000000.

M  [Thr 3704] CCMS: Initialized CCMS Headers in the shared monitoring segment.

M  [Thr 3704] CCMS: Checking Downtime Configuration of Monitoring Segment.

M  [Thr 3704] CCMS: AlMsUpload called by wp 1004.

M  [Thr 3704] CCMS: AlMsUpload successful for E:\usr\sap\J73\J02\log\ALMTTREE.DAT (394 MTEs).

M  [Thr 3704] CCMS: CCMS Monitoring Initialization finished, rc=0.

F 

F Sun Feb 17 14:06:08 2013

F  ********************************************************************************

F  SAP Java VM arguments:

F    arg[ 0] = vfprintf

F    arg[ 1] = abort

F    arg[ 2] = exit

F    arg[ 3] = -XmonGcCallback

F    arg[ 4] = -XdebugStateChangeCallback

F    arg[ 5] = -DSAPJStartVersion=720, patch 401, changelist 0, NTAMD64, optU (EXT) (Jan 16 2013, 16:44:32)

F    arg[ 6] = -verbose:gc

F    arg[ 7] = -XX:+HeapDumpOnOutOfMemoryError

F    arg[ 8] = -DSAPSTARTUP=1

F    arg[ 9] = -DSAPSYSTEM=02

F    arg[10] = -DSAPSYSTEMNAME=J73

F    arg[11] = -DSAPMYNAME=_J73_02

F    arg[12] = -DSAPDBHOST=

F    arg[13] = -DSAPINFO=J73_02_bootstrap

F    arg[14] = -Dj2ee.dbhost=

F    arg[15] = -Dsun.java.launcher=jstart

F    arg[16] = -Dsun.java.command=com.sap.engine.offline.OfflineToolStart com.sap.engine.bootstrap.Bootstrap ./bootstrap

F    arg[17] = -Djstartup.mode=JSTART

F    arg[18] = -Djstartup.whoami=bootstrap

F    arg[19] = -Djstartup.ownProcessId=5388

F    arg[20] = -Djstartup.ownHardwareId=R0115937657

F    arg[21] = -Djstartup.debuggable=no

F    arg[22] = -DLoadBalanceRestricted=no

F    arg[23] = -Denv.class.path=

F    arg[24] = -Dsys.global.dir=E:\usr\sap\J73\SYS\global

F    arg[25] = -Dapplication.home=E:\usr\sap\J73\J02\exe

F    arg[26] = -Djava.class.path=E:\usr\sap\J73\J02\exe\jstart71.jar;E:\usr\sap\J73\J02\exe\sapjvm_6\lib\jvmx.jar;E:\usr\sap\J73\J02\exe\sapjvm_6\lib\jvmx_tools.jar;E:\usr\sap\J73\J02\exe\jre\lib\iqlib.jar;E:\usr\sap\J73\J02\exe\sapjvm_6\lib\tools.jar;.\bootstrap\sap.com~tc~bl~offline_launcher~impl.jar

F    arg[27] = -Djava.library.path=E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin\server;E:\usr\sap\J73\J02\exe\sapjvm_6\jre\bin;E:\usr\sap\J73\J02\j2ee\os_libs;E:\usr\sap\J73\J02\exe\sapjvm_6\bin;E:\usr\sap\J73\J02\exe;C:\Program Files (x86)\Intel\iCLS Client;C:\Program Files\Intel\iCLS Client;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn;E:\usr\sap\J73\SYS\exe\uc\NTAMD64

F    arg[28] = -Xmx3072m

F    arg[29] = -Xss2097152

F  ignore unrecognized options : no

F  ********************************************************************************

F 

F [Thr 7560] Sun Feb 17 14:06:09 2013

F  [Thr 7560] *** LOG => SfCJavaVm: Java VM started.

F  ********************************************************************************

F  Main method call:

F  com/sap/engine/offline/OfflineToolStart.main()

F    arg[ 0] = com.sap.engine.bootstrap.Bootstrap

F    arg[ 1] = ./bootstrap

F  ********************************************************************************

J 

J Sun Feb 17 14:06:09 2013

J  [GC 4032K->1296K(9984K), 0.0067963 secs]

J  [GC 5328K->3611K(14016K), 0.0022383 secs]

J  [Full GC 3611K->3580K(20352K), 0.0094016 secs]

J  [GC 11644K->8273K(20352K), 0.0036331 secs]

J  [Full GC 8273K->6986K(29504K), 0.0151545 secs]

J  [GC 15050K->11806K(32000K), 0.0025365 secs]

F  [Thr 7560] *** LOG => State changed from 0 (Initial) to 2 (Starting framework).

F  [Thr 7560] *** LOG    state real time: 1.783 CPU time: 0.280 sys, 2.527 usr

F  [Thr 7560] *** LOG    total real time: 1.783 CPU time: 0.280 sys, 2.527 usr

F  [Thr 7560]

J  [GC 22366K->15497K(34880K), 0.0046289 secs]

J 

J Sun Feb 17 14:06:10 2013

J  [GC 28937K->17203K(40768K), 0.0033324 secs]

J  [GC 30771K->17412K(40640K), 0.0031309 secs]

J  [GC 30980K->17622K(43008K), 0.0027707 secs]

J  [GC 34262K->18178K(43264K), 0.0047369 secs]

J 

J Sun Feb 17 14:06:11 2013

J  [GC 34818K->19957K(45120K), 0.0076805 secs]

F 

F [Thr 7560] Sun Feb 17 14:06:11 2013

F  [Thr 7560] *** LOG => State changed from 2 (Starting framework) to 3 (Running).

F  [Thr 7560] *** LOG    state real time: 1.712 CPU time: 0.062 sys, 4.336 usr

F  [Thr 7560] *** LOG    total real time: 3.495 CPU time: 0.343 sys, 6.864 usr

F  [Thr 7560]

J 

J Sun Feb 17 14:06:12 2013

J  [GC 38645K->21953K(45568K), 0.0096613 secs]

J  [GC 40641K->24658K(47360K), 0.0084375 secs]

J  [Full GC 24658K->18241K(61696K), 0.0427456 secs]

F 

F [Thr 7560] Sun Feb 17 14:06:12 2013

F  [Thr 7560] *** LOG => State changed from 3 (Running) to 5 (Stopping).

F  [Thr 7560] *** LOG    state real time: 1.352 CPU time: 0.093 sys, 3.369 usr

F  [Thr 7560] *** LOG    total real time: 4.847 CPU time: 0.436 sys, 10.233 usr

F  [Thr 7560]

F  [Thr 988] *** LOG => SfCJavaVm: exit hook is called. (rc = 0)

F  [Thr 988] *** LOG => exiting (exitcode 0, retcode 0).

M  [Thr 988] CCMS: CCMS Monitoring Cleanup finished successfully.

urgent help required,

thanks in advance,

Regards,

rohi

Hi!

I am about to copy existing SAP system by overwriting this with another SAP system via system copy.

(e.g. system ABC will be overwritten by system ABD (system export) and still called as ABC).

Question

Which option within tcode SE06 should I choose during the initialization of TMS and what are the differencees?

a) system copy or

b) installation 

Any helpful information will be very appreciated!

Hello,

I am aware that miniSAP is a stripped down version without modules.

I want to understand which transactions are available before I go through the trouble of installing it. Is there a list?

Is it for example possible to build roles via PFCG and assign those to test users via SU01?

Cheers,

Peter

I have query about developers key,

The developer key is a combination of your installation number, your license key and the user name.

You need this for each person that will make changes (Dictionary or programs) in the system.

For example a single installation numbers can exists with more than one system suppose 123456789 number is same for AD1,bD1,CD1 systems then the user can use the same key for all the systems (if DEVACCESS table is maintained also) ?

1.After a developer key is generated in the SAP market place then how it is maintained in the table DEVACCESS. Is it possible with SE16N ?

   if yes, then we need to register in SCCR keys ?

2. Developer key for a user is can be deleted?

Dear All,

We have successfully generated a PAT File. but unable to find it so that we could convert it and install in the Sandbox system and test.

Could anyone help us here.

i have attached the screen shot of the registering the PAT File.

Hi,

We have a background Job for the RSSTAT26 program. We want to save the spool content of this BG Job automatically once the Job finishes.

We don't want to create any ABAP program for this.

Is there any solution other then ABAP program to automate exporting of the spool content on the desktop of the BG Job?

Hi,

Can I use LSMW to do mass change of Status to TECO projects, WBS's, Networks and Network activities in Project Systems?  If so, I could use some help with how to set up a program using LSMW to do that please.

Thanks,

Donna Price

Hi all,

I know this, to install PAT file we have to convert it to SAR File and navigate to Tcode SAINT and install manually.

but my question is can we install the PAT file remotely(automatically) with the help of a program or something else instead of manually doing it?

Regards

Chinta

Hello Experts,

we have a SAP PI system to integrate SAP R/3 with external applications and recently we are facing a problem with inactive sessions. There's a new application we are setting up that consumes a webservice published by this SAP PI system. The scenario is SOAP --> PI --> PROXY. What we have noticed is that when the application sends loads of requests sometimes the system fails. This is because we are reaching the maximum number of open sessions in AS Java (1000). Investigating a bit more we found out that the sessions are not "closed" once the communication between the application and SAP PI has finished. Those sessions are open until they are automatically timed-out by the system after 1800 sec.

We have found the notes below in SAPNet:

Note 1363751 - ICM: Java Web sessions are not terminated

Note 1307940 - New HTTP session opened for every web service call

However, none of them are applicable to our system because it is more updated:

SAP PI 7.1 EHP1 SP002

Kernel Patch Level: 87

We have tried to close connections from the application that consumes the webservice but with no success. The sessions remain in the server until they are timed-out. Could you please tell us if this is the normal behavior of an AS Java system? Is this the way it should work? If so, can you tell us how to decrease this timeout so the inactive sessions are cleaned faster? We tried to find it but we didn't manage. Is there any way to close the session once the communication has finished?

Thank you in advance.

Roger Allué i Vall