SAP NW Newbie

There are always those important transactions that business users execute on a regular basis and cannot accept it to take too much time. One of the important aspects of addressing bad response on a transaction code is to be able to measure and alert if the response time is tending to increase. If you get an alert you might be able to check the reason for slowness before a widespread impact on business occurs. Log on to your CCMS system Call transaction SE16 and give the table name ALTRAMONI If you want to set alert on the response time of the entire client, you have to set TCODE as * and MON_CLIENT as the client number (for example 100 if the business client is 100) If you want to set alert on the response time of the transaction MIRO on client 100, set TCODE as MIRO and MON_CLIENT as 100. Set MO_NAME to aptly describe what the alert is about. Ex: "Avg response time on txn MIRO on 100 client" Set MTECLASS as you see fit. Ex: "MIRO100RESP" Set SERVER ID to...

You can find out all the indexes that are corrupted by matching up v$database_block_corruption view. Let's begin with formatting the output: set pagesize 50 linesize 170 col segment_name format a30 col partition_name format a30 Now the following SQL will list out the corrupt indexes: select distinct file#,segment_name,segment_type, TABLESPACE_NAME, partition_name from dba_extents a,v$database_block_corruption b where a.file_id=b.file# and a.BLOCK_ID <= b.BLOCK# and a.BLOCK_ID + a.BLOCKS  >= b.BLOCK#;