DeactivateDeltaDb

The DeativateDeltaDb action deactivates delta mode and removes the associated delta database.

The syntax of the DeactivateDeltaDb action is as follows.

jdbadmin action=DeactivateDeltaDb
         [path=database-path]
         [ini=initialization-file-name]
         [server=multiUser]
         [timeout=maximum-number-of-seconds]

The optional timeout argument is used to specify a maximum number of seconds to allow for deactivation to take place and is ignored when the ActivateDeltaDb action is set to true.

The delta database cannot be deactivated until all current processes are idle apart from JADE tools (for example, the JADE Monitor and the SDS Administration application) and the process making the request is idle with no persistent locks and not in transaction state.

The deactivation attempt is abandoned if this does not happen within the specified time, and the delta database remains activated. If a timeout or a value of zero (0) is not specified, a default timeout of 60 seconds is used.

When an SDS secondary database is taken out of delta mode, database tracking is resumed if it is not disabled. On an RPS secondary, the Datapump application is also restarted if it is not running and auto restart data pump is enabled.

If any of the following conditions are not satisfied, deactivation is abandoned and system error 1163 is returned.

• The request cannot be completed because not all applications have become idle within the specified timeout

• The process that requests the deactivation must not have any persistent objects locked

• The process that requests the deactivation must not be in transaction state

• The process that requests the deactivation must not be executing any methods that have a persistent user object as the receiver.

Before the delta database can be deactivated, all current applications (apart from the application making the request) must be idle, not in transaction state, and have no persistent locks held. To be idle, an application must not be currently executing any methods invoked via the JADE object manager; that is, its object manager call stack should be empty. The deactivation attempt is immediately abandoned if there are any idle processes that have persistent objects locked or that are in transaction state.

When a deactivation request is received, each application is allowed to proceed normally until its JADE call stack is empty. When a process is idle, any further attempt to invoke a method is held up until deactivation is completed or abandoned. (The process making the request and JADE tools such as the JADE Monitor and the SDS Administration application are exempt from this.)

Any attempts to start up new applications are also stalled until deactivation is completed or abandoned.

The following is an example of the DeactivateDeltaDb command.

jdbadmin path=d:\salesdb ini=d:\salesdb\jade.ini action=DeactivateDeltaDb timeout=300

Exception 1162 (The system is not Delta Database capable) is raised if you attempt to deactivate a delta database in single user mode.