PVSS00data - PARAM/WARNING - workProcAlert, Cannot get attribute - will use dummy
Enclosed you'll find the explanation for a block of log-messages which can occur during startup of the project or during runtime. The log-messages are written to the PVSS_II.log-file.
PVSS00data (0), 2012.09.20 17:12:27.095, IMPL, WARNING, 54, Unexpected state, DataManRequestHandler, workProcAlert, Cannot get attribute - will use dummy
System1:ExampleDP_AlertHdl1.:_alert_hdl.._panel (Type: 0 Sys: 1 Dp: 98 El: 1 : _alert_hdl.._panel)
PVSS00data (0), 2012.09.20 17:12:27.095, PARAM,WARNING, 46, Attribute was not archived, DataManRequestHandler::RqItemSetHandlergetAlertClassAttribute, Notification class not found - Standard class is being used
(Type: 0 Sys: 1 Dp: 98 El: 1 : _alert_hdl..0)
Log-message with symbolic names:
PVSS00data (0), <TIMESTAMP>, IMPL, WARNING, 54, Unexpected state, DataManRequestHandler, workProcAlert, Cannot get attribute - will use dummy
<DPE-name>:<_alert_hdl-attribute> (<DPE-ID> : >:<_alert_hdl-attribute>)
PVSS00data (0), <TIMESTAMP>, PARAM,WARNING, 46, Attribute was not archived, DataManRequestHandler::RqItemSetHandlergetAlertClassAttribute, Notification class not found - Standard class is being used
(<DPE-ID> : _alert_hdl..0)
These log-messages can occur when doing historical alert queries. They describe that not all the information could be read from the RAIMA-database. The missing part of the information is normally read from the configuration-history, this is a special part of the database.
The basic and most interesting information for the alerts (dpe-name, timestamp, value which caused the alert, priority, alert-text, direction,acknowledge-time) is still available.
The log-entries will occur when one of the following two procedures was used within this system:
-- deletion and recreation of the datapoint with the same DP-ID: When deleting a datapoint the entries for this datapoint in the configuration-history are deleted automatically. This is necessary to avoid that the configuration-history is filled up with information for non exisiting datapoints.
-- initialization of the configuration-history: The initialization can be made with some manual steps when the project is stopped using the command “initdb”. Normally it is not necessary to make this initialization.
Before you try to make this initialization in one of your projects please contact your common WinCC OA support to avoid data loss.
The log-message will only occur if you are requesting historical information before one of these procedures was used. Alerts which are generated afterwards can be read with the complete information and without any log-messages.