Use the DB Alias tab to define the parameters needed for the Informix® loader.
The availability of certain options and fields might be dependent
upon your entries for related options and fields on the tab.
Mode
- Insert
- Insert rows from the source file into empty destination
tables. If destination tables contain data, the loader returns an
error.
- Replace
- Clear all data
in the destination tables and replace
with rows from the source file.
Violation Table Options
- Start Violation Table
- Issue a Start Violation Table SQL statement. Check
for previously linked violation tables and diagnostic tables by clicking . The Exception Table Mapping dialog
displays.
If linked tables are present, the exception
table map is populated with the table names. By default, a violation
table name is the table name with the suffix ‘_E'. (A diagnostic
table name has the suffix ‘_D'.) You can change the names of
the tables by typing over them.
- Delete all rows
- Select this check box to delete all rows in violation
and diagnostic tables before the load begins.
- Load When Source is Empty
- Complete the load if a table to be loaded contains no rows, deleting
any rows from the target. If not selected, empty source tables are
skipped.
Options
- Perform Load
- Run the loader automatically after file conversion.
Options to disable triggers and constraints apply. Clear to convert
the data and create a BAT file.
- Delete files if Successful
- Delete load files after the loader completes
successfully. Fast load confirmation is not
available.
- Delete files if Failure
- Select this check box to delete the data files if
the loader does not complete successfully. Fast load confirmation is not
available.
Commit
The maximum
number of rows (up to 999999999) processed before changes are committed.
To ensure that all data or no data for a table is loaded, specify
zero (0) or leave blank.
Warning Limit
The number of rows (up to 999999999) that the loader can discard
because of errors. Stop processing when the specified number of rows
is discarded.
- To end the process if a single row is discarded,
specify 1 as the maximum.
- To allow an unlimited number of rows to be discarded,
specify zero (0) or leave blank.
Additional Loader Parameters
You can augment
the loader arguments created automatically with additional
loader parameters. The parameters you create are appended to the list
created automatically, but are not validated before starting the loader.
For valid operands, see the database loader documentation. If additional
loader parameters are forced from within product options, you cannot
modify them.
Disable Triggers
- Never
- Never disable
database triggers for the loader.
- Always
- Disable database triggers
during the load process
and re-enable triggers when the process is completed.
- Prompt
- Display the Disabling Trigger/Constraint
Confirmation dialog to list tables with associated triggers.
Right-click the Status After Process column
to enable or disable the corresponding trigger or constraint after
the load completes.
Disable Constraints
- Never
- Never
disable referential integrity constraints for the loader. This option
causes a warning message when you run the loader.
- Always
- Disable constraints during the load process and
re-enable constraints when the process is completed.
- Prompt
- Display the Disabling Trigger/Constraint
Confirmation dialog to list tables with associated constraints.
Right-click the Status During Process column
to enable or disable the corresponding trigger or constraint during
the load. Right-click the Status After Process column to enable or disable the corresponding trigger or constraint
after the load completes.
Note: For Informix, you can also elect to enable constraints with or without using
a violation table. Select With Vio to enable
the constraint and use a violation table. Select No Vio to enable the constraint and not use a violation table. (If you
select Enabled, the Informix default for violation tables applies.)
Workstation Path
Default directory path for storing the temporary loader files.