Database Tab

Use the options on the Database tab to set preferences for handling database connections, multi-byte round trip conversion errors, and cascade deletes. For Sybase ASE, you can specify whether to run in Unchained mode.

For Teradata users, a Teradata button is provided to specify Teradata settings on a Teradata Parallel Transporter (TPT) Settings dialog.

Parallel Processing

Maximum Database Connections: Specify the default number of concurrent database connections for an Archive, Delete, or Extract Process. Increasing database connections improves performance when processing large quantities of data by allowing multiple threads to process rows in parallel.
To increase the maximum number of connections, select an even number from 2 through the site maximum as specified in Product Options.

Note: For performance reasons, you can only select an even number of maximum database connections.

MBCS Roundtrip Processing

Options for handling characters that could cause round trip conversion issues in a multi-byte Optim™ Directory or DB Alias. The availability of these options is governed by the MBCS Roundtrip Processing settings on the Product Options Database tab.

Optim uses the Unicode character set in dialogs and to process data. In some multi-byte character sets (such as Oracle JA16SJIS), multiple characters are mapped to the same Unicode character. When these characters are converted from Unicode back to multi-byte (a round trip), the original character may not be returned.

Archive/Extract Requests

Select an option for handling round trip conversion issues during Archive or Extract processing:

Stop Processing: Stop processing when a multi-byte character is encountered that could cause an incorrect round trip conversion.
Ignore all round trip Failures: Continue processing when a multi-byte character is encountered that could cause an incorrect round trip conversion. (Default.)

Insert/Load/Convert Requests

Select an option for handling round trip conversion issues during Insert, Load, or Convert processing:

Stop Processing: Stop processing when a multi-byte character is encountered that could cause an incorrect round trip conversion.
Ignore all round trip Failures: Continue processing when a multi-byte character is encountered that could cause an incorrect round trip conversion. (Default.)

Select the Ignore all round trip Failures option if the database does not contain data with characters that could cause round trip errors, or if columns used to manipulate data in a Column Map (e.g., a function is used) and columns for which selection criteria are defined do not contain characters that could cause round trip errors.

Cascade Delete Rule

Warn On Cascade Delete/Update

Display a warning if a cascading delete or update may occur to a table that is not explicitly included in an Access Definition or a process.

Runtime: Display a cascade delete/update warning only at run time of a process.
Saving Access Definition: Display a cascade delete/update warning only when saving the Access Definition.
Always: Display a cascade delete/update warning at run time of a process and when saving the Access Definition.
Never: Do not display a cascade delete/update warning. This is the default setting.

The Warn on Cascade Delete/Update setting in Product Options (see Cascade Delete Rule) affects the availability of this option for user input. If available, you can click the down arrow to choose when to display a warning. If unavailable, the value specified for Warn on Cascade Delete/Update in Product Options is displayed and cannot be modified.

Sybase Unchained Mode

Run in Unchained Mode: Optim normally runs in chained mode. When a trigger in a Sybase ASE table will be fired as a result of an Insert or Delete Process, and the trigger calls a stored procedure that must run in unchained mode, the connection must be in unchained mode for the procedure to work.
The Sybase Unchained Mode setting in Product Options (see Sybase Unchained Mode) enables or disables this check box. If enabled, select the check box to run Insert and Delete Processes in Unchained Mode, or clear the check box to run all actions in normal mode.

Teradata

If you use a Teradata database, click the Teradata button to specify the appropriate Teradata settings on the Teradata Parallel Transporter (TPT) Settings dialog.

Allow Temp Table usage

This option determines whether temporary tables are created during an extract or archive process to improve the performance of archives and extracts of related Teradata tables. If you enable this feature, the solution will create temporary tables in Teradata during an archive or extract process. The temporary tables are used to store key values to join with related tables. Select:

Default to use the default setting specified for this parameter on the Product-Options version of the Teradata Parallel Transporter (TPT) Settings dialog. That dialog is available from the Database tab on the Product Options dialog.
Never to not allow the solution to create temporary tables during an extract or archive process.
When Possible to allow the solution to create temporary tables when possible during an extract or archive process. This setting will improve performance during an extract or archive process.

Temp Database

If appropriate, type the name of the database in which you want temporary tables created. If a database name is not specified, the tables will be created in the same database as the reference tables. (The user must have CREATE TABLE, INSERT, and DROP TABLE privileges for the database to create temporary tables.)

Allow Teradata Parallel Transporter (TPT) usage

This option determines whether Teradata Parallel Transporter (TPT) is available for extract and archive requests. TPT is a parallel multi-function load environment. TPT provides scalable access to data sources from a single interface using a single SQL-like scripting language or an open API, and provides a completely parallel environment. TPT utilizes system resources efficiently by allowing distribution of the workload across CPUs, eliminating bottlenecks in data loading process. Select:

Default to use the default setting specified for this parameter on the Teradata Parallel Transporter (TPT) Settings dialog of Product Options. That dialog is available from the Database tab on the Product Options dialog.
Never to never allow the use of TPT for extract and archive requests.
When Possible to use TPT when possible for extract and archive requests, otherwise allow attachments to "step down" to CLIv2 (Call-Level Interface v2).
Optim will step down to CLIv2 if:
- a table contains LOBs, or
- a table includes a Point-and-Shoot list, or
- the table access strategy is Key Lookup.

Note: TPT is used to scan start tables and reference tables, whether the scan is a full-table scan or a scan by subquery.

TPT Limit Settings

Maximum Sessions: Type the maximum number of sessions to log on. The default is one session per available AMP. The maximum value cannot be more than the number of AMPS available.
Minimum Sessions: Type the minimum number of sessions required for a TPT job to continue. The default is one session. This entry must be greater than or equal to 1 and less than or equal to the maximum number of TPT sessions.
Sleep: Type the number of minutes the TPT should pause before attempting to log on when the maximum number of load and export operations are already running on the Teradata database. The default is six minutes.
Tenacity: Type the number of hours the TPT should attempt to log on if the maximum number of load and export operations are already running on the Teradata database. This entry must be greater than zero to enable the Tenacity feature. Type zero to disable the Tenacity feature.