This action might not be possible to undo. Are you sure you want to continue?
Description 1. Check Long running job. (Job running for more than 12 hours (43200 Secs) 2. Check for Status other than Running 3. Check for semaphore 1. Check for old lock entries (Genral more than 1 day . For special case 2 days) 2. No of entries 10,000 1. Check for old terminated updates. 2. Check for status other then 'err' 3. Check for number of pending updates
1. Call or send a mail to user confirming the runtime for the same. 2. Depends on problem we need to react 3. Depends on problem we need to react 1. Check if there is any active job is running for that user. If not then raise service call to HP for clearing old lock entries for respective users. 2. Monitor the system closely & Analyse 1. Analyse the update & check with AM team if this can be reprocessed 2. Analyse the update & check with AM team if this can be reprocessed 3. If pending updates are more than 1000 either raise ticket to HP/AM or analyse 1.Create ticket to AM Team with collected data 1.If instance is not active raise ticket to HP 1. There should not be any entry
ST22 SM51 DB01 ST02
Daily Twice in a day Twice/Thrice in a Day Thrice in a day
1. Check for the dump which is appearing more than 20 times 1. Check for no of instances along with status status. 1. Oracle Lock Monitor
1. Ensure Hit ration for each buffer is more than 95 %. 2. Some times if hit ratio is below 95 % & no Swaps you can ignore it. 3. Ensure extended memory should not cross more than 80% use. 4. Please check the following thresholds for SWAPS for individual Buffer. Program Buffer = 10000 hits per day Othe Buffer's 1000 per day 5. If no free space & Free Directory then create ticket to HP for increasing value ST03N Daily For each server note down the dialog average response time for yesterday 1. Check following paramaeters for DIA. (Workload should be checked for Total) Dia. Response time DB Response Time Gui Time Network Time. Compare all these times with previous data. If there is sudden increase then analyse & corrective action 2. Check for TOP 5 response time transactions weekly once 3. Check for collector status ST04 Daily Oracle Database Overview
Check following settings for all instances 1. Check for Data Buffer quality. It should be above 95 %. 2. Check for DD Cache quality . It should be above 97 %. 3. Check for Read/User Calls. It should be below 40. 4. Check for database message log in detail analysis menu. Please check for errors & warnings.
Ideally 60 % should be free. Check if there are too meny old entries 1. Check for the database health 1. Use this transaction for checking trace files Daily Three/Four times in a week Weekly 1. ST05/ST01 ST10 SLG1 AL11 As & when required As & when required Daily As & when required 1. Use this transaction if you want to find out user across the application servers 1. Check for the entris with status " error" . "Processed" . It should be zero. If error please report to AM Team using WIH ticket . If there are entries analyse & take appropriate action DB16 SMQ1 Daily Twice in a day SMQ2 Twice in a day 1. Check for repetative cancelled jobs 3. If problem is reported use this transaction for analysis 1. check for Collisions & errors (in/out). Check for the errors 1. If issue create ticket to HP 1. (Compare previous week) 1. Check if there are any long running queues 1. If too meny entries are pending create ticket to AM Team if these can be reprocessed 2. 2. DB12 Daily Backup Log overview SM37 Twice in a day SMLG DB16 DB14 Twice in a day Daily Daily 1. Check if optimizer runs successfully 2. Check for Errors & Warnings 1. Use menu "All" or " Brconnect. Check for APQD table entries. Page out/s should be 0.Oracle error. 5. If any problem please create ticket to HP 1. If too meny old entries . If entry exist create ticket for AM team if those entries can be Reorganised or processed. Use this transaction for putting trace in system 1. Check for the old entries 1. If entries are there create ticket to AM Team 1. Check for connections with error status 1. Disk reponse time should be <= 10 ms Queue Lenth should 3. 2. If too meny entries are pending create ticket to AM Team if these can be reprocessed 2.12 & 51 please investigate & create ticket to AM Team 1. Under LAN . raise ticket for AM team if this can reorganised 1. " To be processed". Please check if there are entries with error/Pending status 1. If too meny old entries . Check for the old entries SM58 BD87 SMQR SMQS AL08 SMGW SM21 SM35 Daily Thrice in a day Daily Daily 1. Use this transaction for analysing performance related issue's 1. If unsuccessful please create ticket to HP 2.12 & 51. Check last successful run for that job (time taken). Check if standard house keeping jobs are running 1. Check for load distribution across all application servers Database chek 1. 2. 1. … 1. Check for the pending entries 2. Analyse & take appropriate action 1. If too meny Idocs with status other than 03. Check long running active jobs (Check for last one week) 2. CPU Utlization.ST06 Daily Operating System Monitor Check for following utlization in all instances 1. If current job is taking more time then check with user & take appropriate action 1. If entries are there with 'error' create ticket to HP Team 1.System Errors etc. Check for successful backups/Archive log/Archive ditectory If backup failed for last three days then put status as red in weekly report. Check for OS collector log. Check for the pending entries 2. Check for Errors or warnings & take corrective actions 1. 4. Check for backup duration. raise ticket for AM team if this can reorganised 1. Run a check-status forthat job. Check for Database errors. If any issue raise ticket to HP 1. Please check for the Idocs other than status 03.
Use this transaction for anaysis purpose (To check trace file & logs) .RZ03 As & when required 1.