Reassigning Patch Numbers from a Command Script

You can reassign open patch numbers from a command script (for example, after loading schema patches in a deployed database, to reassign all open patch numbers to the latest JADE release), by specifying the following.

jadloadb path=database-path
         ini=initialization-file-name
         server=singleUser
         executeSchema=RootSchema
         executeClass=Schema
         executeMethod=_reassignPatchNumbers

Alternatively, if you want to reassign all patch numbers (that is, both open and closed path numbers), by specify the following.

jadloadb path=database-path
         ini=initialization-file-name
         server=singleUser
         executeSchema=RootSchema
         executeClass=Schema
         executeMethod=_reassignAllPatchNumbers

If a patch number that is being reassigned already exists in the target JADE release with a version number for that release (for example, release 6.3.11), the reassigned patch number will have two entries (for example, one for release 6.2.12 and one for 6.3.11).

This is likely to occur only if a schema load or changes to entities are made in the JADE development environment with the same numbers as those that existed in earlier release before the _reassignPatchNumbers or _reassignAllPatchNumbers method is executed.

For details about the batch JADE Schema Load (jadloadb) executable, the JadeSchemaLoader application in jadclient, jade, or the Application class startApplicationWithParameter method, see "Loading Schemas in Batch Mode using jadloadb" in the JADE Schema Load User's Guide.