What is OSS Notes?
OSS NOTES is an internet based SAP administration entry that gives modern data on SAP notes. It often delivers bug fixes, patches, new program advancements or improvements and other various updates by SAP. It gives a rundown of rectification notes for SAP objects. OSS means "Online SAP Support."On occasion before you start work, it will be expected to check whether a specific note is available in your SAP frameworkTo guarantee that a specific OSS note is available in your SAP framework, execute the accompanying advances:In SAP order brief, Enter TCode # SNOTE
What is OSS Notes? SAP SNOTE Tutorial
Framework observing is an everyday schedule movement and this report gives a deliberate bit by bit technique for Server Monitoring. It gives an outline of specialized viewpoints and ideas for proactive framework checking. Not many of them are:
Really taking a look at Application Servers.
Checking extensive Work Processes.
Checking Work Processes for Individual Instances.
Checking Lock Entries.
Computer processor Utilization
Accessible Space in Database.
Observing Batch Jobs
Spool Request Monitoring.
Number of Print Requests
ABAP Dump Analysis.
Information base Performance Monitor.
Information base Check.
Observing Application Users.
Why Daily Basic checks/System Monitoring?
SAP Monitoring and Performance Checks: Complete Tutorial with TcodesActually taking a look at Application Servers (SM51)This exchange is utilized to really look at all dynamic application servers.Here you can see which administrations or work processes are designed in each occasion.Checking Work Processes for Individual Instances SM50:Shows generally running, pausing, halted and PRIV processes connected with a specific occasion. Under this step we really take a look at every one of the cycles; the interaction status ought to continuously be pausing or running. On the off chance that any cycle is having a status other than pausing or running we really want to as needs be actually take a look at that specific interaction and report.This exchange shows a great deal of data like:Status of Work process (regardless of whether it's involved)Assuming the work cycle is running, you might have the option to see the move made by it in the Action segment.You might which at any point table is being worked upon
A portion of the normal issues:
The client consumes most of the day to sign on/not ready to logon/online exchange extremely sluggish. This could be the consequence of the DIA work processes are completely used. There could be additionally the consequence of long running position (red marker under the Time section). On the off chance that essential you can drop the meeting by choosing the positions then go to Process>Cancel Without center. This will drop the work and delivery the work cycle for other client/processA few clients might have PRIV status under Reason segment. This could be that the client exchange is huge to such an extent that it requires more memory. At the point when this happen the DIA work cycle will be 'claimed' by the client and won't allow different clients to utilize. In the event that this occurs, check with the client and assuming conceivable run the occupation as a foundation work.In the event that there is a long print work on SPO work process, explore the issue. It very well may be an issue connected with the print server or printer.Observing far reaching Work Processes (SM66)SAP Monitoring and Performance Checks: Complete Tutorial with TcodesBy checking the work cycle load utilizing the worldwide work process outline, we can rapidly research the possible reason for a framework execution issue.Screen the work interaction load on all dynamic examples across the frameworkUtilizing the Global Work Process Overview screen, we can see initially:
The situation with every application server
The justification for why it isn't runningWhether it has been restartedThe CPU and solicitation run timeThe client who has signed on and the client that they signed on toThe report that is runningYet, in the event that the Update isn't dynamic then see as the beneath data:Is the update dynamic, in the event that not, was it deactivated by the framework or by a client?Click on SAP Monitoring and Performance Checks: Complete Tutorial with Tcodes button and get the data.Click on SAP Monitoring and Performance Checks: Complete Tutorial with Tcodes button and get the beneath data:
Is any update dropped?
Is there a long line of forthcoming updates more seasoned than 10 minutes?Observing Lock Entries (SM12)Execute Transaction SM12 and put '*' in the field User NameSAP gives a locking system to keep different clients from changing the record that you are dealing with. In certain circumstances, locks are not delivered. This could occur assuming that the clients are cut off for example because of organization issue before they can deliver the lock.These old locks should be cleared or it could forestall access or changes to the records.We can utilize lock measurements to screen the locks that are set in the framework. We record just those lock passages which are having date time stamp of the earlier day.
Observing System Log (SM21)
We can utilize the log to pinpoint and amend blunders happening in the framework and its current circumstance.We really look at the log for the earlier day with the accompanying determination/choice:Enter Date and time.Select Radio Button Problems and WarningsPress Reread System Log.