NGA support for non-redundancy-aware external influx DB

Discussion about recent product features & solutions!
Search

Post Reply
5 posts • Page 1 of 1
mzugelj
Posts: 9
Joined: Fri Apr 06, 2018 10:35 am

NGA support for non-redundancy-aware external influx DB

Post by mzugelj »

Hi,

I am using WinCC OA 3.17 P004 on Windows server 2019 standard OS. As explained from your side, archiving design as displayed in Figure 1 is not supported yet, so I am testing the next viable option, as indicated in Figure 2.

Figure 1:
Image

Figure 2:
Image

The issue that I am observing with Figure 2 design is that DB schema of winccoa database in external influx databases is not updated (even if I add a new archiving group) while DB schema of winccoa database in local influx database is updated correctly.
Is it possible that I missed some step in configuration of Remote backends or is it required to update external influx DB schema manually each time an archive group is added or when retention policy is changed in WinCC OA Sys Mngmnt -> Database Configuration?

Best regards,
Matevž Žugelj

mzugelj
Posts: 9
Joined: Fri Apr 06, 2018 10:35 am

Re: NGA support for non-redundancy-aware external influx DB

Post by mzugelj »

Correction: Figure 2 should display "External DB PC 1" and "External DB PC 2"

User avatar
leoknipp
Posts: 2926
Joined: Tue Aug 24, 2010 7:28 pm

Re: NGA support for non-redundancy-aware external influx DB

Post by leoknipp »

Do you know if the remote database works correctly if only the backend for the remote database is used/activated?

You have written that you have installed 3.17 P004.
Please do an upgrade to the newest patch for 3.17 as with P010 a lot of changes/improvements have been made in the NGA manager.

Best Regards
Leopold Knipp
Senior Support Specialist

mzugelj
Posts: 9
Joined: Fri Apr 06, 2018 10:35 am

Re: NGA support for non-redundancy-aware external influx DB

Post by mzugelj »

Thank you for your answer.
Do you know if the remote database works correctly if only the backend for the remote database is used/activated?
I can connect to the remote database remotely using influx CLI and telegraf and observe database structure (since no WinCC OA data is pushed into the database). I also manually created winccoa database.
Do you consider this as a valid indicator for "working correctly"?
You have written that you have installed 3.17 P004.
Please do an upgrade to the newest patch for 3.17 as with P010 a lot of changes/improvements have been made in the NGA manager.
Long story short: Should I expect WinCC OA P01X to automatically create the winccoa influx database and the series corresponding to archive groups or is db schema something that one has to do manually for remote database?

Matevž Žugelj

User avatar
leoknipp
Posts: 2926
Joined: Tue Aug 24, 2010 7:28 pm

Re: NGA support for non-redundancy-aware external influx DB

Post by leoknipp »

InfluxDB Is a "schemaless DB", there is no fixed schema as in relational DBs.
So also the structure of the "table" itself can handle adding of new "columns" at runtime without special DB manipulations and new archive groups are created "on demand" (i.e. also no "schema upgrade" is required).


It is highly recommended to install the newest patch for WinCC OA 3.17 as it includes a lot of improvements for the NGA manager.
The upcoming patch P012 for WinCC OA 3.17 will also include an update of the NGA manager.

Best Regards
Leopold Knipp
Senior Support Specialist

Post Reply
5 posts • Page 1 of 1