logs
SAP NW Java: Delete old dumps and trace files with command find
We recomend regulary check directory /usr/sap/<SID>/<INSTANCE>/j2ee/cluster/server<N>/, where can be hold old dumps and trace files. For examle, in Note 1289240 – How to deal with out of memory errors we can read The heap dump is generated in directory /usr/sap/<SID>/<INSTANCE>/j2ee/cluster/server<N>/ where N is the server node number. Automatically created heap dump on out of memory event is in OOM.hprof and OOM.addons files. User generated heap dump is in files named as java_pid<PID>.hprof and java_pid<PID>.addons, where PID is the process ID (9848 for example). Also we can find *.trc files. We recomend delete unnecessary files In case Unix We use command find cd /usr/sap/<SID>/<INSTANCE>/j2ee/cluster/server<N>/ find … Continue Reading
ADS trace
Note 846610 – How to activate ADS trace Symptom This note shows how to activate the ADS trace on a J2EE engine. This trace information will be helpful for analysing irregularities. Other terms ADS, Adobe, Adobe Document Services, Trace, DefaultTrace Solution Run the Visual Administrator for your J2EE engine. Server -> services -> Log Configurator. Then select ‘To Advanced mode’ and ‘Locations’ tab. Root Location -> com -> sap -> engine -> services -> webservices -> server -> runtime -> com -> adobe_adobeDocumentServices -> AdobeDocumentServices and AdobeDocumentServicesSec Please change this node to ‘ALL’, and save the configuration. Modify the log … Continue Reading
AS Java log files
Instance log files Contents Information about the J2EE instance startup, including parameters such as the startup profile used, the system ID (SID), the instance name, and the startup command used. Use to analyze Problems with the startup of the entrie J2EE instance. For example, the central and dialog J2EE instances are running on different physical servers and the startup profile is stored on the central J2EE instance. If a J2EE dialog instance cannot access the startup profile on the central J2EE instance due to access restrictions, it would report the permission problem in this log. Log files The following log … Continue Reading
IcfGetDTFromTaskHandler: ThEppGetRootContextIdAsXuuid failed with (98)!
Symptom In dev_w* files you get errors: IcfGetDTFromTaskHandler: ThEppGetRootContextIdAsXuuid failed with (98)! Solution: Implement the latest kernel for your release. The error will not occur with the latest kernel patch.