Property | Value |
|---|---|
Source Schema Mismatch | Select one of the following: • Treat as Error (default) - If a source schema mismatch occurs, an error message is displayed. This is due to a change in the layout after building the transformation. If you are working in Map Designer user interface (not running from the command line), you can change the mismatch option and connect again. • Use Map Schema - Select this option when you have selected the correct schema. For example, you built a transformation from a DTD where you have mapped all elements and attributes that exist, but the data does not have every element and attribute. • Use Connection, Match by Position - Select this option if there was a change to a field and the field expressions can be matched by ordinal position. For example, you build a transformation with a header to have field names. If this transformation is run against a field that has the same number of fields, but no header record, you can select Use Connection, Match by Position to indicate that the engine must accept Field1, Field2, and Field3 from the new transformation and assign the field expression in the following order: – Connection Field1 gets Map AccountNo (field at position 1) Expression – Connection Field2 gets Map First Name (field at position 2) Expression • Use Connection, Match by Name - Select this option when there is a change to a field and the field expressions can be matched by Name. For example, the transformation has the correct schema but, a new field was added to the table. You want to get the new field and keep all the fields and mapping that already exists. The map schema and the connection schema is merged, and any dangling map field expressions are restored by Name. If the field name exists in the connection schema, the field expression is assigned. Otherwise, the field expression is lost. |
Target Schema Mismatch | Select one of the following: • Treat as Error (default) - If a target schema mismatch occurs, an error message appears indicating that there has been a change in the layout since the transformation was built. If you are working in the Map Designer user interface (not running from the command line), you can change the mismatch option and try to connect again. • Use Map Schema - Select this option when the source and target files have different data structures, but you do not want an error to be returned at run-time. • Use Connection, Match by Position - Select this option if there was a change to a field and the field expressions can be matched by ordinal position. For example, you build a transformation that used a header so that field names display. If this transformation is run against a field that has the same number of fields (but no header record), you can select this option to indicate that the engine must accept Field1, Field2, Field3 from the new transformation and assign the field expression in order. • Use Connection, Match by Name - Select this option if there was a change to a field and the field expressions can be matched by Name. For example, the transformation is the correct schema but, a new field is added to the table. You want to get the new field and keep all the fields and mapping that already exists. The map schema and the connection schema are merged, and any dangling map field expressions is restored by Name. If the field name exists in the connection schema, the field expression is assigned. Otherwise, the field expression is lost. |
Null Handling | If the target field is set to not accept nulls, this property allows you to select how the Map Designer transforms the data. Note: This option applies to SQL targets only. • Ignore - If a null is encountered, the record is not rejected and the transformation proceeds as usual. In this case, the only way to avoid having the record rejected is to write an expression for the target field so that it does not contain a null value. A message is not logged and the engine handles the null as best it can. For example, for a decimal field, a null is written as a zero. For a string field, it is written as an empty string. • Treat as Warning - If a null is encountered, the record is not rejected and the transformation continues uninterrupted. A warning message is logged file indicating a null was encountered. • Treat as Error (default) - If a null is encountered, an error message appears. If the maximum error count is set to 1, the transformation is stopped. In general, Actian DataConnect attempts to provide an appropriate value (that is, 0 for a numeric field, "" for text fields, and so on.). If unable to provide an appropriate value, the attempt to send the record to the server results in an error from the server. |
Overflow Handling | When you have numeric fields in your source that have a higher precision than your target numeric fields, an overflow occurs. Select one of the following: • Ignore - If an overflow occurs, the transformation proceeds as if the overflow did not occur. • Treat as Warning - If an overflow occurs, a warning message is written to the log file, but the transformation continues uninterrupted. • Treat as Error (default) - If an overflow occurs, an error message appears. If the maximum error count is set to 1, the transformation is stopped. Note: Single-mode connectors and multimode connectors may generate overflow errors. |
Truncation Handling | When the text written to the target is longer than the target field, truncation occurs. Select one of the following: • Ignore - If truncation occurs, the transformation proceeds and ignores the truncation. • Treat as Warning - If truncation occurs, a warning message is written to the log file. The transformation continues uninterrupted. • Treat as Error (default) - If truncation occurs, an error message appears. If the maximum error count is set to 1, the transformation is stopped. Multimode connectors can generate truncation errors. |
Key Mismatch Handling | When the key upon which to update is not found key mismatch occurs. Select one of the following: • Ignore - If a key mismatch occurs, the transformation ignores the mismatch and proceeds. • Treat as Warning - If a key mismatch occurs, a warning message is written to the log file. The transformation continues uninterrupted. • Treat as Error (default) - If a key mismatch occurs, an error message appears. If the maximum error count is set to 1, the transformation is stopped. Multimode connectors can generate key mismatch errors. Note: - Any old map will have this value set to Treat as Error. However you can reload the map and change this value to a desired value. - Irrespective of the setting, when a key mismatch occurs, no update or delete will happen for that row. |
Max Thread Count | The maximum number of threads that can be executed at a time for a process. The default value is one. Check your license file. Every new process takes this preference value. |