MakePartitioned

The MakePartitioned action converts the specified non-partitioned database file into a partitioned format.

The syntax of the MakePartitioned action is as follows.

jdbadmin action=MakePartitioned
         [path=database-path]
         [ini=initialization-file-name]
         [server=multiUser|singleUser]
         file=file-name
         [method=method-name]
         [modulus=integer-value]
         [updatesAllowed=true|false]

In addition to the command line argument values that apply to one or more batch database administration utility actions or commands, documented under "Command Arguments", the MakePartitioned action arguments are listed in the following table.

Argument Description
path Optional, in multiuser mode.
file Specifies the target file.
method Identifies the partition method that is to be called as each object is processed. A partition method returns a partition index value that determines the partition in which the receiver is located. Sub‑objects (for example, collections, blob or slob properties, and JADE bytes) are automatically located in the same partition as the parent object. If the method argument is not specified, the autoPartitionIndex method is called. The default Object‑level implementation of this method returns the value zero (0), which causes objects to be located in the latest partition.
modulus

Specifies the creation window size for the operation. This also establishes the number of partitions that will be created. If specified, the modulus value must be an integer in the range 1 through 1024. The default value of 1 results in a single partition getting instantiated.

The effects of a successful MakePartitioned operation are redone by roll‑forward recovery and replayed on an SDS secondary database. To accomplish that, a copy of the partition index is inserted in the database journal when the converted file is instantiated.

updatesAllowed

If you want to partition a file while allowing applications to continue updating the file being partitioned, set the value of the optional updatesAllowed argument to true. If the argument is not specified, the value defaults to false; that is, updates of a partitioned file are not permitted.

If you execute the MakePartitioned command with updatesAllowed=true, when the file conversion process has completed, updates audited in transaction journals are applied to the output file. This recovery phase is referred to as file synchronization.

During the initial file recovery or synchronization phase, further updates to the file are permitted. However, when the file is ultimately instantiated, a database quiet point is acquired. This quiet point will momentarily block active transactions from committing while remaining updates are applied and the partitioned file is instantiated.

The following is an example of the MakePartitioned command.

jdbadmin path=c:\JADE_JRF301 ini=c:\JADE_JRF301\jade.ini action=MakePartitioned file=sales modulus=36 updatesAllowed=true