1 General[edit | edit source]
On lines with PVSS and WinCC OA 3.14, the assignment of the correct archive for PARAMETER VALUES (VA01) and STATUS VALUES (VA02) was important, in order to control the number of file switches triggered for the parameter archive. A wrong assignment was indicated to the user via the "Frequency High" alarm. With WinCC OA 3.18 the previous database system RAIMA was replaced by InfluxDB. Unfortunately there is no onboard diagnostic feature for tracing wrong assignments available. Therefore an in-house solution was implemented.
2 Installation[edit | edit source]
This script is installed via Patch 13 for WinCC OA 3.18 on Oracle Linux 8.4. (013_BMS_OL84ILM_V1.00.bpf)
3 Usage[edit | edit source]
3.1 Call[edit | edit source]
The InfluxDB diagnostics script can be called from anywhere with the command idbdiag. If no additional arguments are given, the following parameters apply:
- user "read_only" is used
- parameter archive (va01) is selected
- an interval of last 24 hours is analyzed
- the number of elements retrieved from the database is limited to 10 000 values (to decrease load on the system)
- only the top 5 datapoint changes are shown
pvss@Gdp:~ > idbdiag ---------------------------------------------------------------------- [ARCHIVE: VA01 | INTERVAL: 24h | LIMIT: 10,000 | TOP: 5] ---------------------------------------------------------------------- DATAPOINT FREQUENCY Gdp2107:StrMdo.DrvPrh004.ModStt 1 Gdp2107:ExtMexCtl.PmtTmpVcuSepPip.Clg.Ts_Stt 8 Gdp2107:ExtMexCtl.PmtTmpVcuMta.Clg.Ts_Stt 9 Gdp2107:Win.TenRol.FlmTenDrs.FacDivStt 164 Gdp2107:Win.TenRol.FlmTenOps.FacDivStt 164 ---------------------------------------------------------------------- 468 row(s) were retrieved. 127 distinct datapoint(s) found.
3.2 Arguments[edit | edit source]
User
-u USER_NAME --user USER_NAME --user=USER_NAME
Sets the user for authentication against the database.
Examples:
Choose user "etm":
pvss@Gcy:~ > idbdiag -u etm
Archive
-a ARCHIVE_NAME --archive ARCHIVE_NAME --archive=ARCHIVE_NAME
Sets the archive to be evaluated. Two options are available:
- "va01" for PARAMETER archive
- "va02" for STATUS archive
Examples:
Choose parameter archive.
pvss@Gcy:~ > idbdiag -a va01
Choose status archive.
pvss@Gcy:~ > idbdiag -a va02
Interval
-i INTERVAL_TIME --interval INTERVAL_TIME --interval=INTERVAL_TIME
Sets the interval to be analyzed. Options:
- "<?>s" for <?> number of seconds
- "?m" for <?> number of minutes
- "?h" for <?> number of hours
- "?d" for <?> number of days
- "?w" for <?> number of weeks
Examples:
Choose last 6 hours.
pvss@Gcy:~ > idbdiag -i 6h
Choose last 4 days.
pvss@Gcy:~ > idbdiag -i 4d
Limit
-l LIMIT_NUMBER --limit LIMIT_NUMBER --limit=LIMIT_NUMBER
Sets the query limit for database operations. Options:
- any numeric value
Examples:
Set limit to 200 elements.
pvss@Gcy:~ > idbdiag -l 200
Top
-t TOP_ENTRIES --top TOP_ENTRIES --top=TOP_ENTRIES
Sets the maximum number of datapoints to be shown as result. Options:
- any numeric value
Examples:
Display the 15 datapoints with highest change frequency.
pvss@Gcy:~ > idbdiag -t 15
Help
-h --help
Display help information.
Examples:
pvss@Gcy:~ > idbdiag -h
Version
-v --version
Display version information.
Examples:
pvss@Gcy:~ > idbdiag -v
3.3 Output[edit | edit source]
Header line: shows the active parameters for the script call.
---------------------------------------------------------------------- [ARCHIVE: VA01 | INTERVAL: 2h | LIMIT: 10,000 | TOP: 5] ----------------------------------------------------------------------
Table of results: shows summarized change frequency per datapoint, ordered smallest to largest.
---------------------------------------------------------------------- DATAPOINT FREQUENCY Gdp2107:StrMdo.DrvPrh004.ModStt 1 Gdp2107:ExtMexCtl.PmtTmpVcuSepPip.Clg.Ts_Stt 8 Gdp2107:ExtMexCtl.PmtTmpVcuMta.Clg.Ts_Stt 9 Gdp2107:Win.TenRol.FlmTenDrs.FacDivStt 164 Gdp2107:Win.TenRol.FlmTenOps.FacDivStt 164 ----------------------------------------------------------------------
Footer line: shows how many records (changes per datapoint) were queried and how many different datapoints were found.
---------------------------------------------------------------------- 468 row(s) were retrieved. 127 distinct datapoint(s) found.
