The FreezeSchemaFiles action changes the volatility of the _userint, _userscm, and _userxrf schema files to frozen.
Setting the file volatility to frozen overrides any specified object volatility for objects stored in that file. Freezing schema files provides performance improvements, by reducing the number of locks and unlocks and fetched user schema objects. This benefit is a result of ignoring implicit lock requests on those objects stored in the frozen schemas.
For details about object volatility, refer to "
Attempts to create or maintain any development objects (for example, schemas, classes, methods, forms, and so on) are disallowed while the schema files are in a frozen state. An attempt to modify any such object raises exception 1106 (Cannot update a frozen object). This also applies to maintenance activities outside the JADE development environment, including jdbadmin batch JADE Database Administration utility actions.
The syntax of the freezeSchemaFiles action is as follows.
jdbadmin action=FreezeSchemaFiles
[path=database-path]
[ini=initialization-file-name]
[server=multiUser|singleUser]
The path arguments is optional in multiuser mode.