SAP BI PS - 0ACTY_ELEMT_ATTR datasource
Hi Guru's
In ECC 6.04, the extractor for 0ACTY_ELEMT_ATTR is uable to fetch records thru RSA3 tcode. It shows 0 records found.
Is there any solution for this as I am finding very difficult to generate the daily progress report.
Your prompt response will be highly appreciated.
Thanks in Advance
With Warm Regards
Shivaji Nalawade
Sorry Guru's. I will do the needful.
Thanks and Regards
Shivaji Nalawade
Similar Messages
-
Sap crm(7.0) datasource test extract error
hi,all:
I activate the CRM datasouce 0CRM_CIC_CTI successfully, but when i did the test extract with T-CODE RSA3,THE error happened. the error description in the below:
Update mode F is not supported by the extraction API
Message no. R3011
Diagnosis
The application program for the extraction of the data was called using update mode F. However, this is not supported by the InfoSource.
System Response
The data extraction is terminated.
Procedure
Check the SAP Support Portal for the appropriate Notes and create a customer message if necessary.
what can i do to solve this question?
wish some help.
THANKS VERY MUCH!Hi,
关于CRM datasource的OSS MESSAGE是CRM的支持顾问负责的..
如果您还有疑问，可以告诉我message number, 我可以帮你确认下..
不过如果设计上的确不支持full mode..那支持顾问也无法阿..
祝好..
Vince -
SAP TM - Freight agreement datasource
Hello Gurus!
Somebody knows which datasource I can use for extracting Freight Agreement from SAP TM?
Thanks a lot.Means you want all objects like cube/dso/info objects and all kind stuff?
if yes then please Google search key as "BI Content for SAP Transportation Management (New)".
With sap help link we need to play them by choosing respective hyperlinks from right side area.
Ex: cubes -
Agreement - 0TMS_C25
Transportation Order Planning - 0TMS_C24
from BI content at bw side, try to install thru using grouping options data flow before and after you may get all objects what ever you need.
Multi provider - Agreement - 0TMS_MP25
As stated above you can install from bi content, you will find all source objects. -
Where are BW Datasources physically/actually stored in the SAP system
Hi,
We are making some changes which are to be moved to the BI production system.
There are a couple of concerns which have arised.
So we need to know where all the changes including CMOD changes, SAP notes and BW Datasources are physically stored in the SAP systems.
As far as I understand these changes should be part of the SAP database.
Is that right or is any part of this stored in any filesystem?
Regards,
Rohan.Hi,
Thanks for your response, that clears it up for the ABAP stack.
Would that be the same for both ABAP as well as Java?
As we are having a ABAP+Java stack.
Regards,
Rohan. -
Unable to Log-in *SAP System Message : Error while reading a Dynpro*
Hi,
We are facing issues while logging-in through SAP logon 710.
The system throws an error dialog box with the below message:
SAP System Message : Error while reading a Dynpro
At the OS level Java process server0 is in stop status with exit code -11113. In ABAP WP Table all processes are in wait status.Hi Please find the contents of std_server.out below.
stdout/stderr redirect
node name : server0
pid : 4124
system name : KEC
system nr. : 01
started at : Mon Jul 27 15:44:57 2009
[Thr 5656] MtxInit: -2 0 0
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
SAP J2EE Engine Version 7.00 PatchLevel 110760.44 is starting...
Loading: LogManager ... 250 ms.
Loading: PoolManager ... 0 ms.
Loading: ApplicationThreadManager ... 47 ms.
Loading: ThreadManager ... 16 ms.
Loading: IpVerificationManager ... 0 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 93 ms.
Loading: LockingManager ... 32 ms.
Loading: ConfigurationManager ... 1032 ms.
Loading: LicensingManager ... 0 ms.
Loading: CacheManager ... 93 ms.
Loading: ServiceManager ...
Loading services.:
Service runtimeinfo started. (16 ms).
Service cross started. (31 ms).
Service file started. (31 ms).
Service memory started. (31 ms).
Service timeout started. (16 ms).
Service trex.service started. (32 ms).
Service userstore started. (0 ms).
Service jmx_notification started. (15 ms).
Service p4 started. (62 ms).
Service classpath_resolver started. (16 ms).
Service deploy started. (3722 ms).
Service MigrationService started. (31 ms).
Service bimmrdeployer started. (0 ms).
Service log_configurator started. (5177 ms).
Service locking started. (0 ms).
Service http started. (126 ms).
Service naming started. (157 ms).
Service failover started. (16 ms).
Service appclient started. (31 ms).
Service javamail started. (47 ms).
Service ts started. (47 ms).
Service jmsconnector started. (47 ms).
Service licensing started. (15 ms).
Service connector started. (93 ms).
Service iiop started. (94 ms).
Service configuration started. (16 ms).
Service webservices started. (265 ms).
Service dbpool started. (1204 ms).
Service UT started. (0 ms).
Jul 27, 2009 3:45:09 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_54] Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: " Error while reading a dynpro ". This message is critical if it appears during the startup of the AS Java.
Jul 27, 2009 3:45:09 PM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_54] Fatal:
service com.sap.security.core.ume.service ================= ERROR =================
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Error while reading a dynpro
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Error while reading a dynpro
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
... 6 more
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Error while reading a dynpro
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Error while reading a dynpro
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Jul 27, 2009 3:45:09 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_54] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started. -
Com.sap.security.core.ume.service failed. J2EE Engine cannot be started
Hi,
I have configured SNC on NetWeaver 7.0 (ABAP+JAVA) System on Windows 2003 Server with MS-SQL 2005 Database.
After the SNC configuration restarted the Server but the JAVA Server process is going down with EXIT Code -11113. The SNC Configuration is working fine but JAVA is not running. SDM and dispatcher are in green but server process is going gray.
I have checked the log files under C:\usr\sap\SID\DVEBMGS00\j2ee\cluster\server0\log
The following is the part of log file.
#1.5#005056BA6C3F001D0000000F000008D8000489ACAFC86070#1277274683393#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_71##0#0#Error#1#/System/Server#Java###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
[EXCEPTION]
#1#com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: SNC required for this connection
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
... 6 more
#1.5#005056BA6C3F001D00000011000008D8000489ACAFC8628E#1277274683393#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_71##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
Please help me to solve the issue.
Thanks,
Ajay.Hi Tim,
I have configured using Kerberos library for 32 bit on Net Weaver 7.0 with MS SQL 2005 Server on Windows 2003 Server. I didnt change any thing on JAVA side. I have configured as per the Kerberos configuration steps as per below URL
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/44/0ebf6c9b2b0d1ae10000000a114a6b/frameset.htm
The configuration was successful and I am able to login with out asking password, but After the configuration when I have restarted every thing on ABAP side works well but JAVA server process going down with EXIT code -11113. One of the log file contains follows error message.
com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: SNC required for this connection
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Jun 25, 2010 3:05:24 AM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_69] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
One of the line says "SNC required for this connection". What does this mean? What else need to be done for JAVA to communicate with ABAP?
Thanks,
Ajay. -
EP starting failed after switching UM datasource to LDAP
I would like to use Windows 2003 AD as user storage of EP. For this purpose, I completed the necessary configuration steps according to online help but still not able to connect EP to LDAP.
Test button show me that parameters entered in the LDAP configuration tab is correct. But once I change the UM datasource to dataSourceConfiguration_ADS_readonly_db.xml and restart the J2EE server. The application server won't start up successfully. It indicated problems with a yellow flag on the server node. Clicking the processes will display that some processes is running. Trace file outlines problem as below:
Jul 15, 2006 11:22:50... com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: No connection to the ldap server, recheck configuration or availability of directory server
Jul 15, 2006 11:22:50... com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: Server not available,recheck configuration or availability of directory server
Jul 15, 2006 11:22:50... com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: Initialisation of a connection pool failed for UACC please check the configuration or availability of the directory server
Jul 15, 2006 11:22:50... com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: Please recheck the LDAP configuration Initialisation of connection pool failed for UACC
poolname shaw2k99:389_UACC
java.naming.provider.url= ldap://shaw2k99:389/CN%3DUsers%2CDC%3Ddimension%2CDC%3Dcom%2CDC%3Dcn
java.naming.factory.initial= com.sun.jndi.ldap.LdapCtxFactory
java.naming.ldap.version= 3
connection_pool_name= shaw2k99:389_UACC
java.naming.security.authentication= simple
[EXCEPTION: no connection to the ldap server:[LDAP: error code 1 - 00000000: LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece ]]
Jul 15, 2006 11:22:50... com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: DataSource CORP_LDAP:Initialisation of connection manager failed because: Initialisation of connection pool failed for UACC
poolname shaw2k99:389_UACC
java.naming.provider.url= ldap://shaw2k99:389/CN%3DUsers%2CDC%3Ddimension%2CDC%3Dcom%2CDC%3Dcn
java.naming.factory.initial= com.sun.jndi.ldap.LdapCtxFactory
java.naming.ldap.version= 3
connection_pool_name= shaw2k99:389_UACC
java.naming.security.authentication= simple
[EXCEPTION: no connection to the ldap server:[LDAP: error code 1 - 00000000: LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece ]]
Jul 15, 2006 11:22:50... com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: Initialization of UME persistence adapter "CORP_LDAP" failed.
service com.sap.security.core.ume.service ================= ERROR =================
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
com.sap.engine.frame.ServiceException: Initialisation of connection pool failed for UACC
Does anyone have clue on this? Thanks!
My EP version: EP 7.0 SP4
AD version: 2003Hello,
I dont think, that the problem is directly related with the usage of SSL. We dont use SSL and we have the same problem mentioned in the first post of this topic in our portal. We are using EP7 SP8.
The connection tests in the config-tool and in the UME-configuration of the EP indicates us, that the connection to the LDAP-Server is working correct. But when we are restarting the portal, then the following exception appears and the server stops to start:
com.sap.security.core.persistence.datasource.PersistenceException: Initialisation of connection pool failed for UACC
poolname <ip-address>:389_UACC
java.naming.provider.url= ldap:// <ip-address>:389/
java.naming.factory.initial= com.sun.jndi.ldap.LdapCtxFactory
java.naming.ldap.version= 3
com.sun.jndi.ldap.connect.timeout= 25000
connection_pool_name= <ip-address>:389_UACC
java.naming.security.authentication= simple
[EXCEPTION: No connection to the ldap server: [LDAP: error code 1 - 00000000: LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece]]
at com.sap.security.core.persistence.datasource.imp.LDAPConnectionManager.initConnectionPools(LDAPConnectionManager.java:777)
at com.sap.security.core.persistence.datasource.imp.LDAPConnectionManager.initialize(LDAPConnectionManager.java:83)
at com.sap.security.core.persistence.datasource.imp.LDAPPersistence.init(LDAPPersistence.java:453)
Has anyone a hint how to solve our problem?
Regards,
Udo -
Generic Extraction (or) How to use table in R/3 system as datasource in BW?
Hi all,
Hope all are having a great day
Can any1 tell me the steps, for Generic Extraction.
It will be very helpful, if the steps are as much as simpler as posible.
I know to create a simple cube in BW.
I have this much knowledge, depending on this can any1 tell me the steps for Generic Extraction from R/3.
examples wud be vry useful
Regards,
Souravhi,
Maintaining Generic DataSources
Use
Independently of application, you can create and maintain generic DataSources for transaction data, master data attributes or texts from any kinds of transparent tables, database views, InfoSets of the SAP query or using a function module. As a result, you can make use of the generic extraction of data.
Procedure
Creating a Generic DataSource(RSO2)
1. Select the DataSource type and give it a technical name.
2. Choose Create.
The creating a generic DataSource screen appears.
3. Choose an application component to which the DataSource is to be assigned.
4. Enter the descriptive texts. You can choose any text.
5. Choose from which datasets the generic DataSource is to be filled.
a. Choose Extraction from View, if you want to extract data from a transparent table or a database view. Enter the name of the table or the database view.
After generation, you get a DataSource whose extract structure is congruent with the database view or the transparent table view.
For more information about creating and maintaining database views and tables, see the ABAP Dictionary Documentation.
b. Choose Extraction from Query, if you want to use a SAP query InfoSet as the data source. Select the required InfoSet from the InfoSet catalog.
Notes on Extraction Using SAP Query
After generation, you now have a DataSource whose extract structure matches the InfoSet.
For more information about maintaining the InfoSet, see the System Administration documentation.
c. Choose Extraction using FM, if you want to extract data using a function module. Enter the function module and extract structure.
The data must be transferred by the function module in an interface table E_T_DATA.
Interface Description and Extraction Process Flow
For information about the function library, see the ABAP Workbench: Tools documentation.
d. With texts, you also have the option of extraction from domain fixed values.
6. Maintain the settings for delta transfer where appropriate.
7. Choose Save.
When extracting, look at SAP Query: Assigning to a User Group.
Note when extracting from a transparent table or view:
If the extract structure contains a key figure field, that references to a unit of measure or currency unit field, this unit field must appear in the same extract structure as the key figure field.
A screen appears in which you can edit the fields of the extract structure.
8. Editing the DataSource:
 Selection
When scheduling a data request in the BW Scheduler, you can enter the selection criteria for the data transfer. For example, you may want to determine that data requests are only to apply to data from the previous month.
If you set the Selection indicator for a field within the extract structure, the data for this field is transferred in correspondence with the selection criteria in the scheduler.
 Hide field
You should set this indicator to exclude an extract structure field from the data transfer. As a result of your action, the field is no longer made available in BW when setting the transfer rules and generating the transfer structure.
 Inversion
Reverse postings are possible for customer-defined key figures. For this reason, inversion is only possible for certain transaction data DataSources. These include DataSources that have a field that is indicated as an inversion field, for example, the field update mode in the DataSource 0FI_AP_3. If this field has a value, then the data records are interpreted as reverse records in BW.
Set the Inversion indicator if you want to carry out a reverse posting for a customer-defined field (key figure). The value of the key figure is then transferred in inverted form (multiplied by 1) into BW.
 Field only known in exit
You can enhance data by extending the extract structure for a DataSource using fields in append structures.
The indicator Field only known in Exit is set for fields of an append structure. In other words, by default these fields are not passed onto the extractor from the field list and selection table.
Deselect the indicator Field Only Known in Exit to enable the Service API to pass on the append structure field to the extractor together with the fields of the delivered extract structures in the field list as well as in the selection table.
9. Choose DataSource ® Generate.
The DataSource is now saved in the source system.
Maintaining Generic DataSources
Change the DataSource
To change a generic DataSource, in the initial screen of DataSource maintenance, enter the name of the DataSource and choose Change.
You can change the assignment of a DataSource to an application component as well as the texts of a DataSource. Double-clicking on the name of the table, view, InfoSet or extract structure takes you to the appropriate maintenance screen. Here you can make changes required to add new fields. You can fully swap transparent tables and database views, but not InfoSets. If you return to the DataSource maintenance and choose Create, the screen for editing a DataSource appears. To save the DataSource in the SAP source system, choose DataSource ® Generate.
If you want to test extraction in the source system independently of a BW system, choose DataSource ® Test Extraction.
Delta DataSource
In the Change Generic DataSource screen, you can delete any DataSources that are no longer relevant. If you are extracting data from an InfoSet, delete the associated query. If you want to delete a DataSource, this must not be connected to a BW system.
For more information about extracting using SAP Query, see Extraction using the SAP Query.
hope this helps.
assign point if so
partha -
JAVA server stop with 2150 service unavailable in sap pi
Hi,
I am facing issue after failed support patch upgrade in sap pi 7.1 ehp 1.
Java is not starting. Please help log is below.
trc file: "C:\usr\sap\PID\DVEBMGS00\work\dev_server0", trc level: 1, release: "711"
sysno 00
sid PID
systemid 562 (PC with Windows NT)
relno 7110
patchlevel 0
patchno 92
intno 20020600
make multithreaded, Unicode, 64 bit, optimized
profile C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
pid 3228
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS All, egi
Tue Sep 02 02:24:43 2014
* trace logging activated, max size = 52428800 bytes, 2 versions
arguments :
arg[ 0] : C:\usr\sap\PID\DVEBMGS00\exe\jstart.EXE
arg[ 1] : -nodeId=2
arg[ 2] : pf=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
arg[ 3] : -DSAPINFO=PID_00_server0
arg[ 4] : -hostvm
arg[ 5] : -nodeName=ID2463250
arg[ 6] : -file=C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\instance.properties
arg[ 7] : -jvmFile=C:\usr\sap\PID\DVEBMGS00\work\jstart.jvm
arg[ 8] : -traceFile=C:\usr\sap\PID\DVEBMGS00\work\dev_server0
arg[ 9] : -javaOutFile=C:\usr\sap\PID\DVEBMGS00\work\jvm_server0.out
arg[10] : -DSAPSTART=1
arg[11] : -DSAPSYSTEM=00
arg[12] : -DSAPSYSTEMNAME=PID
arg[13] : -DSAPMYNAME=usatlsv117_PID_00
arg[14] : -DSAPPROFILE=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
arg[15] : -DFRFC_FALLBACK=ON
arg[16] : -DFRFC_FALLBACK_HOST=localhost
F
F Tue Sep 02 02:24:43 2014
F ********************************************************************************
F Java environment properties
F root directory : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5
F vendor : SAP AG
F version : 1.5.0_14
F cpu : amd64
F java vm type : server
F java vm version : 5.1.027
F jvm library name : jvm.dll
F library path : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin\server;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin
F executable path : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\bin
F SAP extensions : available
F ********************************************************************************
I
I [Thr 7080] Tue Sep 02 02:24:44 2014
I [Thr 7080] MtxInit: 10002 0 2
I [Thr 7080] MPI: dynamic quotas disabled.
I [Thr 7080] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
M [Thr 7080] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=1002;cur=2048)
M [Thr 7080] CCMS: Detected Double Stack (parameter "rdisp/j2ee_start" is active)
M [Thr 7080] CCMS uses Shared Memory Key 73 for monitoring.
M [Thr 7080] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
M [Thr 7080] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
M [Thr 7080] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
M [Thr 7080] CCMS: CCMS Monitoring Initialization finished, rc=0.
F
F Tue Sep 02 02:24:44 2014
F ********************************************************************************
F SAP JVM arguments:
F arg[ 0] = vfprintf
F arg[ 1] = abort
F arg[ 2] = exit
F arg[ 3] = -XmonGcCallback
F arg[ 4] = -XdebugStateChangeCallback
F arg[ 5] = -DSAPSTART=1
F arg[ 6] = -DSAPSYSTEM=00
F arg[ 7] = -DSAPSYSTEMNAME=PID
F arg[ 8] = -DSAPMYNAME=usatlsv117_PID_00
F arg[ 9] = -DSAPPROFILE=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
F arg[10] = -DFRFC_FALLBACK=ON
F arg[11] = -DFRFC_FALLBACK_HOST=localhost
F arg[12] = -Xjvmx
F arg[13] = -XsapSystem:00
F arg[14] = -DSAPSTARTUP=1
F arg[15] = -DSAPDBHOST=usatlsv117
F arg[16] = -DSAPINFO=PID_00_server0
F arg[17] = -Dj2ee.dbhost=usatlsv117
F arg[18] = -Dsun.java.launcher=jstart
F arg[19] = -Dsun.java.command=com.sap.engine.boot.Start -DSAPSTART=1 -DSAPSYSTEM=00 -DSAPSYSTEMNAME=PID -DSAPMYNAME=usatlsv117_PID_00 -DSAPPROFILE=C:\\usr\\sap\\PID\\SYS\\profile\\PID_DVEBMGS00_usatlsv117 -DFRFC_FALLBACK=ON -DFRFC_FALLBACK_HOST=localhost
F arg[20] = -Djstartup.mode=JSTART
F arg[21] = -Djstartup.whoami=server
F arg[22] = -Djstartup.ownProcessId=3228
F arg[23] = -Djstartup.ownHardwareId=Q1489088110
F arg[24] = -Djstartup.debuggable=yes
F arg[25] = -DLoadBalanceRestricted=no
F arg[26] = -XdebugPortRange:50021-50021
F arg[27] = -Denv.class.path=
F arg[28] = -Dsys.global.dir=C:\usr\sap\PID\SYS\global
F arg[29] = -Dapplication.home=C:\usr\sap\PID\DVEBMGS00\exe
F arg[30] = -Djava.class.path=C:\usr\sap\PID\DVEBMGS00\exe\jstart71.jar;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\lib\jvmx.jar;C:\usr\sap\PID\DVEBMGS00\exe\jre\lib\iqlib.jar;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\lib\tools.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\boot\memoryanalyzer.jar
F arg[31] = -Djava.library.path=C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin\server;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin;C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\bin;C:\usr\sap\PID\DVEBMGS00\exe;C:\oracle\PID\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\j2sdk1.4.2_13-x64\bin;C:\Program Files (x86)\Windows Imaging;C:\Program Files\OmniBack\bin
F arg[32] = -XX:MaxNewSize=512m
F arg[33] = -Xms1536m
F arg[34] = -XX:PermSize=1536m
F arg[35] = -Xmx2560m
F arg[36] = -XX:NewSize=512m
F arg[37] = -XX:MaxPermSize=1536m
F arg[38] = -Drdbms.driverLocation=C:\usr\sap\PID\DVEBMGS00\exe\ojdbc14.jar
F arg[39] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler
F arg[40] = -Djava.security.policy=./../bin/kernel/java.policy
F arg[41] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
F arg[42] = -Dnetworkaddress.cache.ttl=10
F arg[43] = -Djco.jarm=1
F arg[44] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
F arg[45] = -Djava.security.egd=file:/dev/urandom
F arg[46] = -Djava.awt.headless=true
F arg[47] = -Djmx.invoke.getters=true
F arg[48] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
F arg[49] = -Djava.io.tmpdir=./temp
F arg[50] = -XX:SoftRefLRUPolicyMSPerMB=1
F arg[51] = -XX:-TraceClassUnloading
F arg[52] = -XX:+DumpDetailedClassStatisticOnOutOfMemory
F arg[53] = -XX:+DisableExplicitGC
F arg[54] = -XX:+PrintGCDetails
F arg[55] = -XX:+PrintGCTimeStamps
F arg[56] = -XX:HeapDumpPath=OOM.hprof
F arg[57] = -XX:+UseConcMarkSweepGC
F arg[58] = -XX:TargetSurvivorRatio=90
F arg[59] = -XX:-StringInternTableInPermGen
F arg[60] = -XX:+HeapDumpOnOutOfMemoryError
F arg[61] = -XX:MaxErrorQueueLength=200
F arg[62] = -verbose:gc
F arg[63] = -XX:SurvivorRatio=9
F arg[64] = -Xss2097152
F ignore unrecognized options : no
F ********************************************************************************
J JVMX version - Dec 11 2008 23:18:49 - 51_REL - optU - windows amd64 - bas2:113000 (mixed mode)
J (CompilerOracle read from file C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\.hotspot_compiler )
J (CompilerOracle exclude com/sun/tools/javac/code/SymbolMethodSymbol overrides)
F [Thr 6924] *** LOG => SfCJavaVm: Java VM started.
F ********************************************************************************
F Main method arguments:
F arg[ 0] = -DSAPSTART=1
F arg[ 1] = -DSAPSYSTEM=00
F arg[ 2] = -DSAPSYSTEMNAME=PID
F arg[ 3] = -DSAPMYNAME=usatlsv117_PID_00
F arg[ 4] = -DSAPPROFILE=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
F arg[ 5] = -DFRFC_FALLBACK=ON
F arg[ 6] = -DFRFC_FALLBACK_HOST=localhost
F ********************************************************************************
J
J Tue Sep 02 02:24:45 2014
J 1.887: [GC 1.887: [ParNew: 429056K->5751K(476672K), 0.0161568 secs] 429063K->5759K(1525248K), 0.0163708 secs]
F
F [Thr 6924] Tue Sep 02 02:24:46 2014
F [Thr 6924] *** LOG => State changed from 0 (Initial) to 1 (Waiting to start).
F [Thr 6924] *** LOG state real time: 2.437 CPU time: 0.453 sys, 2.828 usr
F [Thr 6924] *** LOG total real time: 2.437 CPU time: 0.453 sys, 2.828 usr
F [Thr 6924]
F [Thr 6924] *** LOG => State changed from 1 (Waiting to start) to 2 (Starting framework).
F [Thr 6924] *** LOG state real time: 0.000 CPU time: 0.000 sys, 0.000 usr
F [Thr 6924] *** LOG total real time: 2.437 CPU time: 0.453 sys, 2.828 usr
F [Thr 6924]
F
F [Thr 2080] Tue Sep 02 02:24:50 2014
F [Thr 2080] *** WARNING => SfCFramework::registerNatives: failed for com.sap.conn.rfc.driver.CpicDriver [sfxxifrw.hpp 167]
J
J Tue Sep 02 02:24:56 2014
J 12.669: [GC 12.669: [ParNewJ
J Tue Sep 02 02:24:57 2014
: 434807K->47616K(476672K), 0.3151169 secs] 435328K->90877K(1525248K), 0.3153873 secs]
F
F [Thr 7164] Tue Sep 02 02:25:05 2014
F [Thr 7164] *** LOG => SfCJavaVm: exit hook is called. (rc = 2150)
F [Thr 7164] *** LOG => exiting (exitcode 2150, retcode 1).
M [Thr 7164] CCMS: CCMS Monitoring Cleanup finished successfully.
trc file: "C:\usr\sap\PID\DVEBMGS00\work\dev_server0", trc level: 1, release: "711"
sysno 00
sid PID
systemid 562 (PC with Windows NT)
relno 7110
patchlevel 0
patchno 92
intno 20020600
make multithreaded, Unicode, 64 bit, optimized
profile C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
pid 2400
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS All, egi
Tue Sep 02 02:25:52 2014
* trace logging activated, max size = 52428800 bytes, 2 versions
arguments :
arg[ 0] : C:\usr\sap\PID\DVEBMGS00\exe\jstart.EXE
arg[ 1] : -appTrc
arg[ 2] : -nodeId=2
arg[ 3] : pf=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
arg[ 4] : -DSAPINFO=PID_00_server0
arg[ 5] : -hostvm
arg[ 6] : -nodeName=ID2463250
arg[ 7] : -file=C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\instance.properties
arg[ 8] : -jvmFile=C:\usr\sap\PID\DVEBMGS00\work\jstart.jvm
arg[ 9] : -traceFile=C:\usr\sap\PID\DVEBMGS00\work\dev_server0
arg[10] : -javaOutFile=C:\usr\sap\PID\DVEBMGS00\work\jvm_server0.out
arg[11] : -DSAPSTART=1
arg[12] : -DSAPSYSTEM=00
arg[13] : -DSAPSYSTEMNAME=PID
arg[14] : -DSAPMYNAME=usatlsv117_PID_00
arg[15] : -DSAPPROFILE=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
arg[16] : -DFRFC_FALLBACK=ON
arg[17] : -DFRFC_FALLBACK_HOST=localhost
F
F Tue Sep 02 02:25:52 2014
F ********************************************************************************
F Java environment properties
F root directory : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5
F vendor : SAP AG
F version : 1.5.0_14
F cpu : amd64
F java vm type : server
F java vm version : 5.1.027
F jvm library name : jvm.dll
F library path : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin\server;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin
F executable path : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\bin
F SAP extensions : available
F ********************************************************************************
I [Thr 3860] MtxInit: 10002 0 2
I [Thr 3860] MPI: dynamic quotas disabled.
I [Thr 3860] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
M [Thr 3860] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=1002;cur=2048)
M [Thr 3860] CCMS: Detected Double Stack (parameter "rdisp/j2ee_start" is active)
M [Thr 3860] CCMS uses Shared Memory Key 73 for monitoring.
M
M [Thr 3860] Tue Sep 02 02:25:53 2014
M [Thr 3860] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
M [Thr 3860] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
M [Thr 3860] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
M [Thr 3860] CCMS: CCMS Monitoring Initialization finished, rc=0.
F
F Tue Sep 02 02:25:53 2014
F ********************************************************************************
F SAP JVM arguments:
F arg[ 0] = vfprintf
F arg[ 1] = abort
F arg[ 2] = exit
F arg[ 3] = -XmonGcCallback
F arg[ 4] = -XdebugStateChangeCallback
F arg[ 5] = -DSAPSTART=1
F arg[ 6] = -DSAPSYSTEM=00
F arg[ 7] = -DSAPSYSTEMNAME=PID
F arg[ 8] = -DSAPMYNAME=usatlsv117_PID_00
F arg[ 9] = -DSAPPROFILE=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
F arg[10] = -DFRFC_FALLBACK=ON
F arg[11] = -DFRFC_FALLBACK_HOST=localhost
F arg[12] = -Xjvmx
F arg[13] = -XsapSystem:00
F arg[14] = -DSAPSTARTUP=1
F arg[15] = -DSAPDBHOST=usatlsv117
F arg[16] = -DSAPINFO=PID_00_server0
F arg[17] = -Dj2ee.dbhost=usatlsv117
F arg[18] = -Dsun.java.launcher=jstart
F arg[19] = -Dsun.java.command=com.sap.engine.boot.Start -DSAPSTART=1 -DSAPSYSTEM=00 -DSAPSYSTEMNAME=PID -DSAPMYNAME=usatlsv117_PID_00 -DSAPPROFILE=C:\\usr\\sap\\PID\\SYS\\profile\\PID_DVEBMGS00_usatlsv117 -DFRFC_FALLBACK=ON -DFRFC_FALLBACK_HOST=localhost
F arg[20] = -Djstartup.mode=JSTART
F arg[21] = -Djstartup.whoami=server
F arg[22] = -Djstartup.ownProcessId=2400
F arg[23] = -Djstartup.ownHardwareId=Q1489088110
F arg[24] = -Djstartup.debuggable=yes
F arg[25] = -DLoadBalanceRestricted=no
F arg[26] = -XdebugPortRange:50021-50021
F arg[27] = -Denv.class.path=
F arg[28] = -Dsys.global.dir=C:\usr\sap\PID\SYS\global
F arg[29] = -Dapplication.home=C:\usr\sap\PID\DVEBMGS00\exe
F arg[30] = -Djava.class.path=C:\usr\sap\PID\DVEBMGS00\exe\jstart71.jar;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\lib\jvmx.jar;C:\usr\sap\PID\DVEBMGS00\exe\jre\lib\iqlib.jar;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\lib\tools.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\boot\memoryanalyzer.jar
F arg[31] = -Djava.library.path=C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin\server;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin;C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\bin;C:\usr\sap\PID\DVEBMGS00\exe;C:\oracle\PID\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\j2sdk1.4.2_13-x64\bin;C:\Program Files (x86)\Windows Imaging;C:\Program Files\OmniBack\bin
F arg[32] = -XX:MaxNewSize=512m
F arg[33] = -Xms1536m
F arg[34] = -XX:PermSize=1536m
F arg[35] = -Xmx2560m
F arg[36] = -XX:NewSize=512m
F arg[37] = -XX:MaxPermSize=1536m
F arg[38] = -Drdbms.driverLocation=C:\usr\sap\PID\DVEBMGS00\exe\ojdbc14.jar
F arg[39] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler
F arg[40] = -Djava.security.policy=./../bin/kernel/java.policy
F arg[41] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
F arg[42] = -Dnetworkaddress.cache.ttl=10
F arg[43] = -Djco.jarm=1
F arg[44] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
F arg[45] = -Djava.security.egd=file:/dev/urandom
F arg[46] = -Djava.awt.headless=true
F arg[47] = -Djmx.invoke.getters=true
F arg[48] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
F arg[49] = -Djava.io.tmpdir=./temp
F arg[50] = -XX:SoftRefLRUPolicyMSPerMB=1
F arg[51] = -XX:-TraceClassUnloading
F arg[52] = -XX:+DumpDetailedClassStatisticOnOutOfMemory
F arg[53] = -XX:+DisableExplicitGC
F arg[54] = -XX:+PrintGCDetails
F arg[55] = -XX:+PrintGCTimeStamps
F arg[56] = -XX:HeapDumpPath=OOM.hprof
F arg[57] = -XX:+UseConcMarkSweepGC
F arg[58] = -XX:TargetSurvivorRatio=90
F arg[59] = -XX:-StringInternTableInPermGen
F arg[60] = -XX:+HeapDumpOnOutOfMemoryError
F arg[61] = -XX:MaxErrorQueueLength=200
F arg[62] = -verbose:gc
F arg[63] = -XX:SurvivorRatio=9
F arg[64] = -Xss2097152
F ignore unrecognized options : no
F ********************************************************************************
J JVMX version - Dec 11 2008 23:18:49 - 51_REL - optU - windows amd64 - bas2:113000 (mixed mode)
J (CompilerOracle read from file C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\.hotspot_compiler )
J (CompilerOracle exclude com/sun/tools/javac/code/SymbolMethodSymbol overrides)
F [Thr 780] *** LOG => SfCJavaVm: Java VM started.
F ********************************************************************************
F Main method arguments:
F arg[ 0] = -DSAPSTART=1
F arg[ 1] = -DSAPSYSTEM=00
F arg[ 2] = -DSAPSYSTEMNAME=PID
F arg[ 3] = -DSAPMYNAME=usatlsv117_PID_00
F arg[ 4] = -DSAPPROFILE=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
F arg[ 5] = -DFRFC_FALLBACK=ON
F arg[ 6] = -DFRFC_FALLBACK_HOST=localhost
F ********************************************************************************
J
J Tue Sep 02 02:25:54 2014
J 1.887: [GC 1.887: [ParNew: 429056K->5753K(476672K), 0.0159590 secs] 429063K->5761K(1525248K), 0.0161560 secs]
F
F [Thr 780] Tue Sep 02 02:25:55 2014
F [Thr 780] *** LOG => State changed from 0 (Initial) to 1 (Waiting to start).
F [Thr 780] *** LOG state real time: 2.328 CPU time: 0.343 sys, 3.000 usr
F [Thr 780] *** LOG total real time: 2.328 CPU time: 0.343 sys, 3.000 usr
F [Thr 780]
F [Thr 780] *** LOG => State changed from 1 (Waiting to start) to 2 (Starting framework).
F [Thr 780] *** LOG state real time: 0.000 CPU time: 0.000 sys, 0.000 usr
F [Thr 780] *** LOG total real time: 2.328 CPU time: 0.343 sys, 3.000 usr
F [Thr 780]
F
F [Thr 2564] Tue Sep 02 02:25:59 2014
F [Thr 2564] *** WARNING => SfCFramework::registerNatives: failed for com.sap.conn.rfc.driver.CpicDriver [sfxxifrw.hpp 167]
J
J Tue Sep 02 02:26:20 2014
J 27.372: [GC 27.372: [ParNew: 434809K->47616K(476672K), 0.3671732 secs] 435338K->93001K(1525248K), 0.3674017 secs]
F
F [Thr 4160] Tue Sep 02 02:26:30 2014
F [Thr 4160] *** LOG => SfCJavaVm: exit hook is called. (rc = 2150)
F [Thr 4160] *** LOG => exiting (exitcode 2150, retcode 1).
M [Thr 4160] CCMS: CCMS Monitoring Cleanup finished successfully.
trc file: "C:\usr\sap\PID\DVEBMGS00\work\dev_server0", trc level: 1, release: "711"
sysno 00
sid PID
systemid 562 (PC with Windows NT)
relno 7110
patchlevel 0
patchno 92
intno 20020600
make multithreaded, Unicode, 64 bit, optimized
profile C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
pid 6984
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS All, egi
Tue Sep 02 02:27:04 2014
* trace logging activated, max size = 52428800 bytes, 2 versions
arguments :
arg[ 0] : C:\usr\sap\PID\DVEBMGS00\exe\jstart.EXE
arg[ 1] : -appTrc
arg[ 2] : -nodeId=2
arg[ 3] : pf=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
arg[ 4] : -DSAPINFO=PID_00_server0
arg[ 5] : -hostvm
arg[ 6] : -nodeName=ID2463250
arg[ 7] : -file=C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\instance.properties
arg[ 8] : -jvmFile=C:\usr\sap\PID\DVEBMGS00\work\jstart.jvm
arg[ 9] : -traceFile=C:\usr\sap\PID\DVEBMGS00\work\dev_server0
arg[10] : -javaOutFile=C:\usr\sap\PID\DVEBMGS00\work\jvm_server0.out
arg[11] : -DSAPSTART=1
arg[12] : -DSAPSYSTEM=00
arg[13] : -DSAPSYSTEMNAME=PID
arg[14] : -DSAPMYNAME=usatlsv117_PID_00
arg[15] : -DSAPPROFILE=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
arg[16] : -DFRFC_FALLBACK=ON
arg[17] : -DFRFC_FALLBACK_HOST=localhost
F
F Tue Sep 02 02:27:04 2014
F ********************************************************************************
F Java environment properties
F root directory : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5
F vendor : SAP AG
F version : 1.5.0_14
F cpu : amd64
F java vm type : server
F java vm version : 5.1.027
F jvm library name : jvm.dll
F library path : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin\server;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin
F executable path : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\bin
F SAP extensions : available
F ********************************************************************************
I [Thr 4780] MtxInit: 10002 0 2
I [Thr 4780] MPI: dynamic quotas disabled.
I [Thr 4780] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
M
M [Thr 4780] Tue Sep 02 02:27:05 2014
M [Thr 4780] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=1002;cur=2048)
M [Thr 4780] CCMS: Detected Double Stack (parameter "rdisp/j2ee_start" is active)
M [Thr 4780] CCMS uses Shared Memory Key 73 for monitoring.
M [Thr 4780] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
M [Thr 4780] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
M [Thr 4780] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
M [Thr 4780] CCMS: CCMS Monitoring Initialization finished, rc=0.
F
F Tue Sep 02 02:27:05 2014
F ********************************************************************************
F SAP JVM arguments:
F arg[ 0] = vfprintf
F arg[ 1] = abort
F arg[ 2] = exit
F arg[ 3] = -XmonGcCallback
F arg[ 4] = -XdebugStateChangeCallback
F arg[ 5] = -DSAPSTART=1
F arg[ 6] = -DSAPSYSTEM=00
F arg[ 7] = -DSAPSYSTEMNAME=PID
F arg[ 8] = -DSAPMYNAME=usatlsv117_PID_00
F arg[ 9] = -DSAPPROFILE=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
F arg[10] = -DFRFC_FALLBACK=ON
F arg[11] = -DFRFC_FALLBACK_HOST=localhost
F arg[12] = -Xjvmx
F arg[13] = -XsapSystem:00
F arg[14] = -DSAPSTARTUP=1
F arg[15] = -DSAPDBHOST=usatlsv117
F arg[16] = -DSAPINFO=PID_00_server0
F arg[17] = -Dj2ee.dbhost=usatlsv117
F arg[18] = -Dsun.java.launcher=jstart
F arg[19] = -Dsun.java.command=com.sap.engine.boot.Start -DSAPSTART=1 -DSAPSYSTEM=00 -DSAPSYSTEMNAME=PID -DSAPMYNAME=usatlsv117_PID_00 -DSAPPROFILE=C:\\usr\\sap\\PID\\SYS\\profile\\PID_DVEBMGS00_usatlsv117 -DFRFC_FALLBACK=ON -DFRFC_FALLBACK_HOST=localhost
F arg[20] = -Djstartup.mode=JSTART
F arg[21] = -Djstartup.whoami=server
F arg[22] = -Djstartup.ownProcessId=6984
F arg[23] = -Djstartup.ownHardwareId=Q1489088110
F arg[24] = -Djstartup.debuggable=yes
F arg[25] = -DLoadBalanceRestricted=no
F arg[26] = -XdebugPortRange:50021-50021
F arg[27] = -Denv.class.path=
F arg[28] = -Dsys.global.dir=C:\usr\sap\PID\SYS\global
F arg[29] = -Dapplication.home=C:\usr\sap\PID\DVEBMGS00\exe
F arg[30] = -Djava.class.path=C:\usr\sap\PID\DVEBMGS00\exe\jstart71.jar;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\lib\jvmx.jar;C:\usr\sap\PID\DVEBMGS00\exe\jre\lib\iqlib.jar;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\lib\tools.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\boot\memoryanalyzer.jar
F arg[31] = -Djava.library.path=C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin\server;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin;C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\bin;C:\usr\sap\PID\DVEBMGS00\exe;C:\oracle\PID\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\j2sdk1.4.2_13-x64\bin;C:\Program Files (x86)\Windows Imaging;C:\Program Files\OmniBack\bin
F arg[32] = -XX:MaxNewSize=512m
F arg[33] = -Xms1536m
F arg[34] = -XX:PermSize=1536m
F arg[35] = -Xmx2560m
F arg[36] = -XX:NewSize=512m
F arg[37] = -XX:MaxPermSize=1536m
F arg[38] = -Drdbms.driverLocation=C:\usr\sap\PID\DVEBMGS00\exe\ojdbc14.jar
F arg[39] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler
F arg[40] = -Djava.security.policy=./../bin/kernel/java.policy
F arg[41] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
F arg[42] = -Dnetworkaddress.cache.ttl=10
F arg[43] = -Djco.jarm=1
F arg[44] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
F arg[45] = -Djava.security.egd=file:/dev/urandom
F arg[46] = -Djava.awt.headless=true
F arg[47] = -Djmx.invoke.getters=true
F arg[48] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
F arg[49] = -Djava.io.tmpdir=./temp
F arg[50] = -XX:SoftRefLRUPolicyMSPerMB=1
F arg[51] = -XX:-TraceClassUnloading
F arg[52] = -XX:+DumpDetailedClassStatisticOnOutOfMemory
F arg[53] = -XX:+DisableExplicitGC
F arg[54] = -XX:+PrintGCDetails
F arg[55] = -XX:+PrintGCTimeStamps
F arg[56] = -XX:HeapDumpPath=OOM.hprof
F arg[57] = -XX:+UseConcMarkSweepGC
F arg[58] = -XX:TargetSurvivorRatio=90
F arg[59] = -XX:-StringInternTableInPermGen
F arg[60] = -XX:+HeapDumpOnOutOfMemoryError
F arg[61] = -XX:MaxErrorQueueLength=200
F arg[62] = -verbose:gc
F arg[63] = -XX:SurvivorRatio=9
F arg[64] = -Xss2097152
F ignore unrecognized options : no
F ********************************************************************************
J JVMX version - Dec 11 2008 23:18:49 - 51_REL - optU - windows amd64 - bas2:113000 (mixed mode)
J (CompilerOracle read from file C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\.hotspot_compiler )
J (CompilerOracle exclude com/sun/tools/javac/code/SymbolMethodSymbol overrides)
F [Thr 1340] *** LOG => SfCJavaVm: Java VM started.
F ********************************************************************************
F Main method arguments:
F arg[ 0] = -DSAPSTART=1
F arg[ 1] = -DSAPSYSTEM=00
F arg[ 2] = -DSAPSYSTEMNAME=PID
F arg[ 3] = -DSAPMYNAME=usatlsv117_PID_00
F arg[ 4] = -DSAPPROFILE=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
F arg[ 5] = -DFRFC_FALLBACK=ON
F arg[ 6] = -DFRFC_FALLBACK_HOST=localhost
F ********************************************************************************
J
J Tue Sep 02 02:27:06 2014
J 1.902: [GC 1.902: [ParNew: 429056K->5751K(476672K), 0.0129215 secs] 429063K->5759K(1525248K), 0.0131458 secs]
F
F [Thr 1340] Tue Sep 02 02:27:07 2014
F [Thr 1340] *** LOG => State changed from 0 (Initial) to 1 (Waiting to start).
F [Thr 1340] *** LOG state real time: 2.484 CPU time: 0.359 sys, 3.031 usr
F [Thr 1340] *** LOG total real time: 2.484 CPU time: 0.359 sys, 3.031 usr
F [Thr 1340]
F [Thr 1340] *** LOG => State changed from 1 (Waiting to start) to 2 (Starting framework).
F [Thr 1340] *** LOG state real time: 0.000 CPU time: 0.000 sys, 0.000 usr
F [Thr 1340] *** LOG total real time: 2.484 CPU time: 0.359 sys, 3.031 usr
F [Thr 1340]
F
F [Thr 7080] Tue Sep 02 02:27:11 2014
F [Thr 7080] *** WARNING => SfCFramework::registerNatives: failed for com.sap.conn.rfc.driver.CpicDriver [sfxxifrw.hpp 167]
J
J Tue Sep 02 02:27:16 2014
J 11.641: [GC 11.641: [ParNewJ
J Tue Sep 02 02:27:17 2014
: 434807K->47616K(476672K), 0.3650486 secs] 435337K->93577K(1525248K), 0.3653062 secs]
F
F [Thr 3508] Tue Sep 02 02:27:24 2014
F [Thr 3508] *** LOG => SfCJavaVm: exit hook is called. (rc = 2150)
F [Thr 3508] *** LOG => exiting (exitcode 2150, retcode 1).
M [Thr 3508] CCMS: CCMS Monitoring Cleanup finished successfully.
trc file: "C:\usr\sap\PID\DVEBMGS00\work\dev_server0", trc level: 1, release: "711"
sysno 00
sid PID
systemid 562 (PC with Windows NT)
relno 7110
patchlevel 0
patchno 92
intno 20020600
make multithreaded, Unicode, 64 bit, optimized
profile C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
pid 6824
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS All, egi
Tue Sep 02 02:27:57 2014
* trace logging activated, max size = 52428800 bytes, 2 versions
arguments :
arg[ 0] : C:\usr\sap\PID\DVEBMGS00\exe\jstart.EXE
arg[ 1] : -appTrc
arg[ 2] : -nodeId=2
arg[ 3] : pf=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
arg[ 4] : -DSAPINFO=PID_00_server0
arg[ 5] : -hostvm
arg[ 6] : -nodeName=ID2463250
arg[ 7] : -file=C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\instance.properties
arg[ 8] : -jvmFile=C:\usr\sap\PID\DVEBMGS00\work\jstart.jvm
arg[ 9] : -traceFile=C:\usr\sap\PID\DVEBMGS00\work\dev_server0
arg[10] : -javaOutFile=C:\usr\sap\PID\DVEBMGS00\work\jvm_server0.out
arg[11] : -DSAPSTART=1
arg[12] : -DSAPSYSTEM=00
arg[13] : -DSAPSYSTEMNAME=PID
arg[14] : -DSAPMYNAME=usatlsv117_PID_00
arg[15] : -DSAPPROFILE=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
arg[16] : -DFRFC_FALLBACK=ON
arg[17] : -DFRFC_FALLBACK_HOST=localhost
F
F Tue Sep 02 02:27:57 2014
F ********************************************************************************
F Java environment properties
F root directory : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5
F vendor : SAP AG
F version : 1.5.0_14
F cpu : amd64
F java vm type : server
F java vm version : 5.1.027
F jvm library name : jvm.dll
F library path : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin\server;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin
F executable path : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\bin
F SAP extensions : available
F ********************************************************************************
I [Thr 3256] MtxInit: 10002 0 2
I [Thr 3256] MPI: dynamic quotas disabled.
I [Thr 3256] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
M [Thr 3256] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=1002;cur=2048)
M [Thr 3256] CCMS: Detected Double Stack (parameter "rdisp/j2ee_start" is active)
M [Thr 3256] CCMS uses Shared Memory Key 73 for monitoring.
M [Thr 3256] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
M [Thr 3256] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
M [Thr 3256] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
M [Thr 3256] CCMS: CCMS Monitoring Initialization finished, rc=0.
F
F Tue Sep 02 02:27:57 2014
F ********************************************************************************
F SAP JVM arguments:
F arg[ 0] = vfprintf
F arg[ 1] = abort
F arg[ 2] = exit
F arg[ 3] = -XmonGcCallback
F arg[ 4] = -XdebugStateChangeCallback
F arg[ 5] = -DSAPSTART=1
F arg[ 6] = -DSAPSYSTEM=00
F arg[ 7] = -DSAPSYSTEMNAME=PID
F arg[ 8] = -DSAPMYNAME=usatlsv117_PID_00
F arg[ 9] = -DSAPPROFILE=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
F arg[10] = -DFRFC_FALLBACK=ON
F arg[11] = -DFRFC_FALLBACK_HOST=localhost
F arg[12] = -Xjvmx
F arg[13] = -XsapSystem:00
F arg[14] = -DSAPSTARTUP=1
F arg[15] = -DSAPDBHOST=usatlsv117
F arg[16] = -DSAPINFO=PID_00_server0
F arg[17] = -Dj2ee.dbhost=usatlsv117
F arg[18] = -Dsun.java.launcher=jstart
F arg[19] = -Dsun.java.command=com.sap.engine.boot.Start -DSAPSTART=1 -DSAPSYSTEM=00 -DSAPSYSTEMNAME=PID -DSAPMYNAME=usatlsv117_PID_00 -DSAPPROFILE=C:\\usr\\sap\\PID\\SYS\\profile\\PID_DVEBMGS00_usatlsv117 -DFRFC_FALLBACK=ON -DFRFC_FALLBACK_HOST=localhost
F arg[20] = -Djstartup.mode=JSTART
F arg[21] = -Djstartup.whoami=server
F arg[22] = -Djstartup.ownProcessId=6824
F arg[23] = -Djstartup.ownHardwareId=Q1489088110
F arg[24] = -Djstartup.debuggable=yes
F arg[25] = -DLoadBalanceRestricted=no
F arg[26] = -XdebugPortRange:50021-50021
F arg[27] = -Denv.class.path=
F arg[28] = -Dsys.global.dir=C:\usr\sap\PID\SYS\global
F arg[29] = -Dapplication.home=C:\usr\sap\PID\DVEBMGS00\exe
F arg[30] = -Djava.class.path=C:\usr\sap\PID\DVEBMGS00\exe\jstart71.jar;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\lib\jvmx.jar;C:\usr\sap\PID\DVEBMGS00\exe\jre\lib\iqlib.jar;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\lib\tools.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\boot\memoryanalyzer.jar
F arg[31] = -Djava.library.path=C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin\server;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin;C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\bin;C:\usr\sap\PID\DVEBMGS00\exe;C:\oracle\PID\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\j2sdk1.4.2_13-x64\bin;C:\Program Files (x86)\Windows Imaging;C:\Program Files\OmniBack\bin
F arg[32] = -XX:MaxNewSize=512m
F arg[33] = -Xms1536m
F arg[34] = -XX:PermSize=1536m
F arg[35] = -Xmx2560m
F arg[36] = -XX:NewSize=512m
F arg[37] = -XX:MaxPermSize=1536m
F arg[38] = -Drdbms.driverLocation=C:\usr\sap\PID\DVEBMGS00\exe\ojdbc14.jar
F arg[39] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler
F arg[40] = -Djava.security.policy=./../bin/kernel/java.policy
F arg[41] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
F arg[42] = -Dnetworkaddress.cache.ttl=10
F arg[43] = -Djco.jarm=1
F arg[44] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
F arg[45] = -Djava.security.egd=file:/dev/urandom
F arg[46] = -Djava.awt.headless=true
F arg[47] = -Djmx.invoke.getters=true
F arg[48] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
F arg[49] = -Djava.io.tmpdir=./temp
F arg[50] = -XX:SoftRefLRUPolicyMSPerMB=1
F arg[51] = -XX:-TraceClassUnloading
F arg[52] = -XX:+DumpDetailedClassStatisticOnOutOfMemory
F arg[53] = -XX:+DisableExplicitGC
F arg[54] = -XX:+PrintGCDetails
F arg[55] = -XX:+PrintGCTimeStamps
F arg[56] = -XX:HeapDumpPath=OOM.hprof
F arg[57] = -XX:+UseConcMarkSweepGC
F arg[58] = -XX:TargetSurvivorRatio=90
F arg[59] = -XX:-StringInternTableInPermGen
F arg[60] = -XX:+HeapDumpOnOutOfMemoryError
F arg[61] = -XX:MaxErrorQueueLength=200
F arg[62] = -verbose:gc
F arg[63] = -XX:SurvivorRatio=9
F arg[64] = -Xss2097152
F ignore unrecognized options : no
F ********************************************************************************
J JVMX version - Dec 11 2008 23:18:49 - 51_REL - optU - windows amd64 - bas2:113000 (mixed mode)
J (CompilerOracle read from file C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\.hotspot_compiler )
J (CompilerOracle exclude com/sun/tools/javac/code/SymbolMethodSymbol overrides)
F [Thr 5160] *** LOG => SfCJavaVm: Java VM started.
F ********************************************************************************
F Main method arguments:
F arg[ 0] = -DSAPSTART=1
F arg[ 1] = -DSAPSYSTEM=00
F arg[ 2] = -DSAPSYSTEMNAME=PID
F arg[ 3] = -DSAPMYNAME=usatlsv117_PID_00
F arg[ 4] = -DSAPPROFILE=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
F arg[ 5] = -DFRFC_FALLBACK=ON
F arg[ 6] = -DFRFC_FALLBACK_HOST=localhost
F ********************************************************************************
J
J Tue Sep 02 02:27:59 2014
J 1.855: [GC 1.856: [ParNew: 429056K->5734K(476672K), 0.0159448 secs] 429063K->5742K(1525248K), 0.0161384 secs]
F
F [Thr 5160] Tue Sep 02 02:27:59 2014
F [Thr 5160] *** LOG => State changed from 0 (Initial) to 1 (Waiting to start).
F [Thr 5160] *** LOG state real time: 2.375 CPU time: 0.406 sys, 2.906 usr
F [Thr 5160] *** LOG total real time: 2.375 CPU time: 0.406 sys, 2.906 usr
F [Thr 5160]
F [Thr 5160] *** LOG => State changed from 1 (Waiting to start) to 2 (Starting framework).
F [Thr 5160] *** LOG state real time: 0.015 CPU time: 0.000 sys, 0.031 usr
F [Thr 5160] *** LOG total real time: 2.390 CPU time: 0.406 sys, 2.937 usr
F [Thr 5160]
F
F [Thr 3804] Tue Sep 02 02:28:03 2014
F [Thr 3804] *** WARNING => SfCFramework::registerNatives: failed for com.sap.conn.rfc.driver.CpicDriver [sfxxifrw.hpp 167]
J
J Tue Sep 02 02:28:08 2014
J 10.938: [GC 10.938: [ParNew: 434790K->47616K(476672K), 0.3162156 secs] 435321K->93746K(1525248K), 0.3164450 secs]
F
F [Thr 7028] Tue Sep 02 02:28:15 2014
F [Thr 7028] *** LOG => SfCJavaVm: exit hook is called. (rc = 2150)
F [Thr 7028] *** LOG => exiting (exitcode 2150, retcode 1).
M [Thr 7028] CCMS: CCMS Monitoring Cleanup finished successfully.
trc file: "C:\usr\sap\PID\DVEBMGS00\work\dev_server0", trc level: 1, release: "711"
sysno 00
sid PID
systemid 562 (PC with Windows NT)
relno 7110
patchlevel 0
patchno 92
intno 20020600
make multithreaded, Unicode, 64 bit, optimized
profile C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
pid 3608
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS All, egi
Tue Sep 02 02:29:06 2014
* trace logging activated, max size = 52428800 bytes, 2 versions
arguments :
arg[ 0] : C:\usr\sap\PID\DVEBMGS00\exe\jstart.EXE
arg[ 1] : -appTrc
arg[ 2] : -nodeId=2
arg[ 3] : pf=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
arg[ 4] : -DSAPINFO=PID_00_server0
arg[ 5] : -hostvm
arg[ 6] : -nodeName=ID2463250
arg[ 7] : -file=C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\instance.properties
arg[ 8] : -jvmFile=C:\usr\sap\PID\DVEBMGS00\work\jstart.jvm
arg[ 9] : -traceFile=C:\usr\sap\PID\DVEBMGS00\work\dev_server0
arg[10] : -javaOutFile=C:\usr\sap\PID\DVEBMGS00\work\jvm_server0.out
arg[11] : -DSAPSTART=1
arg[12] : -DSAPSYSTEM=00
arg[13] : -DSAPSYSTEMNAME=PID
arg[14] : -DSAPMYNAME=usatlsv117_PID_00
arg[15] : -DSAPPROFILE=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
arg[16] : -DFRFC_FALLBACK=ON
arg[17] : -DFRFC_FALLBACK_HOST=localhost
F
F Tue Sep 02 02:29:06 2014
F ********************************************************************************
F Java environment properties
F root directory : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5
F vendor : SAP AG
F version : 1.5.0_14
F cpu : amd64
F java vm type : server
F java vm version : 5.1.027
F jvm library name : jvm.dll
F library path : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin\server;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin
F executable path : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\bin
F SAP extensions : available
F ********************************************************************************
I [Thr 4340] MtxInit: 10002 0 2
I [Thr 4340] MPI: dynamic quotas disabled.
I [Thr 4340] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
M [Thr 4340] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=1002;cur=2048)
M [Thr 4340] CCMS: Detected Double Stack (parameter "rdisp/j2ee_start" is active)
M [Thr 4340] CCMS uses Shared Memory Key 73 for monitoring.
M [Thr 4340] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
M [Thr 4340] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
M [Thr 4340] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
M [Thr 4340] CCMS: CCMS Monitoring Initialization finished, rc=0.
F
F Tue Sep 02 02:29:06 2014
F ********************************************************************************
F SAP JVM arguments:
F arg[ 0] = vfprintf
F arg[ 1] = abort
F arg[ 2] = exit
F arg[ 3] = -XmonGcCallback
F arg[ 4] = -XdebugStateChangeCallback
F arg[ 5] = -DSAPSTART=1
F arg[ 6] = -DSAPSYSTEM=00
F arg[ 7] = -DSAPSYSTEMNAME=PID
F arg[ 8] = -DSAPMYNAME=usatlsv117_PID_00
F arg[ 9] = -DSAPPROFILE=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
F arg[10] = -DFRFC_FALLBACK=ON
F arg[11] = -DFRFC_FALLBACK_HOST=localhost
F arg[12] = -Xjvmx
F arg[13] = -XsapSystem:00
F arg[14] = -DSAPSTARTUP=1
F arg[15] = -DSAPDBHOST=usatlsv117
F arg[16] = -DSAPINFO=PID_00_server0
F arg[17] = -Dj2ee.dbhost=usatlsv117
F arg[18] = -Dsun.java.launcher=jstart
F arg[19] = -Dsun.java.command=com.sap.engine.boot.Start -DSAPSTART=1 -DSAPSYSTEM=00 -DSAPSYSTEMNAME=PID -DSAPMYNAME=usatlsv117_PID_00 -DSAPPROFILE=C:\\usr\\sap\\PID\\SYS\\profile\\PID_DVEBMGS00_usatlsv117 -DFRFC_FALLBACK=ON -DFRFC_FALLBACK_HOST=localhost
F arg[20] = -Djstartup.mode=JSTART
F arg[21] = -Djstartup.whoami=server
F arg[22] = -Djstartup.ownProcessId=3608
F arg[23] = -Djstartup.ownHardwareId=Q1489088110
F arg[24] = -Djstartup.debuggable=yes
F arg[25] = -DLoadBalanceRestricted=no
F arg[26] = -XdebugPortRange:50021-50021
F arg[27] = -Denv.class.path=
F arg[28] = -Dsys.global.dir=C:\usr\sap\PID\SYS\global
F arg[29] = -Dapplication.home=C:\usr\sap\PID\DVEBMGS00\exe
F arg[30] = -Djava.class.path=C:\usr\sap\PID\DVEBMGS00\exe\jstart71.jar;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\lib\jvmx.jar;C:\usr\sap\PID\DVEBMGS00\exe\jre\lib\iqlib.jar;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\lib\tools.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\boot\memoryanalyzer.jar
F arg[31] = -Djava.library.path=C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin\server;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin;C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\bin;C:\usr\sap\PID\DVEBMGS00\exe;C:\oracle\PID\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\j2sdk1.4.2_13-x64\bin;C:\Program Files (x86)\Windows Imaging;C:\Program Files\OmniBack\bin
F arg[32] = -XX:MaxNewSize=512m
F arg[33] = -Xms1536m
F arg[34] = -XX:PermSize=1536m
F arg[35] = -Xmx2560m
F arg[36] = -XX:NewSize=512m
F arg[37] = -XX:MaxPermSize=1536m
F arg[38] = -Drdbms.driverLocation=C:\usr\sap\PID\DVEBMGS00\exe\ojdbc14.jar
F arg[39] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler
F arg[40] = -Djava.security.policy=./../bin/kernel/java.policy
F arg[41] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
F arg[42] = -Dnetworkaddress.cache.ttl=10
F arg[43] = -Djco.jarm=1
F arg[44] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
F arg[45] = -Djava.security.egd=file:/dev/urandom
F arg[46] = -Djava.awt.headless=true
F arg[47] = -Djmx.invoke.getters=true
F arg[48] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
F arg[49] = -Djava.io.tmpdir=./temp
F arg[50] = -XX:SoftRefLRUPolicyMSPerMB=1
F arg[51] = -XX:-TraceClassUnloading
F arg[52] = -XX:+DumpDetailedClassStatisticOnOutOfMemory
F arg[53] = -XX:+DisableExplicitGC
F arg[54] = -XX:+PrintGCDetails
F arg[55] = -XX:+PrintGCTimeStamps
F arg[56] = -XX:HeapDumpPath=OOM.hprof
F arg[57] = -XX:+UseConcMarkSweepGC
F arg[58] = -XX:TargetSurvivorRatio=90
F arg[59] = -XX:-StringInternTableInPermGen
F arg[60] = -XX:+HeapDumpOnOutOfMemoryError
F arg[61] = -XX:MaxErrorQueueLength=200
F arg[62] = -verbose:gc
F arg[63] = -XX:SurvivorRatio=9
F arg[64] = -Xss2097152
F ignore unrecognized options : no
F ********************************************************************************
J JVMX version - Dec 11 2008 23:18:49 - 51_REL - optU - windows amd64 - bas2:113000 (mixed mode)
J (CompilerOracle read from file C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\.hotspot_compiler )
J (CompilerOracle exclude com/sun/tools/javac/code/SymbolMethodSymbol overrides)
F [Thr 7024] *** LOG => SfCJavaVm: Java VM started.
F ********************************************************************************
F Main method arguments:
F arg[ 0] = -DSAPSTART=1
F arg[ 1] = -DSAPSYSTEM=00
F arg[ 2] = -DSAPSYSTEMNAME=PID
F arg[ 3] = -DSAPMYNAME=usatlsv117_PID_00
F arg[ 4] = -DSAPPROFILE=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
F arg[ 5] = -DFRFC_FALLBACK=ON
F arg[ 6] = -DFRFC_FALLBACK_HOST=localhost
F ********************************************************************************
J
J Tue Sep 02 02:29:08 2014
J 1.824: [GC 1.824: [ParNew: 429056K->5740K(476672K), 0.0139839 secs] 429063K->5748K(1525248K), 0.0141350 secs]
F
F [Thr 7024] Tue Sep 02 02:29:08 2014
F [Thr 7024] *** LOG => State changed from 0 (Initial) to 1 (Waiting to start).
F [Thr 7024] *** LOG state real time: 2.234 CPU time: 0.359 sys, 2.937 usr
F [Thr 7024] *** LOG total real time: 2.234 CPU time: 0.359 sys, 2.937 usr
F [Thr 7024]
F [Thr 7024] *** LOG => State changed from 1 (Waiting to start) to 2 (Starting framework).
F [Thr 7024] *** LOG state real time: 0.000 CPU time: 0.000 sys, 0.000 usr
F [Thr 7024] *** LOG total real time: 2.234 CPU time: 0.359 sys, 2.937 usr
F [Thr 7024]
F
F [Thr 5004] Tue Sep 02 02:29:12 2014
F [Thr 5004] *** WARNING => SfCFramework::registerNatives: failed for com.sap.conn.rfc.driver.CpicDriver [sfxxifrw.hpp 167]
J
J Tue Sep 02 02:29:18 2014
J 12.580: [GC 12.580: [ParNewJ
J Tue Sep 02 02:29:19 2014
: 434796K->47616K(476672K), 0.3256880 secs] 435332K->95328K(1525248K), 0.3259093 secs]
F
F [Thr 3460] Tue Sep 02 02:29:26 2014
F [Thr 3460] *** LOG => SfCJavaVm: exit hook is called. (rc = 2150)
F [Thr 3460] *** LOG => exiting (exitcode 2150, retcode 1).
M [Thr 3460] CCMS: CCMS Monitoring Cleanup finished successfully.
trc file: "C:\usr\sap\PID\DVEBMGS00\work\dev_server0", trc level: 1, release: "711"
sysno 00
sid PID
systemid 562 (PC with Windows NT)
relno 7110
patchlevel 0
patchno 92
intno 20020600
make multithreaded, Unicode, 64 bit, optimized
profile C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
pid 5224
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS All, egi
Tue Sep 02 02:30:00 2014
* trace logging activated, max size = 52428800 bytes, 2 versions
arguments :
arg[ 0] : C:\usr\sap\PID\DVEBMGS00\exe\jstart.EXE
arg[ 1] : -appTrc
arg[ 2] : -nodeId=2
arg[ 3] : pf=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
arg[ 4] : -DSAPINFO=PID_00_server0
arg[ 5] : -hostvm
arg[ 6] : -nodeName=ID2463250
arg[ 7] : -file=C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\instance.properties
arg[ 8] : -jvmFile=C:\usr\sap\PID\DVEBMGS00\work\jstart.jvm
arg[ 9] : -traceFile=C:\usr\sap\PID\DVEBMGS00\work\dev_server0
arg[10] : -javaOutFile=C:\usr\sap\PID\DVEBMGS00\work\jvm_server0.out
arg[11] : -DSAPSTART=1
arg[12] : -DSAPSYSTEM=00
arg[13] : -DSAPSYSTEMNAME=PID
arg[14] : -DSAPMYNAME=usatlsv117_PID_00
arg[15] : -DSAPPROFILE=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
arg[16] : -DFRFC_FALLBACK=ON
arg[17] : -DFRFC_FALLBACK_HOST=localhost
F
F Tue Sep 02 02:30:00 2014
F ********************************************************************************
F Java environment properties
F root directory : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5
F vendor : SAP AG
F version : 1.5.0_14
F cpu : amd64
F java vm type : server
F java vm version : 5.1.027
F jvm library name : jvm.dll
F library path : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin\server;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin
F executable path : C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\bin
F SAP extensions : available
F ********************************************************************************
I [Thr 6284] MtxInit: 10002 0 2
I [Thr 6284] MPI: dynamic quotas disabled.
I [Thr 6284] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
M [Thr 6284] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=1002;cur=2048)
M [Thr 6284] CCMS: Detected Double Stack (parameter "rdisp/j2ee_start" is active)
M [Thr 6284] CCMS uses Shared Memory Key 73 for monitoring.
M [Thr 6284] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
M [Thr 6284] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
M [Thr 6284] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
M [Thr 6284] CCMS: CCMS Monitoring Initialization finished, rc=0.
F
F Tue Sep 02 02:30:00 2014
F ********************************************************************************
F SAP JVM arguments:
F arg[ 0] = vfprintf
F arg[ 1] = abort
F arg[ 2] = exit
F arg[ 3] = -XmonGcCallback
F arg[ 4] = -XdebugStateChangeCallback
F arg[ 5] = -DSAPSTART=1
F arg[ 6] = -DSAPSYSTEM=00
F arg[ 7] = -DSAPSYSTEMNAME=PID
F arg[ 8] = -DSAPMYNAME=usatlsv117_PID_00
F arg[ 9] = -DSAPPROFILE=C:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_usatlsv117
F arg[10] = -DFRFC_FALLBACK=ON
F arg[11] = -DFRFC_FALLBACK_HOST=localhost
F arg[12] = -Xjvmx
F arg[13] = -XsapSystem:00
F arg[14] = -DSAPSTARTUP=1
F arg[15] = -DSAPDBHOST=usatlsv117
F arg[16] = -DSAPINFO=PID_00_server0
F arg[17] = -Dj2ee.dbhost=usatlsv117
F arg[18] = -Dsun.java.launcher=jstart
F arg[19] = -Dsun.java.command=com.sap.engine.boot.Start -DSAPSTART=1 -DSAPSYSTEM=00 -DSAPSYSTEMNAME=PID -DSAPMYNAME=usatlsv117_PID_00 -DSAPPROFILE=C:\\usr\\sap\\PID\\SYS\\profile\\PID_DVEBMGS00_usatlsv117 -DFRFC_FALLBACK=ON -DFRFC_FALLBACK_HOST=localhost
F arg[20] = -Djstartup.mode=JSTART
F arg[21] = -Djstartup.whoami=server
F arg[22] = -Djstartup.ownProcessId=5224
F arg[23] = -Djstartup.ownHardwareId=Q1489088110
F arg[24] = -Djstartup.debuggable=yes
F arg[25] = -DLoadBalanceRestricted=no
F arg[26] = -XdebugPortRange:50021-50021
F arg[27] = -Denv.class.path=
F arg[28] = -Dsys.global.dir=C:\usr\sap\PID\SYS\global
F arg[29] = -Dapplication.home=C:\usr\sap\PID\DVEBMGS00\exe
F arg[30] = -Djava.class.path=C:\usr\sap\PID\DVEBMGS00\exe\jstart71.jar;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\lib\jvmx.jar;C:\usr\sap\PID\DVEBMGS00\exe\jre\lib\iqlib.jar;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\lib\tools.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\boot\memoryanalyzer.jar
F arg[31] = -Djava.library.path=C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin\server;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\bin;C:\usr\sap\PID\DVEBMGS00\j2ee\os_libs;C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\bin;C:\usr\sap\PID\DVEBMGS00\exe;C:\oracle\PID\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\j2sdk1.4.2_13-x64\bin;C:\Program Files (x86)\Windows Imaging;C:\Program Files\OmniBack\bin
F arg[32] = -XX:MaxNewSize=512m
F arg[33] = -Xms1536m
F arg[34] = -XX:PermSize=1536m
F arg[35] = -Xmx2560m
F arg[36] = -XX:NewSize=512m
F arg[37] = -XX:MaxPermSize=1536m
F arg[38] = -Drdbms.driverLocation=C:\usr\sap\PID\DVEBMGS00\exe\ojdbc14.jar
F arg[39] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler
F arg[40] = -Djava.security.policy=./../bin/kernel/java.policy
F arg[41] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
F arg[42] = -Dnetworkaddress.cache.ttl=10
F arg[43] = -Djco.jarm=1
F arg[44] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
F arg[45]stdout/stderr redirection
node name : server0
host name : usatlsv117
system name : PID
system nr. : 00
started at : Tue Sep 02 03:32:31 2014
JVMX version - Dec 11 2008 23:18:49 - 51_REL - optU - windows amd64 - bas2:113000 (mixed mode)
(CompilerOracle read from file C:\usr\sap\PID\DVEBMGS00\exe\sapjvm_5\jre\.hotspot_compiler )
(CompilerOracle exclude com/sun/tools/javac/code/SymbolMethodSymbol overrides)
The active factory is : com.sap.engine.boot.loader.StandardClassLoaderFactory
Class loading cache information loaded from package index [C:\usr\sap\PID\DVEBMGS00\j2ee\cluster\bin\index.list]
Reading kernel properties from kernelProperties.bin file...
Checked the data for 63 ms
Read the objects for 484 ms
Substituted the values for 125 ms
Finished reading kernel objects for 609 ms
Startup mode [NORMAL] and action [NONE] read
AS Java version [7.11.3301.353173.20131008093148 SP 13] is starting server process [ID2463250] on host [usatlsv117]...
Loading [LogManager]... [39329] ms
Loading [PoolManager]... [15] ms
Loading [ApplicationThreadManager]... [219] ms
Loading [ThreadManager]... 46.066: [GC 46.066: [ParNew: 429056K->5700K(476672K), 0.0113643 secs] 429063K->5707K(1525248K), 0.0115702 secs]
[31] ms
Loading [ClassLoaderManager]... [16] ms
Loading [ClusterManager]... [437] ms
Loading [LockingManager]... [94] ms
Loading [ConfigurationManager]... [1922] ms
Loading [CacheManager]... [78] ms
Loading [DatabaseManager]... [1047] ms
Loading [SessionManager]... [1266] ms
Loading [LicensingManager]... [31] ms
Loading [ServiceManager]...
Initialize components for : 203 ms.
Resolve components for : 360 ms.
Load components for 3437 ms.
Loading services.
Calculate startup service set for 469 ms.
Service [webservices] started. [0] ms / [0] CPU ms
Service [tc~je~security~api] started. [0] ms / [0] CPU ms
Service [tc~je~cross~api] started. [0] ms / [0] CPU ms
Service [r3startup] started. [0] ms / [0] CPU ms
Service [tc~esi~uddi~content~handler] started. [0] ms / [0] CPU ms
Service [tc~je~mngt_model~srv] started. [0] ms / [0] CPU ms
Service [engine.lm.log.facade] started. [0] ms / [0] CPU ms
Service [engine.dsr.facade] started. [0] ms / [0] CPU ms
Service [tc~je~content~classification~handler] started. [0] ms / [0] CPU ms
Service [runtimeinfo] started. [46] ms / [0] CPU ms
Service [cluster] started. [15] ms / [0] CPU ms
Service [memory] started. [156] ms / [46] CPU ms
Service [timeout] started. [156] ms / [78] CPU ms
Service [jmx_notification] started. [187] ms / [0] CPU ms
Service [cross] started. [156] ms / [15] CPU ms
Service [userstore] started. [125] ms / [0] CPU ms
Service [log_configurator] started. [250] ms / [78] CPU ms
Service [locking] started. [94] ms / [0] CPU ms
Service [p4] started. [344] ms / [62] CPU ms
Service [classload] started. [0] ms / [0] CPU ms
Service [classload.facade] started. [0] ms / [0] CPU ms
Service [msp] started. [62] ms / [15] CPU ms
Service [classpath_resolver] started. [218] ms / [15] CPU ms
Service [tc~sec~destinations~provider] started. [922] ms / [187] CPU ms
Service [naming] started. [797] ms / [265] CPU ms
Service [objectanalyzing] started. [47] ms / [0] CPU ms
Service [file] started. [16] ms / [0] CPU ms
Service [appclient] started. [93] ms / [0] CPU ms
Service [tc~je~sca~ejb.plugin] started. [0] ms / [0] CPU ms
Service [ts] started. [250] ms / [31] CPU ms
Service [licensing] started. [16] ms / [0] CPU ms
Service [engine.license.facade] started. [0] ms / [0] CPU ms
Service [javamail] started. [359] ms / [62] CPU ms
Service [connector] started. [469] ms / [78] CPU ms
Service [library_container] started. [31] ms / [15] CPU ms
Service [schemaprocessor~srv] started. [3078] ms / [953] CPU ms
Service [http] started. [4078] ms / [218] CPU ms
69.171: [GC 69.171: [ParNew: 434756K->47616K(476672K), 0.3116390 secs] 435300K->96608K(1525248K), 0.3119670 secs]
Service [deploy] started. [16469] ms / [343] CPU ms
Service [deploy.facade] started. [0] ms / [0] CPU ms
Service [metadatarepository] started. [0] ms / [0] CPU ms
Service [MigrationService] started. [31] ms / [15] CPU ms
Service [engine.migservice.facade] started. [0] ms / [0] CPU ms
Service [engine.migration.facade] started. [0] ms / [0] CPU ms
Service [orpersistence] started. [359] ms / [46] CPU ms
Service [dbpool] started. [2703] ms / [453] CPU ms
Service [dbpool.facade] started. [0] ms / [0] CPU ms
Service [tc~je~sca~integration] started. [2891] ms / [1890] CPU ms
Service [tc~je~dbcontainer~srv] started. [140] ms / [0] CPU ms
Service [tc~je~sca~ws.plugin] started. [156] ms / [125] CPU ms
Service [tc~je~cachemgmt~srv] started. [922] ms / [125] CPU ms
Service [com.sap.security.core.ume.service] start ================= ERROR =================
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Destination UMEBackendConnection could not be created: java.lang.NoSuchMethodError: com.sap.security.core.server.destinations.lib.RFCDestinationCore.setLoginTicket(Ljava/lang/String;)V
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:402)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:155)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:60)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:177)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:295)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Destination UMEBackendConnection could not be created: java.lang.NoSuchMethodError: com.sap.security.core.server.destinations.lib.RFCDestinationCore.setLoginTicket(Ljava/lang/String;)V
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:642)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getNewInstance(PrincipalDatabagFactory.java:228)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:170)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:240)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:157)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:103)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:208)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:263)
... 7 more
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Destination UMEBackendConnection could not be created: java.lang.NoSuchMethodError: com.sap.security.core.server.destinations.lib.RFCDestinationCore.setLoginTicket(Ljava/lang/String;)V
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:227)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:550)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:517)
... 14 more
Caused by: com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Destination UMEBackendConnection could not be created: java.lang.NoSuchMethodError: com.sap.security.core.server.destinations.lib.RFCDestinationCore.setLoginTicket(Ljava/lang/String;)V
at com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo700Proxy.<init>(R3JCo700Proxy.java:111)
at com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCoProxy.getInstance(R3JCoProxy.java:136)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.doInitRfc(R3PersistenceBase.java:778)
at com.sap.security.core.persistence.datasource.imp.R3Persistence.localInitialization(R3Persistence.java:258)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:525)
... 15 more
Caused by: com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Destination UMEBackendConnection could not be created: java.lang.NoSuchMethodError: com.sap.security.core.server.destinations.lib.RFCDestinationCore.setLoginTicket(Ljava/lang/String;)V
at com.sap.conn.jco.rt.DefaultDestinationManager.update(DefaultDestinationManager.java:208)
at com.sap.conn.jco.rt.DefaultDestinationManager.searchDestination(DefaultDestinationManager.java:374)
at com.sap.conn.jco.rt.DefaultDestinationManager.getDestinationInstance(DefaultDestinationManager.java:89)
at com.sap.conn.jco.JCoDestinationManager.getDestination(JCoDestinationManager.java:86)
at com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo700Proxy.<init>(R3JCo700Proxy.java:91)
... 19 more
Caused by: java.lang.NoSuchMethodError: com.sap.security.core.server.destinations.lib.RFCDestinationCore.setLoginTicket(Ljava/lang/String;)V
at com.sap.security.core.server.destinations.provider.DestinationsProviderFrame.getDestinationProperties(DestinationsProviderFrame.java:164)
at com.sap.conn.jco.rt.DefaultDestinationManager.getProperties(DefaultDestinationManager.java:324)
at com.sap.conn.jco.rt.DefaultDestinationManager.update(DefaultDestinationManager.java:161)
... 23 more
FATAL: Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [com.sap.security.core.ume.service] failed to start] -
Difference of decimal place in SAP R/3 and BW
Hello SAP experts,
I am extracting purchasing data from SAP R/3 using datasource 2LIS_02_SCL.
In BW I see a difference of one decimal place.
In RSA3 amount is shown as 17.350,00
Whereas in PSA above value is displayed as 1.735,000
Decimal notations are same in both R/3 and BW.
Please help me to understand the reason behind difference in values.
Thanks and Regards
ShilpaHello All,
The issue is resolved. The difference in Amount is due to different decimal configuration settings in TCURX table in both R/3 and BW. Ideally these settings should be same in R/3 and BW. If decimal settings doesn't match misalignment has to be taken care of either in ETL or during query design.
Thanks and Regards
Shilpa -
J2EE Engine cannot be started. SAP CRM EHP1 Dialog Instance Installation
Hi All,
During Installation of a DI on a Linux host, I encounterd a problem. An error occured during " start dialog instance". The ABAP enginee is started successfully where as the JAVA Enginee cant be started. During investigation I found from the log directory
..j2ee/cluster/server0/log as stated below ..
#1.#0050569F663E001E0000000C0000054F0004803004D18B3F#1266843634469#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_64##0#0#Error#1#/System/Server#Java###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
[EXCEPTION]
#1#com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: null
ume.db.connection_pool_type=SAP/BC_UME
ume.db.connection_pool.j2ee.xatransactions_used=false
ume.db.connection_pool.j2ee.is_unicode=false
ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:83)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:109)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: null
ume.db.connection_pool_type=SAP/BC_UME
ume.db.connection_pool.j2ee.xatransactions_used=false
ume.db.connection_pool.j2ee.is_unicode=false
ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:887)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:440)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
... 6 more
#1.#0050569F663E001E0000000E0000054F0004803004D18C49#1266843634469#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_64##0#0#Fatal#1#/System/Server/Critical#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
I checked with the env variable and parameter, it all looks good. If anybody finds the same issue please suggest ....
Thanks in Advance.
Regards,
ShashiThere is a troubleshooting topic for this on the Help Portal.
See http://help.sap.com/saphelp_nw70ehp1/helpdata/en/20/361941edd5ef23e10000000a155106/frameset.htm.
-Michael -
Error messge during data extract from flatfile to sap bw using DataServices
I am extracting data from flat file to SAP BW using Data Services tool. I am able to load all the data from flat file to SAP BW 3.x datasource successfully, but the request in in RED status with error message
Error Encountered at RFC Server Please Check Parameter Setting at BW System.
Can someone please help me how to resolve this issue?I would recommend to post your question here
Data Services and Data Quality
and close the current thread.
Regards,
Stratos -
PP DataSource 2LIS_04_P_ARBPL - Incorrect extraction of latest scheduled start dates (SSAVD)
Hi experts,
we use the SAP Business Content Standard DataSource 2LIS_04_P_ARBPL "Work Center View PP" and need the latest scheduled start date each production order operation.
In the production order operation overview (t/code CO03) on the ERP-side we have the expected latest scheduled start (Source AFVGD-SSAVD)
But in the DataSource 2LIS_04_P_ARBPL (PSA-Table) we become the incorrect latest scheduled start dates (DataSource field SSAVD)
Any ideas or experiences why the latest scheduled start date not up-to-date?
Many thanks and best regards,
MichaelHi,
I have tested the scenario again...
At the header level of test production order 1000381 I have changed the basic dates (Start/End) from 22.04.2014 to 24.04.2014.
As a result the start dates at operation level also changed...
After the above changes I have extracted the Data. The Delta-Queue (RSA7) for the relevant DataSource 2LIS_04_P_ARBPL looks nearly good.
For the both operations 20 and 30 the delta update for the field "Latest start date" (SSAV) works correct. But the delta update for the first operation "10" not processed.
Is it possible that the delta update only works for specific system status? Or any other ideas?
Many thanks and best regards,
Michael -
No hide fields or select fields in SAP Query Extractor?
HI Gurus,
I want to generate a data source, extraction data from SAP Query.
Now I want to hide some fields or to mark some fields as relevant for selection.
But after saving my settings are unavaiable...?
Does somebody have an idea? Is this standard when extracting from Query or is this maybe an OSS...?
ThanksHello,
Just logoff and Login again, then check it.
Also see
SAP Note 1014073 DFG: Changes to the DataSource are displayed incorrectly
SAP Note 1073714 DataSource in RSA6: Unable to display/change customer fields
SAP Note 925398 RSA6: DataSource enhancement only visible after restart
Thanks
Chandran -
Combine query, result from another query on SAP BI query Universe?
Hello all,
We are using SAP BI queries as datasource for our universes. Is the combined query option disabled for webi reports written on such universes?
result from another query - is this option active for such webi reports? I see both these options greyed out so wanted to check.
One last thing what is really difference between subquery and results from another query? subquery - you can use filters from that one data provider only right? or can you use a different data provider/report in sub query?
Thanks a lot for all the replies.Hi,
in BO 3.1 Combined query and result from another query options are not available in webi report on OLAP Universes (SAP BW Universe.)
Thanks,
Amit
Maybe you are looking for
-
HP Officejet Pro 8500A Plus Printer will connect to apps but will not connect to EPrint
OS MAC 10.6.8 Snow Leopard. I am using a wireless connection, no USB, and everything worked fine at one time. Recently, all remote printing, including Airprint stopped connecting. I am unable to access anything on the HP website via the printer ex
-
D600 raw file could not open in Aperture, but ok in Preview
I import D600 photo to my Aperture library all photo are in RAW format, but some file (almost 1-2 out of 100) could not view in Aperture, which show "Unsupported Image Format", but which could open in Preview, I try to import those file again and I g
-
Hi I need to block material for billing..how to go ahead? i have tried with sales org1 (dis channl status/ ex dis chall status) system did not allow me sales . its perfect but when i create STN from STO(UB/ LU) system did not allow me for NL delivery
-
Headset symbol has appeared of my screen Nokia E50
Hello I have this problem and I don't know what to do... I have restore phone to factory default, restart and take out battery for 5 minute, I don't know what to do. Please help me. If connect hands free, I can use phone with any problem, but if I tr
-
I forgot my security questions and when I want to reset but never received the email
Hi i forgot my security questions on my apple id and when i want to reset it they never send me the e mail were i can reset ir what can i do?