Help Articles: Initialize RAIMA-Database for Living Alerts

Back to All Topics

Introduction

If you have crashed your WinCC OA project and received any of the following errors in your log viewer, then this help article is for you.

  • Error code SEVERE, 69, Database error, AlertCacheItem, loadComment, Code :0
  • Other associated errors: alliving, AlertHist

Summary

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 sent to the data-manager to store the information in the alliving.

Due to failure 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. 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:

Note(s)

  • Please notice that all living alerts will be generated with the current timestamp during the procedure.
  • Command shell: To navigate to your home directory, use “cd” or “cd ~” To navigate up one directory level, use “cd ..” To navigate to the previous directory (or back), use “cd -” To navigate into the root directory, use “cd /”

Procedure to Initialize RAIMA Database

  1. Make an ASCII-export for the _alert_hdl-configuration using the filter P + _alert_hdl for the ASCII-manager into the file alert_hdl.asc
    • If the ASCII manager is started from a command shell the following command is started. Before starting the command you have to go to the dplist-directory of the project. On Linux operating systems is has to be ensured that the environment variables PATH and LD_LIBiAiY_PATH are set correctly and include the bin-directory for the WinCC OA installation.
    • <WinCCOA installation>/bin/PVSS00ascii –proj <project name> -filter P:_alert_hdl -out alert_hdl.asc
    • <WinCC OA installation>/bin/WCCOAascii -proj <project name> -filter P -out alert_hdl.asc
  2. Stop the project
  3. Copy the db-folder to create a backup, when using value-archives it is not necessary to copy the VA-folders
  4. Open a command shell
  5. Go to the directory <WinCC OA project>/db/pvss/alliving or <WinCC OA project>/db/wincc_oa/alliving
  6. Start the command <WinCC OA installation>/bin/initdb –y AlertHist
  7. Start the project in the minimum configuration: data-manager + event-manager
  8. Make an import of the ASCII-file alert_hdl.asc
    • If the ASCII manager is started from a command shell the following command is started. Before starting the command you have to go to the dplist-directory of the project. On Linux operating systems is has to be ensured that the environment variables PATH and LD_LIBRARY_PATH are set correctly and include the bin-directory for the WinCC OA installation.
    • <PVSS installation>/bin/PVSS00ascii –proj <project name> -in alert_hdl.asc -inactivateAlerts
    • <WinCC OA installation>/bin/WCCOAascii -proj <project name> -in alert_hdl.asc -inactivateAlerts
  9. Wait until the import is finished
  10. Stop the project
  11. Start the project in normal configuration
  12. Check if the project is running correctly
Was this article helpful?
How can we improve this article?
Scroll to Top