Before You Get Started

Before installing patches and performing a reorganization in a runtime-only environment, you must take a backup copy of the database as the reorganization can fail under some circumstances (for example, if there is insufficient disk space or a change in the new schema definition is not compatible with runtime data). If this occurs, your JADE application may be left in an unusable state. You should then restore the database from backup, correct the problem that caused the reorganization to fail, and then repeat the load and reorganization.

For details about correcting data after a reorganization, see "Correcting Data if a Reorganization Fails", in Chapter 14 of the JADE Developer's Reference.

If you have mapping method logic on subclassed controls that rely on this logic when executing, you must protect that logic from situations where properties of subclassed controls are accessed or referenced by JADE processes such as the JADE Painter, JADE Translator utility, or the loading of schemas.

If external databases, ActiveX (COM) libraries, relational views, or RPS mappings have been extracted separately by using the appropriate Extract command, the order in which you should load extracted files is as follows.

  1. Relational view extract file or files.

  2. Selective schema extract file.

  3. External database, RPS mapping, or ActiveX (COM) library extract file or files.

If a reorganization is required after the .scm file load and before the .ddb file load, you can load the .ddbx file (RPS mapping information) before the reorganization, to keep the RPS mappings up-to-date with the schema changes. After the reorganization, the .ddb file is loaded as normal, to complete the changes. When extracting a schema with an RPS mapping and the DDX format style is selected, a separate .ddbx file is produced as for a DDB extract but the file contents are in XML format.

For details about loading an encrypted schema file, see "Encrypting Schema Source Files", in Chapter 10 of the JADE Development Environment User’s Guide.

If you are loading multiple schemas and you want to suppress the display of all warning messages resulting from compiling schema files (for example, class number conflict messages), set the SuppressWarningDialogs parameter in the [JadeCompiler] section of the JADE initialization file to true. Warning messages are then output only to the message log.

The default installation sets up the JADE Utilities\JADE Loader shortcut for the JADE Schema Load utility.

The Jade Loader icon is installed in your JADE program folder when you install JADE. The default installation sets up the JADE Utilities\JADE Loader shortcut for the JADE Schema Load utility. For details about installing the Schema Load utility, see "Installing Your JADE Software", in Chapter 1 of the JADE Installation and Configuration Guide.

The following table lists examples of the properties required to run the JADE Schema Load utility in single user mode.

Property Example
Command line jadload.exe path=c:\jade\system
Working directory c:\jade\bin

If you want all methods loaded from the schema file to be compiled during the load process, including those whose source is the same as their source in the database:

By default, the load process skips methods whose source is the same as their source in the database.

Exception 6429 is raised when you attempt to load a schema with the default map file marked as partitionable (that is, the DbFile class partitionable property is set to true).