|
-gentrigger causes ODXAIM
to generate a script file that will create the AIM table(s)
(odxtrans) and add all the triggers necessary to maintain
the Omnidex indexes installed on the environment.
-file=newtrigfile
specifies the output file that the script will be written
to. If omitted at the command line, ODXAIM will prompt the
user for this filespec.
cfgfile is the ODXAIM
configuration filespec. The environment filespec is the only
required information contained in the configuration file that
is required for generating triggers. All other settings in
the configuration file have defaults that will be used if
not specified. If cfgfile is omitted
at the command line, the environment must be specified with
the -env option.
-env=OAEnvFile is
the Environment Catalog filespec that ODXAIM will connect
to. This environment must have Omnidex indexes installed on
it in order to have triggers generated. If -env
is omitted at the command line, the configuration must be
specified at the command line or ODXAIM will prompt the user
for the environment filespec.
-newenvsrc=newenvsrcfile
causes the environment file source to be generated and output
to newenvsrcfile. It is assumed that newenvsrcfile
does not already exist. Note that this can also be done later
using the -genodxtrans directive.
-tables=<oatablelist>
causes create table scripts to be generated for all tables
in oatablelist. An odxtrans table will be created
for each table. An * (asterisk) can be used in oatablelist
to create an odxtrans table for all Omnidex indexed tables.
-colsep=c is the
column list separator character. If omitted, the default ~
(tilde) will be used. The column separator character is used
to separate the column names in the column list.
-datasep=d is the
data values separator character, column delimiter. If omitted,
the default ^ (carat) will be used. This character is used
in the AIM table transaction_data field to separate the data
values for each column.
-overwrite instructs ODXAIM
to overwrite the output file if it already exists. If omitted,
and the file exists, an error will occur.
After the script file has been generated, it must be executed
in the native database to create the AIM table and install
the triggers. Use SQL Plus in Oracle, Query Analyzer in SQL
Server, or Command Center in DB2 to execute the script. Consult
the appropriate database documentation for details on executing
scripts in these programs.
top
Example
The following example demonstrates generating the triggers
against the Orders sample database installed in Oracle. The
triggers and create table statement will be output to the
orders.sql file. Note that the environment source entry for
the odxtrans table is not generated by this command.
c:\orders>odxaim -gentrigger -file=orders.sql
-env=orders.env
Generating triggers for the Omnidex Automatic Indexing Manager
program.
Finished generating Omnidex trigger source file.
c:\orders>
This example generates the triggers and the create table
statements for all of the odxtrans tables, as well as the
environment source file entries. The triggers and create table
statements are output to newtriggers.sql and the environment
source entries are output to newsource.src.
c:\orders>odxaim -gentrigger -file=newtriggers.sql
-env=orders.env -newenvsrc=newsource.src -tables=table_list
top
|
[-env=OAEnvFile]