PowerCenter 9.0.1 Workflow Basics Guide (English)

Guidelines for Configuring Environment SQL

Consider the following guidelines when creating the SQL statements:

¨ You can enter any SQL command that is valid in the database associated with the connection object. The

Integration Service does not allow nested comments, even though the database might.

¨ When you enter SQL in the SQL Editor, you type the SQL statements.

¨ Use a semicolon (;) to separate multiple statements.

¨ The Integration Service ignores semicolons within /*...*/.

¨ If you need to use a semicolon outside of comments, you can escape it with a backslash (\).

¨ You can use parameters and variables in the environment SQL. Use any parameter or variable type that you can define in the parameter file. You can enter a parameter or variable within the SQL statement, or you can use a parameter or variable as the environment SQL. For example, you can use a session parameter,

$ParamMyEnvSQL, as the connection or transaction environment SQL, and set $ParamMyEnvSQL to the SQL statement in a parameter file.

¨ You can configure the table owner name using sqlid in the connection environment SQL for a DB2 connection.

However, the table owner name in the target instance overrides the SET sqlid statement in environment SQL.

To use the table owner name specified in the SET sqlid statement, do not enter a name in the target name prefix.

Database Connection Resilience

Database connection resilience is the ability of the Integration Service to tolerate temporary network failures when connecting to a relational database or when the database becomes unavailable. The Integration Services is resilient to failures when it initializes the connection to the source or target database and when it reads data from or writes data to a database.

You configure the resilience retry period in the connection object. You can configure the retry period for source, target, SQL, and Lookup transformation database connections. When a network failure occurs or the source or target database becomes unavailable, the Integration Service attempts to reconnect for the amount of time configured for the connection retry period. If the Integration Service cannot reconnect to the database in the amount of time for the retry period, the session fails.

The Integration Service will not attempt to reconnect to a database in the following situations:

¨ The database connection object is for an ODBC or Informix connection.

¨ The transformation associated with the connection object does not have the output is deterministic option enabled.

¨ The value for the DTM buffer size is less than what the session requires.

¨ The truncate the target table option is enabled for a target and the connection fails during execution of the truncate query.

¨ The database connection fails during a commit or rollback.

Use the retry period with the following connection types:

¨ Relational database connections

¨ FTP connections

¨ JMS connections

¨ WebSphere MQ queue connections

Database Connection Resilience 119