WCCILdata - SYS/SEVERE - Database error, DataManTask, dbError, RAIMA Database Error *** Code:-909 file record limit exceeded

Enclosed you'll find the explanation for a log-message which occurs during runtime. The messages are written to the PVSS_II.log-file.

WCCILdata (0), 2018.02.21 13:04:01.596, SYS, SEVERE, 69, Database error, DataManTask, dbError, RAIMA Database Error *** Code:-909 (SYSTEM/OS error: -909
file record limit exceeded
C errno = 0: No error
FILE: dio.c(2096))

Log-message with symbolic names:

WCCILdata (0), <TIMESTAMP>, SYS, SEVERE, 69, Database error, DataManTask, dbError, RAIMA Database Error *** Code:-909 (SYSTEM/OS error: -909
file record limit exceeded
C errno = 0: No error
FILE: dio.c(2096))

This log-message describes that the file limit for some database files is exceeded. It is written in combination with other log-entries for the data-manager.
When this message occurs some information in the database cannot be stored. Most of the time the limit for the configuration database is reached, which means that changes at the configs cannot be saved.

If this message is observed you should check in the first step the size of the database-files for the RAIMA-database. The parts of the RAIMA-database are all sub-directories and files at the <project-path>/db/pvss-directory excluding the directories with the name-pattern VA_*.
If the filesize for some files is about 200MB or higher you have to check if the file-record limit is exceeded.

This can be done with the following steps:
-- stop the project
-- open a command-shell
-- change into the directory which contains the huge files

Depending on the directory where the huge files are found different commands have to be started, enclosed you’ll find a list of the directory-names followed by the necessary command. The <installation-path> is the directory where you’ve installed PVSS/WinCC OA. In case of an older version (before WinCC OA 3.11) you have to choose db/pvss instead of db/wincc_oa):
<project-path>/db/wincc_oa – <installation-path>/bin/dbcheck ConfHist > confhist.log
<project-path>/db/wincc_oa – <installation-path>/bin/dbcheck TypeAndId > typeandid.log
<project-path>/db/wincc_oa/al<10-digit-number> – <installation-path>/bin/dbcheck AlertHist > alerthist.log
<project-path>/db/wincc_oa/alliving – <installation-path>/bin/dbcheck AlertHist > alliving.log
<project-path>/db/wincc_oa/lastval – <installation-path>/bin/dbcheck ValHist > valhist.log

-- open the created log-file with a text-editor (Notepad, VI, …)
-- check if entries can be found where the number of records is 16777216 (2°24) or nearly this value. 16777216 is the limit for record entries.

When you’ve collected this information please submit a service request using the Siemens Industry Support (https://support.industry.siemens.com) and add the following information:
-- installed WinCC OA-version
-- used operating system
-- problem description
-- log-file <project-path>/log/PVSS_II.log-file
-- log-file created by the dbcheck command
-- directory-listing for the database-directory <project-path>/db/wincc_oa
E.g. on Windows this file can be created with the command dir /s > db_dirlist.txt started from a command shell

Afterwards you’ll get detailed information which parts of the database are affected and how the problem can be solved.