Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA Enterprise SCADA

All connection type configuration settings

  • Last UpdatedApr 07, 2026
  • 2 minute read

The following Configuration settings apply to all connection types:

Configuration Setting

Description

MAX_DESTINATIONS

Sets the maximum number of destination systems that the source system can datapump to. The default is 15. Datapump must be reconfigured if this value needs to change after configuration.

Note: If the maximum number of destination systems is greater than 15, refer to MAX_DESTINATIONS parameter greater than default value for more information.

RESTART_PROCESS

When set to True, any critical failure of the DPdirect process will cause the process monitor to restart it. The default is False.

INCLUDE_GMT_OFFSET_IN_DEBLOB

Deblobbed timeline collect data contains the following columns:
time, [DP:offset], tagId, value, millisec, status. Where offset is only written when INCLUDE_GMT_OFFSET_IN_DEBLOB is True. Typically, this setting is set to TRUE when copying into an Oracle database (as Oracle uses a datetime type for a time column rather than an integer type for a Greenwich Mean Time (GMT) seconds column). The default is True.

MAX_ROWS_PER_BLOB

The maximum rows in a RealTime collect Binary Large OBject (BLOB) are 201. However, the Historical BLOB can grow larger than this when edited. Therefore, the default number of rows written by Datapump is set to 256 to give room for modifications.

MAX_COLUMNS

The maximum number of columns per table that can be configured with Datapump. The default value is 120.

ARCHIVE_LINKED_SERVER

The connection to the Archive server that is needed when Archive is not directly accessible by other services.

BULK_INSERT_TIMEOUT

The number of seconds for the bulk copy between servers to complete before it times out. The default value is 60.

BULK_INSERT_DUPLICATE_ERRMSG_LOGGING

When set to True (default), the system will log any duplicate error encountered during the DPdirect bulk insert operation.

ENABLED

Certain feature installations might cause the system to deploy a Datapump.json file on a RealTime server belonging to a system where Historical is not configured with Datapump.

In such cases, disable the Datapump feature by changing the ENABLED key from True to False. The default is True.