(For backward compatibility only)
Creates persistent objects in a federated database, using information from a text file created by oodump.
[-abort | -db]
Terminates without applying changes. You can use this option (with or without the -verbose option) to test the load operation without committing the transaction. If you use this option you cannot use the -db option.
Deletes any databases whose system name matches a database in the input text file. If you use this option you cannot use the -abort option. This option supersedes the -cont option when both are specified.
Deletes containers from the database whose object identifier or system name matches a container in the text file.
Pipes the input file through the specified data-decompression tool. If tool is not specified, the standard UNIX or Macintosh uncompress tool is used.
Allows external references within the text file, generating a warning for each external reference it encounters.
Warning: Use of this option can introduce semantic inconsistencies into the federated database.
Ignores container size information in the input file and resizes containers as necessary. Use of this option can result in a more compact federated database.
Overrides the hash-factor information in the input file with the value hashFactor for all containers. hashFactor can be any nonnegative integer.
hashFactor applies only to containers in databases that use the pre-Release 9.0 internal database format.
Overrides the growth-factor information in the input file with the value growthPercent for all containers. growthPercent can be any nonnegative integer.
Input text file (previously created by oodump).
Prints full status information during processing and a summary message after processing terminates. This tool sends all status messages to stdout and all error messages to stderr.
Nonconcurrent mode. Use this option if no lock server is running or to bypass a running lock server.
Warning: Corruption can occur if concurrent access to the federated database is attempted while any process is using this mode.
Suppresses the copyright notice and program title banner. Useful when invoking the tool from another tool or product.
Suppresses all normal program output.
Prints the tool syntax and definition to the screen.
Path to the boot file of the federated database where the objects will be loaded; by default the federated database specified in the text input file. (HA) You can specify the boot file of any autonomous partition.
Although the oodump and ooload tools are still supported, you should use ooexportfd and ooimport instead.
By default, ooload terminates upon encountering an external reference. External references are either relationships (associations) with, or object identifiers for, objects not in the specified text input file. Specify the -external option to allow ooload to skip external references without terminating.
The federated database referenced by bootFilePath must have a schema identical to (or a superset of) that of the federated database from which the text input file was dumped.
The ooload tool does not:
- Preserve object identifiers (OIDs), although the containment hierarchy is preserved.
- Load indexing information.
- Call constructors when it creates objects.
- Call destructors when it deletes objects. If ooload deletes a database or container whose object identifier or system name matches the object identifier or system name specified by the ‑db or ‑cont option, it does not call the object’s destructor.
- Preserve container files. If a database had any external containers when it was dumped, ooload re-creates them as embedded containers within the file of the loaded database.