Data location status

Data location status

A data location status is:

  • Ready: A data location in this status can be accessed in read/write mode, accepts incoming batches and processes its current batches.

  • Maintenance: A data location in this status cannot be accessed. It does not accept incoming batches but completes its current batches. New loads cannot be initialized and existing loads cannot be submitted. Continuous loads stop processing incoming loads and keep them on hold.

When moving a data location to a Maintenance status, the currently processed batches continue until completion. Loads submitted after the data location is moved to Maintenance will fail. They can be kept open and submitted later, when the data location is restored to a ready status.

When a data location is in maintenance mode, it appears with a disabled avatar in the welcome page.

Change a data location status

To set a data location status to maintenance:

  1. In the Management view, expand the Data Locations node, right-click the data location and select Set Status to Maintenance.

  2. Click OK in the confirm dialog.

The data location is moved to Maintenance mode.

To set a data location status to ready:

  1. In the Management view, expand the Data Locations node, right-click the data location and select Set Status to Ready.

The data location is moved to a ready state.

Use the maintenance mode

The Maintenance status can be used to perform maintenance tasks on the data locations.
For example, if you want to move the data location to a model edition with data structure changes that mandate manual DML commands to be issued on the hub tables, you may perform the following sequence:

  1. Move the data location to Maintenance mode.

  2. Let the currently running batches complete. No batch can be submitted to this edition.

  3. Deploy the new model edition.

  4. Perform your DML commands.

  5. Move the data location from Maintenance to the Ready status. Batches can now be submitted to this data location.

Using this sequence, you prevent batches being submitted while the hub is in Maintenance.

The data location is automatically set to maintenance when deploying a model edition and then automatically reverted to ready state.