SAP daily checking

Question

hi all
I'm assigned by my boss to create SAP daily check (Critical section)
Need your suggestion what to check
I already put DB13, DB14, ST02, ST03
but I need in detail, for example.. on ST02 the program buffer should not > 10.000
My friend said I have to put the log file in OS system also, but I don't know what log and where is the path?
and what to check inside the log?
Also, my boss concern about free space, he told me to aware about the free space.
So, what filesystem should I check everyday? /oracle/SID/oraarch, /usr/sap/trans? and??
thanks in advance
regards,
Della

Answer 1

Hi Rosa,
Tcode sm12 used for lock management .With this you are able to determine which locks are being used currently.You can detect and correct problems by deleting locks that you no longer want. You can also later analyze the cause of lock table overflows using the History .
In tcode sm12 you can see which type the lock object is with the help of Lock mode.Where S: shared lock, E: exclusive lock, X: exclusive and not cumulative, O: optimistic lock. Again from Table name column you are able to know in which row of the table are locked.From Lock argument column you are able to see the argument (key field) of the lock entry.
Lock entry with Blue color means that the locks have already been transferred to the update task (see also The Owner Concept), with the result that the backup flag is set. These locks are also rewritten to the lock table when the enqueue server is restarted.Black means that the lock (still) belongs to the dialog owner. The backup flag is not set.By double-clicking a lock entry, you can display detailed information, including the host name and number of the SAP System in which the lock was generated.Rosa remember never delete a lock when you are unsure and/or don't know what is this lock for.If you delete a lock without proper justification may be it generate an inconsistence.Locks are put on table and / or table entries when a process needs exclusive access to this DB table and/or record. Removing this lock could let for example another process to change the same data while the process is still running thus generating inconsistence.
Always try to match a lock with a process in SM66, a background Job in SM37, a DB session, in ST04 / detailed analysis / sessions or a user logged in with AL08/SM04.
If you have identified from where does the lock come, then first try to kill the job, then the related process, then kick the user out (best would be to ask him what is he doing) and finally the DB session.
Usually one of this action will remove the lock cleanly.If it is not the case, deleting a lock in SM12 would be the very last option.
The ABAP Dumps will occur with respective of the problem.If you got the error. check the error name and serach in.
http://service.sap.com/notes.
Few of the most frequently occuring dumps are :
1) TIME_OUT : this happens due to longer dialog execution time for a user compared to the parameter settings. We can ask the user to run the report in batch jobs instead of dialog. we can ask the user to reduce the search criteria if he is using one.
2) RAISE_EXCEPTION : This is due to error in exception handling of the abap program. If its a customer report we can ask the developer to modify code or if its a sap report we can raise issue with sap
3) DBIF_SQL_ERROR: this happens due to various problems with database.
suppose user is trying to write duplicate entries to the tables then it occurs, if there is problem with the datafile then also it occurs. you have to read the details of the error.
4) TSV_NEW_PAGE_ALLOCATION_FAILED: Error due to not enough extended memory to run the report. This happens during high memory usage time, We can ask the user to run the report during less load and also to reduce the input criteria which will in turn reduce the processing memory required for the internal table.
or we need to increase the extended memory parameters.
5) MEMORY_NO_MORE_PAGING: happens due to not enough space in paging area. Can be solved by increasing the paging file parameter value.
6) LOAD_PROGRAM_ERROR: this error happens if during runtime any of the repository objects are changed by means of transport. We can ask the user to rerun the program.