Database Save Errors

[Anonymous user]

📖 Home  Back  
This is a rough outline of the steps followed by ClearSCADA as it saves the configuration and data streams to disk:

• The database is placed under a write lock

• A copy of the stream is made in memory

• The database write lock is release

• The database copy is written to 'temporary' file on the disk (TempDBConfigXXXX or TempDBDataXXXX depending on stream, XXXX is an increasing number each time)

• The stream's 'current' .dat file is deleted

• The new 'temporary' file is renamed and become the new 'current' .dat file

Prior to ClearSCADA 2009 R2 there was only 1 configuration and 1 data stream. In ClearSCADA 2009 R2 and later there may be multiple streams depending on the size of the database. See the article on Streams for details

If DBServer is unable to successfully save the database to disk it will result in a Database Save Error
Some common reason for the Database Save Error are:

• The disk is full

• The disk is inaccessible

• A third party programs has temporarily locked the existing .dat files, for example:

• AV products see Anti-virus Scan Exclusions)

• Indexing products (MS Index Service, Google Desktop)

• Defrag tools (Diskkeeper) (See Online Defragmenter Exclusions)

Go: Home Back