Schema Definition Commands Options

Run the script to build the schema in the database with the provided options.

Option Description
--propFile, /--propFile, or -system:propFile Optional. When you execute be-jdbcdeploy, it searches for a property file of the same name in the working directory. This property file provides startup values and other parameters to the executable. You can specify the path and filename of a startup property file explicitly using the --propFile parameter.

For example, if you start the engine from a directory other than BE_HOME/bin, then you would generally use --propFile to specify BE_HOME/bin/be-jdbcdeploy.tra.

-p, /p, -property, or /property Optional. Allows you to pass one or more supplementary property files to be-jdbcdeploy. Specify the path and filename. Values in supplementary property files override the values in the startup property file.
-o, /o, -out, or /out Required. Specifies the schema output filename for deployment.
Tip
If you specify a directory path, the backing store scripts are generated in the specified directory and the last element of the path is taken as the schema output filename.
-c, /c, -cdd, or /cdd Optional. Specifies the absolute path to the CDD file. See Ontology Identifiers that Exceed the DBMS Maximum Column Length to understand when the CDD file is needed.
-optimize Optional. Use this option to eliminate schema generation for in-memory events.
EARpath Required. The last option is always the EAR file path.
-h, /h, -help, or /help Displays this help.
-a, /a, -ansi, or /ansi Optional. If set to true, ANSI compatible SQL types are used during script generation.

Allowable values are true and false. For ANSI compatible databases, it is set to true by default.