[[-host hostName] -filepath path]
[[-host hostName] -filepath path]
System name of the new database. The system name must be unique among the system names of all databases in the federated database.
Integer identifier of the new database (for example, 78). This option also accepts the identifier specified in D-C-P-S format (for example, 78-0-0-0). If you omit this option, the identifier is assigned by Objectivity/DB. You may not specify the identifier 1 or the identifier 65535, which are reserved by Objectivity/DB. The maximum database identifier is 65534.
If -filepath specifies a Windows UNC share name, hostName is set to the literal string oo_local_host; any value you specify is ignored.
Path to the new database file on the designated host. If the -host option specifies a remote system, path must be full, not relative.
The path may optionally include the filename for the database; if you omit the filename, it is generated automatically.
If you omit both the -filepath and -host options, the default path consists of a generated filename in the directory of the system-database file.
(HA) Weight of the new database (useful only if you plan to create additional database images). weight must be a positive integer. The default is 1. If the value is 0, oonewdb reports an error.
Storage-page size, in bytes. Allowable page sizes are integer multiples of 8 between 1024 and 65536 (inclusive). If you omit this option, the federated database’s default storage-page size is used.
The storage-page size is used for any external container created in the database without an explicit storage-page size.
Warning: You must specify the federated database’s default storage-page size if you are creating a pre-Release 9.0 database that will be accessed by unrebuilt pre-Release 9.0 applications.
For information about choosing a storage-page size, see the chapter on performance in the documentation for your Objectivity/DB programming interface.
Nonconcurrent mode. Use this option only if the lock server for the specified federated database or autonomous partition is stopped. If the lock server is running, the tool reports an error and terminates.
Suppresses the copyright notice and program title banner. Useful when invoking the tool from another tool or product.
Path to the boot file of the federated database to which the new database is to be attached. You can omit this argument if you set the OO_FD_BOOT environment variable to the correct path. (HA) If the -ap option is included, you can specify the boot file of any autonomous partition. Otherwise, if the -ap option is omitted, bootFilePath specifies the autonomous partition that is to control the new database.
If both the -host nor the -filepath option are omitted, the database is created with a generated name in the same directory as the federated database’s system-database file. You can use oochangedb to move the new database to a different location.
(HA) You use oonewdb to create the first or only image of a database in a federated database. To replicate the database (that is, to create additional database images), you must use oonewdbimage; see Objectivity/DB High Availability.
The oonewdb tool can be used to create new databases in pre-Release 9.0 federated databases. In this case, the new database is created with the pre-Release 9.0 internal format. The internal database format refers to the implementation of catalogs, and may affect the behavior of an application; see the appendix about accessing earlier databases in the documentation for your Objectivity/DB programming interface.
Tuesday, October 30, 2012