MAINTENANCE

Maintenance Mode

Maintenance mode is an offline mode that makes Data Virtuality server not to build the dependency graph, not check for possible failures of objects and data sources and not to start scheduled jobs. Jobs that are already triggered on time of activation of maintenance mode, will be processed nevertheless.

In maintenance mode only the following queries work:

create/alter/drop
selects to system tables (from SYS/SYSADMIN/SYSLOG/SYSADMIN_VDB schemas)
calls to system procedures (from SYS/SYSADMIN/SYSLOG/SYSADMIN_VDB schemas)

All other calls cause an exception.

Switching off maintenance mode behaves like a restart of Data Virtuality Server, the dependency graph will be built then, objects and data sources will be checked for failures.

Activate Maintenance Mode on a Running Server

This may be done by setting the default option MAINTENANCE to true. Setting it back to false will reactivate normal mode.

enable Maintenance Mode

call "SYSADMIN.setDefaultOptionValue"(
    "opt" => 'MAINTENANCE',
    "val" => 'true'
);;

SQL

disable Maintenance Mode

call "SYSADMIN.setDefaultOptionValue"(
    "opt" => 'MAINTENANCE',
    "val" => 'false'
);;

SQL

Configure Data Virtuality Server to Start in Maintenance Mode

The Maintenance mode might be also activated by setting the boolean system property dv.maintenance. If set to true, the server will start in maintenance mode. The default is false.

Example for setting system property dv.maintenance via standalone.conf.props.bat (Windows)

set "JAVA_OPTS=%JAVA_OPTS% -Ddv.maintenance=true"

CODE

Example for setting system property dv.maintenance via standalone.conf.props (Linux)

JAVA_OPTS="$JAVA_OPTS -Ddv.maintenance=true"

CODE

When set via the configuration file, the property overrides the one set via "SYSADMIN.setDefaultOptionValue" procedure.