After a long period of absence, I posted something today and once again sat with some materials of writing on SAP monitoring ……Configuration of of central monitoring system with Solution Manager etc….How about creating a new section as ‘/log’? Logs and alerets are something indispensibale part of the monitoring….
I was preparing a document on solution manager configuration. I was going thru my old piece of papers where I used to scribble thru with some vital informations….Thought before organising better to write it here….
Note 796998 – CCMS: Setting titles for alert mails
Note 176492 – Automatic email when an alert occurs (RZ20)
Note 1525363 – CCMS: Client and User fields in alert email
Note 934834 – CCMS: CCMS_OnAlert_Email parameter TIME_ZONE
Very important to use with escalation
Note 617547 – RZ20: Sending alerts as mail and SMS
All these are actually read and used during configuration of central monitoring…….
One puzzling thought came into my mind. I am running a SAP landscape with a Disaster Recovery(DR) server. This is configured using the Oracle dataguard facility. So the database remains at the standby phase and SAP instance kept shutdown. So that data replication goes on and whenever I am in disaster I can fail over to DR by activating and opening the standby database in read write mode and then starting the SAP instance
Now the question is……..
The Oracle database of SAP system is kept in standby mode this can not be kept in read/write mode because it breaks the Oracle dataguard combination with the primary active SAP instance. The health of the standby (DR) system is actually very important, because you never know when you do require to fail over to DR. In this condition how solution manager can help out? As database is in standby mode you can not start SAP instance and if SAP instance is not started yet, how does solution manager can help?