Create database with WCCOAtoolCreateDb without default datapoints

[setschel]

Hello,

we are using WinCC OA V3.19 P003 on a Oracle Linux Server 9.2 system.

We want to create our initial database with WCCOAtoolCreateDb and datapoint lists during the creation of the database. Everything works so far, but we have the problem, with every creation of the database we are getting the default datapoint types with the corresponding datapoints (datapoint types ANALOG1, ANALOG2, BIT_CONDITION, COUNTER_SUB, COUNTER1, DRIVE1, DRIVE2, EXAMPLEDP_BarTrend, ExampleDP_Bit, ExampleDP_DDE, ExampleDP_Float, ExampleDP_Int, ExampleDP_Text, LABOR_ANALOG, LABOR_COUNTER, MODE_CMD, MODE_STATE, PUMP1, PUMP2, SETPOINT, SLIDE_VALVE_HAND1, SLIDE_VALVE1, SLIDE_VALVE2, SSC_KPI_Instance, WH_SC_SUB, WH_SC1).

These datapoint types/datapoints are of course not in our datapoint lists, which we are importing during WCCOAtoolCreateDb.
In the WinCC OA help I could not find any hint (https://www.winccoa.com/documentation/W ... olCreateDb). Using option -empty does not work (do not load internal datapoints).

This is our command to create the database and import the datapoint lists, which are listed in the file lists.txt:

Code: Select all

/opt/WinCC_OA/3.19/bin/WCCOAtoolCreateDb -proj Projectname -importAscii /data/Projectname/restore/lists.txt -yes

Is there any possibility, that the default datapoint types/datapoints are not created when creating the database with WCCOAtoolCreateDb?

Thank you in advance for your support.

[dbindernagel]

I do not know if this is possible, but I was told once that you should not delete the default datapoints.
Not sure how big of a problem it actually would be but it seems it might cause trouble during upgrades/updates.

From the help:

Standard Datapoint Types
Some errors may occur during a project update if the standard data point types were modified (e.g. data point type ANALOG1 was deleted). Therefore, it's recommended to do an ASCII export before the update and import the data after the update.

https://www.winccoa.com/documentation/W ... id-title32

[leoknipp]

There is no option available to create a new database without the standard datapoints.
A new database always consists of the internal datapoints, some master datapoints for specific DP types and some example datapoints.

Please be aware that deleting the datapoint types and its related datapoints is not sufficient to get rid of the datapoints as in some internal datapoint elements references are saved to the standard DP types and datapoints.

Why do you want to have a database without these datapoints?

Best Regards
Leopold Knipp
Senior Support Specialist

[setschel]

Thank you for your fast answers @dbindernagel and leoknipp!

We just wanted to have no "useless" datapoints for our project shown in PARA (more clear display in PARA), but if the default datapoint types + datapoints are needed, we leave them in the database.

Best regards

[gschijndel]

I agree that a new database contains many useless datapoints of rarely used or perhaps even obsolete features (like pager).

Even if you can specify which feature you use obsolete datapoints are there. For example if you create a new NGA project it will still contain the value archive and RDB datapoints.

[leoknipp]

Info: With the next major version unused datapoint types and datapoints have been deleted from the standard database.
In a standard database you will still have the datapoints for several functionalities (e.g. all possible archiving technologies) as splitting up the ASCII files into all possible sub parts (databases, drivers, Add-Ons, ...) is too much effort.

Best Regards
Leopold Knipp
Senior Support Specialist

[kilianvp]

Just delete all DPTs with a Script. But you must keep all interal DPTs and "SSC_KPI_Instance"

[leoknipp]

As mentioned in my posting viewtopic.php?p=969900#p969900 just a deletion of the datapoints and DP types is not the correct way.
If the referenced information on other internal datapoint elements is not deleted some standard functionality will possibly not work or a least give some errors.

Best Regards
Leopold Knipp
Senior Support Specialist

[gschijndel]

Apparently it is possible and a lot of customers do it without issues. I believe the effort is nothing in comparison to the combined effort the customers put in to do it themselves with a lot less knowledge.

I think this would score high if customers could vote on which feature they would use in the future.

[kilianvp]

If we are not allowed to delete them, then why not build in an option to hide them in the para and datapoint selector?
I have never met a customer who needs them and they don't bother him.