Grim Reaper

Hello,

Previous versions of WinCC did not have segmentation concept in audit trail. The present version 7.5 and above has segmentation concept. When using the OCX control of Audit trail and segment of the specified database can be combined similar to alarm logging and trending. However the issue occurs when ODBC connection is established to pull data from the audit trail database.

We've named the database as WinCC_Audit and segments formed look like... 

1. WinCC_Audit_TEST-SUENDRA_Audit_20220822113240_20220823142258 - completed segment

2. WinCC_Audit_TEST-SUENDRA_Audit_20220823142258 - running segment

When the time interval specified crosses over from the completed segment to the running segment the OCX can manage it, however the in wincc report we've used ODBC table which restricts the data to the connected segment only. If the generalized table name (WinCC_Audit) is specified there is a connectivity error.

How can we over come such a situation? 

There are 2 solutions in my opinion

1. Combining all the segments - which I am not sure of how to proceed with.

2. Prevent segmentation - which can be done by incrementing time of segment change to the year 2100 (by which time we might be probably gone or the system might be replaced).

Request any suggestions or recommendations to overcome this issue. Kindly pass on your suggestions.

Best Regards

 Hi

Did you find any solution about it. I am facing same problem here.

if you find any solution please share with me. It will help me.

Thanks in advance

------------------------------------------------------------------------------------------
Split from Wincc7.5SP2 Audit trail and segmentation.

 Same problem, i also have put support request, but yet not any reply from siemens, dont know on which base siemens modify features of their products.

Grim Reaper

Hello,

Previous versions of WinCC did not have segmentation concept in audit trail. The present version 7.5 and above has segmentation concept. When using the OCX control of Audit trail and segment of the specified database can be combined similar to alarm logging and trending. However the issue occurs when ODBC connection is established to pull data from the audit trail database.

We've named the database as WinCC_Audit and segments formed look like... 

1. WinCC_Audit_TEST-SUENDRA_Audit_20220822113240_20220823142258 - completed segment

2. WinCC_Audit_TEST-SUENDRA_Audit_20220823142258 - running segment

When the time interval specified crosses over from the completed segment to the running segment the OCX can manage it, however the in wincc report we've used ODBC table which restricts the data to the connected segment only. If the generalized table name (WinCC_Audit) is specified there is a connectivity error.

How can we over come such a situation? 

There are 2 solutions in my opinion

1. Combining all the segments - which I am not sure of how to proceed with.

2. Prevent segmentation - which can be done by incrementing time of segment change to the year 2100 (by which time we might be probably gone or the system might be replaced).

Request any suggestions or recommendations to overcome this issue. Kindly pass on your suggestions.

Best Regards

Closed cause question posted twice.

The second thread with the subject Audit Trail Custom Report Generation and SQL query for reading Audit Trail from DB is published within the conference SIMATIC WinCC.

Best regards,
Jen_Moderator
​