In System Monitoring, alerting has been configured for Oracle Messages Ex. ORA-01654. The Collection Interval is given as Hourly. When an ORA Error message comes up in DB02 at 06:00:00, the system picks up the error and provides an Alert. The Alert always references to this timeline, namely 06:00:00, for all the other Data Collection runs also. This leads to a scenario wherein you would have to wait for almost 24 hours for the next alert to be generated. In the Managed System, which has Oracle as Database, the DB02 job runs daily at 06:00:00 hrs. The job uses the program RSDBAJOB. If we check DB02 in the Managed system, it gives the list of ORA Error messages as stated in the following example:
Scenario: Say the Job Run at 06:00:00 was successful and had no ORA errors. If an ORA error happens after the DB02 Job run, say at 06:30:00 hrs. then the system will create an Alert only after 23 hours and 30 minutes, i.e., after the next day’s DB02 Job run, since the reference taken for all the subsequent Data Collection run is the image which happened at 06:00:00 hrs., which was successful. So we would like you to take a look into this issue wherein Solution Manager takes the reference of DB02 errors for all the subsequent Data Collection runs and instead Solman needs to check the present status of the ORA Error Messages at every Data Collection time.
SAP Solution Manager 7.2
Solman, Oracle Error Messages, Alerts Delayed, RSDBAJOB, DB02 , KBA , SV-SMG-MON-ALR , Monitoring/Alerting/Reporting Infrastructure , SV-SMG-MON-ALR-CFG , Alert / Metric Configuration , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.