on 02-01-2009 2:51 AM
Hi ,
I would be more grateful to all of you if you could let me know whatever logs we can check to find out/trace SAP system problems on the following
Installation logs (ABAP+JAVA)
DB logs - Oracle & SQL
J2EE,SDM & JSPM logs
I appreciate all your help.
Thanks in advance
Hello Daniel,
i will only give a little overview.
> Installation logs (ABAP+JAVA)
The default location depends on your OS (for example /tmp/sapinst_dir) or the specified path in the environment variable. Check the sapinst_dev.log
> DB logs - Oracle & SQL
/oracle/<SID>/saptrace/background/alert_<SID>.log
/oracle/<SID>/sapbackup/
/oracle/<SID>/saparch (or the path in the environment variable SAPARCH)
> J2EE
/usr/sap/<SID>/<INST>/work
/usr/sap/<SID>/<INST>/j2ee/cluster/server<X>/log/defaultTrace*
/usr/sap/<SID>/<INST>/j2ee/cluster/server<X>/log/applications*
To be honest i don't know what this information should be for.. but have fun
Regards
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
sqlnet.ora- Sqlnet.ora'is a text file that provides [[SQL*Net]] with basic configuration details like tracing options, default domain, encryption, etc. This file can be found in the [[ORACLE HOME]]\NETWORK\ADMIN directory.
'''TNSNAMES.ORA''' is a [[SQL*Net]] configuration file that defines databases addresses for establishing connections to them. This file normally resides in the [[ORACLE HOME]]\NETWORK\ADMIN directory.
The TNSNAMES.ORA files is located on both client and server systems. If you make configuration changes on the server ($ORACLE_HOME/network/admin/tnsnames.ora) ensure you can connect to the database through the listener if you are logged on to the server. If you make configuration changed on the client (c:\oracle\product\10.2.0\db_1\network\admin\tnsnames.ora) ensure you can connect from your client workstation to the database through the listener running on the server
Rohit
Hi ,
Thanks a lot ..Useful Information you provided.
I got a different scenario;I keep both Dev and Qty on the same server ,if I start the listener of Dev then It should start the Qty listener also automatically but the system(qty) should be up once we give "startsap" separately..for this where should I make the relevant settings.
I appreciate your help.
Thanks in advance
Hi ,
I am not at all talking about listener concept in Windows+ SQL 2005 combination.
To start SAP on Windows 2003
first we right click on the SID from MMC then to choose "startsap" - It starts message server,enqueue server & dispatcher one by one.
In our scenario I have installed two instance(DEV& QTY) on a same hostname ,so I have to start the each instance subsequently with the above procedure to up the services.
Is it possible to start the instance QTY also along with the DEV ,instead of again doing "startsap" for QTY separately..I hope my question is clear now.
Any script or settings change to be done somewhere on MSSQL 2005 & SAP to attain this scenario?
Thanks in advance
Hello Daniel,
this thing can be done in one case
suppose you have taken a reboot of the server,then we can automate the starting of both the servers
This can be done by changing the startup of SAP services from manual to automatic through services.exe.then after an outage both servers will start automatically
Hope it helps
Rohit
You can also check out at
/usr/sap/SID/DVEBMGS00/log directory
/usr/sap/SID/DVEBMGS00/work directory contains dev_ms, dev_disp,dev_wnn, dev_rfc, dev_icm files for dispatcher, message server, work processes, rfc ,etc
Lokesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hai,
For JAVA logs check the below link...
http://help.sap.com/saphelp_nwce10/helpdata/en/45/e3b0f5f76a2e99e10000000a155369/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/e4/540c404a435509e10000000a1550b0/frameset.htm
For Oracle logs check the user trace and Background trace under /oracle/<SID>/saptrace
For BR tools logs you can check DB12 this is for Backup, Redo logs etc.,
For DB calendar DB13, For memory related settings check ST04.
DB16,DB17 also can be used to check the DB logs.
BRBACKUP writes the following file system logs:
<SAPDATA_HOME>/sapbackup/b<encoded timestamp>.<ext>
Every detail log contains information about the status of the ORACLE database at the time of the corresponding backup and about the actions that were performed during the course of that backup.
<SAPDATA_HOME>/sapbackup/back<DBSID>.log
This summary log contains a brief entry for each backup. Among other things, this log shows the return code of every backup.
BRBACKUP also records its actions in the database tables SDBAH and SDBAD.
Check the below link.....
http://help.sap.com/saphelp_nw04s/helpdata/EN/0d/d30ed24a0c11d182b80000e829fbfe/frameset.htm
Normally all Oracle problems starts with the string ORA-XXXXX ( X - represents numbers ).
Regards,
Yoganand.V
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Use the Transaction code ST11 to find the error logs...
db12 and db14 for backup logs...
Regards,
Kalyan
Edited by: Kalyan Gupta on Feb 1, 2009 2:47 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.