WCCILdata - IMPL/WARNING - DataManager, mainLoop, Last alert fileswitch not completed - restarting timer

The following log message can be displayed during the startup of the project. The log message is written to the PVSS_II.log-file.

WCCILdata (0), 2012.01.12 18:44:59.466, IMPL, WARNING, 54, Unexpected state, DataManager, mainLoop, Last alert fileswitch not completed - restarting timer

The log message with symbolic names:

WCCILdata(0), <TIMESTAMP>, IMPL, WARNING, 54, Unexpected state, DataManager, mainLoop, Last alert fileswitch not completed - restarting time

This log message describes that last alert fileswitch in the RAIMA database was not finished before the project was stopped.

If the project is stopped while the "round off"-timer is running, the timer is restarted after the startup and the log message is written.

When a fileswitch of the RAIMA-alert-database is made, the previous fileset and the new fileset remain open for a given time. The name for the new fileset-directory is a 10-digit-number in seconds since 1970.01.01 00:00 which is the time when the fileset-change was started. Especially in redundant systems this is necessary to achieve that the filesets get the same number.

The value for the "timer" is defined with the dp-elements _DataManager.AlertDataSetChange.SwitchTime and

_DataManager_2.AlertDataSetChange.SwitchTime. Normally the value 0 is set.

In redundant projects the "timer" is set by using the config entry fileSwitchRoundOff.

In the standard config.redu-file the "round off" time is specified by using the config entry fileSwitchRoundOff with a time of 3600 seconds.

If no value is specified, the "round off" time is 60 seconds.

When a fileswitch is made, a timer is started to avoid fileswitches in too short intervals.

Within this timespan, a new fileset-change cannot be started.

If the problem occurs at the startup or at the time when the next fileswitch should be executed (configured via System Management --> Database --> Archive, Export Raima) , this could lead to inconsistencies of the alert database.

To repair the inconsistencies:

  • Stop the WinCC OA project
  • Copy the database without the value-archive directories
  • Open a DOS-box/command shell
  • Move to the directory <WinCC OA project>/db/wincc_oa
  • Remove the vista.taf file by using the rm command
  • Start the command "wida" (Windows) or “ida” (Linux). This is a tool for the modification of the RAIMA-database

When using Windows, proceed as follows in the tool “wida”:

  • File --> Open Database --> AlertDir.dbd
  • Record --> Scan by Key --> ALERTDIRKEY --> Scan
  • In the next dialog click on "Last"
  • Scroll to the end of the list
  • Save the value "2" on the next to last line
  • Select the next to last line
  • Click on "Select"
  • Double-click on "Flags"
  • Enter the value "0"
  • Click on "OK" and "Store"

A dialog with the information that the record was modified will be displayed.

  • Click on "OK"
  • Scroll to the end of the list
  • Save the value "1" on the last line
  • Select the last line and click on "Select"
  • Double-click on "Flags"
  • Enter the value "0" and click on "OK"
  • Click on "Store"

A dialog with the information that the record was modified will be displayed.

  • Click on "OK"
  • Select File --> Close Database
  • Select File --> Quit

On Linux systems keyboard commands are used for the operation of the tool "ida".

The following commands must be executed. In the description below you can find the names of the commands. The keyboard character which must be used is marked with double quotes. If a sequence needs to be executed, it is described as “step 1” – “step 2” – “step 3” …

  • Use “o” to open
  • Select One_user via “o”
  • Select the entry 5. AlertDir “5” – “Enter” – “Enter”
  • Access by using “a”
  • Record by using “r”
  • Use the character “k” for Keyscan
  • Scan via “s”

+ Select the entry ALERTDIRREC.ALERTDIRKEY “1” – “Enter” – “Enter” – “Enter”

Now the list of alert filesets will be displayed. The first entry on every line is the number of the fileset.

  • Go to the end of the list by using Next “n”
  • Select the the next to last fileset via “s”
  • Enter the number of the next to last fileset “<number>” – “Enter” – “Enter”

Now the information for the fileset is displayed. For the field FLAGS the value “2” will be displayed.

  • Use “x” to X_exit
  • Use “m” to Modify
  • Use “e” – “Enter” – “Enter” – “Enter” to Edit
  • The field “FLAGS” is now selected.
  • Modify the status (VI style) and set the value “0” – “Enter”
  • Use “w” to Write

At the bottom of the screen the information is displayed that the record was modified.

  • Use “x” to X_exit
  • Use the character “k” for Keyscan
  • Scan via “s”
  • Select the entry ALERTDIRREC.ALERTDIRKEY “1” – “Enter” – “Enter” – “Enter”

Now the list of alert filesets will be displayed. The first entry on every line is the number of the fileset.

  • Go to the end of the list by using Next “n”
  • Select the last fileset via “s”
  • Enter the number of the last fileset “<number>” – “Enter” – “Enter”

Now the information for the fileset is displayed. For the field FLAGS the value “1” will be displayed.

  • Use “x” to X_exit
  • Modify by using “m”
  • Use “e” – “Enter” – “Enter” – “Enter” to Edit

The field “FLAGS” is now selected.

  • Modify the status (VI style) and set the value “0” – “Enter”
  • Use “w” to Write

At the bottom of the screen the information that the record was modified is displayed

  • Use “x” to X_exit until the first selection list is displayed (command Quit at the end of the line)
  • Quit via “q”

The state of the alert-filesets was modified meaning that the state "online" was set for these two alert filesets.

  • Start the WinCC OA project
  • During startup check the log-messages to detect possible error messages of the alert database
  • Check that the automatic filesetswitches are executed at the next fileswitch-time.