SAP daily checking

[Former Member]

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

[Former Member · Accepted solution]

hi all

thanks for all the answers

can anyone explain me what to observe in sm12 - Lock Entries and st22 - short dumps

here is sampe of sm12 :

300 CASHIERSO 07:45:10 E TCJ_C_JOURNALS 30010000002 1 1

300 MEGGY 08:25:54 E EKKO 3004500003071 0 1

300 MEGGY 08:25:54 E EKPO 3004500003071##### 0 1

300 HARDYW 09:13:41 S VBAK 300$%&sdbatch 0 1

300 HARDYW 09:13:41 E VBAK 3003200001324 0 1

300 SUHARYANTO 09:22:48 E EBAN 300100000080100010 0 1

300 SUHARYANTO 09:22:48 E EBAN 300100000080100020 0 1

300 SUHARYANTO 09:22:48 E EBAN 300100000080100030 0 1

300 SUHARYANTO 09:22:48 E EBAN 300100000080100040 0 1

300 SUHARYANTO 09:22:48 S MARM 300000000003000001132### 0 1

300 SUHARYANTO 09:22:48 S MARM 300000000003000001146### 0 1

300 SUHARYANTO 09:22:48 S MARM 300000000003000007041### 0 1

300 SUHARYANTO 09:22:48 S MARM 300000000003000013546### 0 1

300 HERU 09:23:26 E SKB1 30010000021111404 0 1

300 MURDOKO 09:24:47 E EKKO 3004500003078 0 1

300 MURDOKO 09:24:47 E EKPO 3004500003078##### 0 1

here is sampe of st22 :

19.03.2009 17:22:17 casapci_CAP_32 WHS 300 C RAISE_EXCEPTION

19.03.2009 17:22:16 casapci_CAP_32 WHS 300 C RAISE_EXCEPTION

19.03.2009 17:22:15 casapci_CAP_32 WHS 300 C RAISE_EXCEPTION

19.03.2009 17:22:14 casapci_CAP_32 WHS 300 C RAISE_EXCEPTION

19.03.2009 17:22:13 casapci_CAP_32 WHS 300 C RAISE_EXCEPTION

19.03.2009 17:22:12 casapci_CAP_32 WHS 300 C RAISE_EXCEPTION

19.03.2009 17:22:11 casapci_CAP_32 WHS 300 C RAISE_EXCEPTION

19.03.2009 17:22:10 casapci_CAP_32 WHS 300 C RAISE_EXCEPTION

19.03.2009 17:22:09 casapci_CAP_32 WHS 300 C RAISE_EXCEPTION

19.03.2009 13:30:49 casapci_CAP_32 SATIMANSO 300 C CALL_FUNCTION_REMOTE_ERROR

19.03.2009 11:57:41 casapci_CAP_32 WF-BATCH 300 C COMPUTE_BCD_OVERFLOW CX_SY_ARITHMETIC_OVERFLOW

19.03.2009 07:52:32 casapci_CAP_32 MTD4 300 C RAISE_EXCEPTION

[Former Member · Accepted solution]

Hi,

I am suggesting you to read the complete information which contained in the ABAP Dump.

Eg: in your sample code i could see lot of RAISE_EXCEPTION Dumps.

what i am trying to explain is u need to read complete information abt the dump in ST22 because some times exception conditions are different for every Entry of RAISE_EXCEPTION.

eg: table_illegal exceptions, insertion of data exceptions etc...

depends on exception conditions only u can find the solutions in OSS notes.

-Srini

Edited by: Srinivas Korva on Mar 20, 2009 10:50 AM

[former_member187565 · Accepted solution]

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.

[Former Member · Accepted solution]

hi Neo

may I ask, in which case we have to pay full attention on abap dump?

what error indicate the serious problem??

thanks

[Former Member]

Rosa,

I would suggest you to check following transaction minimum. At Operating system level you can check the space by using bdf command.

SM51 Check the status of application servers

SM50 Process overview

SM37 Scheduled jobs

SM12 Application Locks

DB01 Oracle Locks

DB12 Backups and space in Archive log directory

DB14 DBA operation logs

ST02 Tune Buffers/ Check for buffer swaps

ST06 Operating system monitor check for CPU utiliztion,

Swapping and disk utilization

ST04 Database performance. Checks for data buffer quality etc

SM21 Check system log

ST22 ABAP dumps. Find out all the error/warning and take appropriate action

ST03 Reponse time/ Top SQLs etc

SM04 Check users list

Hope this helps.

Manoj

[Former Member]

Hi,

CPU Idle OS06 -> detail analysis button -> compare recent days

Total steps ST03 -> Expert mode -> Load History and Distribution -> Load History -> Choose total -> Choose other task type -> Total -> record the number under Dialog Steps.

Total Average Response Time (seconds)ST03 -> Expert mode -> Load History and Distribution -> Load History -> Choose total -> Choose other task type -> Total -> record the number under Avg Response Time.

Dialog steps ST03 -> Expert mode -> Load History and Distribution -> Load History -> Choose total -> Choose other task type -> Dialog -> record the number under Dialog Steps.

Dialog Average Response Time (seconds) ST03 -> Expert mode -> Load History and Distribution -> Load History -> Choose total -> Choose other task type -> Dialog -> record the number under Avg Response Time.

Lock Entries SM12

Cancelled Jobs SM37 -> Choose cancelled, all users, all jobs from yesterday to today

Short Dumps ST22

Max Memory Used (3GB max) ST02 -> Under SAP Memory at the bottom, record the number in row u2018Extended Memoryu2019 under column u2018Max Useu2019

Total User Count ST03 -> Load Distribution -> Users per instance

Program Buffer Swaps ST02 -> Record the value for Program Buffer Swaps

Generic Key Buffer Swaps ST02 -> Record the value for Generic Key Buffer Swaps

Single Record Buffer Swaps ST02 -> Record the value for Single Record Buffer Swaps

DB Size (MB) DB02 -> DB Space History Button -> Per Day button -> record number in ALLOCSPACE column for previous day

DB Utilized ( MB) Same as above, just record DBSIZE column instead

SQL Hit Ratio ST04 -> Detailed Analysis -> Server Detail Button -> Cache Detail Tab -> bottom number under hit %

Hope the above information will helps you.

-Srini

[Former Member]

Hi

(1)SM51

(2)'/usr/sap' Be sure used<=70%

(3)SM37

And some DB relevant Tx.

[manu_susankar]

Hi Rosa Della,

Could you please check this [Help Doc|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/baac25ca960611e10000000a42189b/frameset.htm]

for the [Monitoring the Memory Management System |http://help.sap.com/saphelp_nw04/helpdata/en/02/96263e538111d1891b0000e8322f96/content.htm]ore information and configuration...

Regards,

S.Manu.