How to initialize the RAIMA-database for the living alerts?
The living alerts are stored in the alliving-folder of the RAIMA-database. When starting the project the current/living alerts are read from this part of the database and send to the event-manager. If an alert is changed the changes are send to the data-manager to store the information in the alliving.
Due to powercuts or other problems with the hardware sometimes this part of the database gets corrupted, which results in problems when saving living alerts or changes at living alerts documented with log-message which refer to this error.
In most of the cases one of the following words is displayed at the log-message: alliving, AlertHist, AlertCacheItem
With an initialization of this part of the database you can get rid of this error.
To initialize this part of the database please perform the following steps, in case of a redundant system you would have to stop the project on both servers at the same time. The initialization is only necessary at one server, the other one will copy the corrected database parts during the recovery:
Please note that all living alerts will be deleted during this procedure.
-- Stop the project
-- Copy the db-folder to create a backup, when using value-archives it is not necessary to copy the VA-folders
-- Open a command shell
-- Go to the directory <WinCC OA project>/db/pvss/alliving or <WinCC OA project>/db/wincc_oa/alliving
-- Start the command <WinCC OA installation>/bin/initdb –y AlertHist
-- Start the project and check the logs during startup
During startup of the project all alerts will be raised again automatically if the current value exceeds one of the alert thresholds.
The AEScreen will show all pending alerts in status "CAME" after the startup. The number of pending alerts before and after this procedure will be different as alert pairs which have been in state CAME/GONE will not appear again as there are already gone before the initialization was made. Alerts in this state cannot be recovered and only pending alerts will appear.
If you have additional questions please get in contact with your common WinCC OA support.