17
System Health Check Training 19 th March 2015 By: Aslaily Abd Manan

Ingress Training

Embed Size (px)

DESCRIPTION

Ingress

Citation preview

Slide Title

System Health Check Training

19th March 2015By: Aslaily Abd Manan

2015 ABeam Consulting Ltd. Confidential001AgendaIntroductionSAP MonitoringDB MonitoringOS MonitoringConclusion 2015 ABeam Consulting Ltd. Confidential1IntroductionSAP Monitoring:Why? It provides the windows of things to happenWhat? SAP application, Database health and OS health checksWho? System AdministratorWhen? Subjective but in a nutshell, its supposed to be a daily routine job by the system administrator. For example: What time is supposed to complete? If it failed what would be the next action plan.2 2015 ABeam Consulting Ltd. ConfidentialSAP MonitoringFirst thing first:Are you able to login?If not please check the normal scenarios below;a) Correct information in the SAP GUIb) Network connectivityc) SAP services are up and runningBy right we should be seeing this:

3

2015 ABeam Consulting Ltd. ConfidentialSAP MonitoringOnce login, we are able to do the normal monitoring:Listed here are the general t-codes we used to do system monitoring:SM51SM50SM12SM13ST22SM21SM37DB12DB13SP01ST03NSP12ST06DBACOCKPITSA38Whatever listed here should only be seen as guided reference.

4 2015 ABeam Consulting Ltd. ConfidentialSAP Monitoring (SM51)SM51 - List of SAP Servers display list of active application servers that have registered in the SAP message server. manage & display the status, users, work process in all application servers belonging to the SAP System.

5

2015 ABeam Consulting Ltd. Confidential1) SMLG = display global user list5SAP Monitoring (SM50)SM50 - Work Process Overview used to monitor and manage work processes.a) DIA: Work process for executing dialog steps in user transactions.b) UPD: Update process for making U1 (time-critical) database changes.c) UP2: Update process for executing U2 (not time-critical) database changes.d) ENQ: For locking or releasing SAP lock objects.e) BTC: For processing background jobs. f) SPO: For spool formatting processes.

6

Process ID of the work process (on the operating system) Running (executing a request) Waiting (idle and waiting for work) Hold (held for one user) is not an abnormal state, but a work process can only serve a single user. Stopped (aborted with Restart set to No) 2015 ABeam Consulting Ltd. Confidential6SAP Monitoring (SM12)SM12 - Display and Delete Locks SAP System is equipped with a special lock mechanism that synchronizes access to data on the database.The purpose of the lock mechanism is to prevent two transactions from changing the same data on the database simultaneouslyLock entries are usually set and deleted automatically when user programs access a data object & release it again. If any outdated entry found, go to AL08 or SM04 to get the transaction code that been use by the user. Release the table from lock by deleting the lock.

7

2015 ABeam Consulting Ltd. ConfidentialSAP Monitoring (SM13)SM13 - Display Update RecordsWith update management, we can perform following tasks:a) Display update requestsb) Analyze problems relating to the updatec) Test and clean up canceled update requestsd) Display and reset the status of update requestse) Delete update requests f) Display statistics on the update

8

2015 ABeam Consulting Ltd. Confidentialc) Goto Administration System >Reorganize update requests.f) Goto Administration System > choose Statistics.8SAP Monitoring (ST22) 1 of 2ST22 - ABAP Runtime Errorlist the ABAP runtime errors that have occurred in an ABAP system as well as the relevant short dumps.To allow clearer processing, the runtime errors are divided into categories. The category of the runtime error returns hints on cause of the error and troubleshooting.

9CategoriesDescriptionInternal Kernel ErrorError in ABAP Kernel.Recommendation Sending an error message to SAP.Errors in the ABAP runtimeErrors in the screen runtimeErrors in the database interfaceThe system was able to roughly determine the area in which the error occurred. Next, clarify whether it was triggered by an internal error or by a programming error.Resource bottleneckExample: SYSTEM_NO_ROLL: The application does not have enough memory available. 2015 ABeam Consulting Ltd. Confidential9SAP Monitoring (ST22) 2 of 210

2015 ABeam Consulting Ltd. Confidential10SAP Monitoring (SM21)SM21 - System Logcan use the log to pinpoint and correct errors occurring in your system and its environment.

11

2015 ABeam Consulting Ltd. ConfidentialSAP Monitoring (SM37)SM37 - Background Job Overview SAP background processing allows the automation of routine tasks. 12

2015 ABeam Consulting Ltd. ConfidentialSAP Monitoring (SP01)SP01 - Output Controlleruser can manage the spool and output requests in the Output Controller. In the output controller, we can:a) Specify selection criteria for displaying spool and output requests. A list of spool or output requests that match these criteria appears.b) Output spool requests, that is, print them.c) Display detailed data about a spool or output request and change certain attributes, such as destination printer and number of copiesd) Display the data to be printed and export it in different formats.e) Delete requests.

13

2015 ABeam Consulting Ltd. ConfidentialSAP Monitoring (SP12)SP12 TemSe Administration to display and manage TemSe objects.TemSe is a store for temporary sequential data; that is, objects that are not normally permanently held in the system are stored in the TemSe.The spool system uses the TemSe to store output data temporarily.We can set whether the spool data is to be stored by TemSe in the SAP database or in the file system

14

2015 ABeam Consulting Ltd. ConfidentialAOB15 2015 ABeam Consulting Ltd. Confidential

2015 ABeam Consulting Ltd. Confidential16