Encodes the output file so that it cannot be read by end users. If you omit this option, the schema change information is written as text.
Name of the file to which the schema representation is to be written. If you omit this option, the output will be written to a default file called schema.dmp in the current directory.
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 with the evolved schema. You can omit this argument if you set the OO_FD_BOOT environment variable to the correct path. (HA) You can specify the boot file of any autonomous partition.
You normally perform schema evolution on a source federated database at your development site. When you are ready to test or deploy the evolved schema, you can use ooschemadump to write the schema changes to an output file. You (or your end users) then use ooschemaupgrade to apply the changes in this file to the destination federated database (for example, your end user’s production federated database).
(Objectivity/C++) Some complex schema-evolution operations require that you run a conversion or upgrade application between uses of the DDL processor. When this is the case, you need to use ooschemadump after each use of the DDL processor, and before you run a conversion or upgrade application or continue with any other schema-evolution operations. When you deploy the schema changes, you must distribute all such ooschemadump output files to your end user.
Tuesday, October 30, 2012