Reblocking Collection Class Maps
You can use the reblocking collection class maps facility after upgrading an environment from an earlier release that had a different file structure (for example, when upgrading JADE release 6.3 or 7.0 to 7.1), to reblock collections for the best fit to the new file structure.
You can reblock all collections in one or more map files, by using the JadeCollectionReblocker application in the jadclient executable in single user or multiuser mode; that is:
jadclient.exe path=database-path ini=jade-initialization-file server=SingleUser|MultiUser schema=user-schema-name app=JadeCollectionReblocker file=file-name|mask [file2=file-name [file3=file-name]...] [workers=number-of-worker-threads]
The file-name value is a complete map file name or a partial map file name with a trailing asterisk; for example, cust* means all map files that begin with the letters cust. Specify the file-name mask * (a single asterisk) to indicate reblocking of all user files, including rootdef. Specify the mask _* (underscore asterisk) to indicate the reblocking of all system files such as _userscm.
The following are examples of the reblocking action.
jadclient path=d:\jadeuser ini=d:\salesdb\jade.ini schema=Sales server=singleUser app=JadeCollectionReblocker file=*
jadclient path=d:\jadeuser ini=d:\salesdb\jade.ini schema=Sales server=singleUser app=JadeCollectionReblocker file1=testdb file2=banking file3=_userdev workers=5
The optional workers argument enables you to specify the number of multiple concurrent worker threads that are used. The default value of 1 is used if you do not specify the workers argument. You can specify a value in the range 1 through 16. If you specify a value greater than 16, the maximum number of 16 worker threads is used.
Reblocking is done in normal update transactions, which are committed every 1,000 collections or 30 seconds.
Reblocking skips collections that do not require reblocking. The JadeCollectionReblocker application can be terminated part way through a file, in which case only uncommitted changes are discarded. When reblocking is restarted for the same file, collections that have already been reblocked are skipped.