How to: |
Flows properties allow you to view or set properties that apply to the entire data flow. These include:
Specify flow properties in the Properties pane by clicking Properties in the Tools group of the Flow tab.
If you right-click anywhere in the Properties pane, a shortcut menu opens, with the following options available:
The Properties pane opens, as shown in the following image.
The General attribute section of the Properties pane has the following fields and options:
Is a description of the flow. You can enter up to 150 characters. Descriptions appear in the navigation pane next to the flow name.
Are comments regarding the flow.
This section also provides information on the flow name, the user who created the flow, and the date it was last modified.
The Properties pane opens.
The Execution attribute section of the Properties pane has the following fields and options:
Allows faster loading when the source and target are in the same relational database. This option can be used with databases that use the MERGE command, as well as Insert only operations.
When selected, a flow will continue to run, even if an error is generated.
Causes the flow to fail with a non-zero return code if the number of errors specified is exceeded. Applies to relational targets when Insert/Update or Insert records from memory is used. Any rows written to the RDBMS are committed to the RDBMS. The default value is 10000000, unless this is overridden in the Run Options found in the Tools group of the Home tab.
A relational database may return an error for a constraint violation, such as a Unique Index constraint, a Not Null constraint, or a user-specified constraint.
If such errors are not expected, you may want to fix their cause without waiting for the entire flow to be processed. Using a low value, such as 10, can provide enough information to determine the cause of the problem, without running the entire job.
If such errors are expected, and you want to continue processing anyway, use a high value, one greater than the number of records in the source, or do not select the Stop processing after check box.
Allows you to stop processing if no data is returned. When this option is selected, and no data is returned, code 18708 occurs.
The Properties pane opens.
The Restart attribute section of the Properties pane has the following fields and options:
Is the number of times a flow will be restarted if the execution fails.
Note: The amount of time between restart attempts can be set for the server. The default value is 60 seconds. For more information, see Setting Up DataMigrator.
Is the point from which the next attempt will be made. The options are Beginning or Last Commit.
Note: Last Commit cannot be used for flat file, delimited file, or XML targets. Last Commit can only be used for existing targets, and cannot be used with Prior to Load Options of Delete all rows from table, Truncate table, or Drop table.
Note: Your DataMigrator Server must be configured for email notification to use this option.
The Properties pane opens.
The Log and output destinations section has the Send HTML output as inline message. When selected, if any stored procedures called by the flow generate an output, the message is included as message text, instead of as an attachment.
E-Mail On Start, E-Mail On Completion, and E-Mail On Failure all have the following fields and options:
Select this to enable when an email should be sent.
The email addresses to which the messages will be sent. Place each email address (or user ID configured on the server with an associated email address) on a new line with no separators.
Select this option to get the following options:
Note: Your DataMigrator Server must be configured for email notification in order to use this option. See How to Configure the Server for E-mail Notification.
Note: These settings are not available if the Optimize Load option is enabled.
The Properties pane opens.
The Record Logging attribute section of the Properties pane has the following fields and options:
Logs transactions rejected by an RDBMS due to a constraint violation or data type error. For flat file targets, format errors are also recorded.
Logs transactions rejected due to a duplicate key.
Logs transactions rejected for not meeting a VALIDATE condition
Logs transactions rejected when a required key is not found.
Logs transactions rejected due to a format error. Format errors only apply to direct load flows.
Logs transactions that were accepted.
Logs all transactions.
WebFOCUS | |
Feedback |