Best practices to oracle data integrator

This is my first post.

I would like to start with some best practices we should follow in oracle data integrator ELT plans:

1. Generally we use variables in procedures. But it is not a good practice. We should use options in procedures instead of variables. Options are input parameters to our procedures. We can provide option value as Substitution variable by preceding the variable name with #. ( Will be discussed in detail later in upcoming posts)

2. Recurring tasks are very common for data manipulation in every data warehouse design. So we usually write complex procedure to provide solution for recurring tasks. After writing complex procedure it is a good practice to convert into a KM ( Knowledge module) by using ODI Substitution API.

3. Since operating system commands are specific to OS. We should avoid OS specific commands whenever possible.

4. Every procedure may contain one or more commands. When writing commands it is highly recommended that use the ODI substitution API.

5. It is Best practice to define options to improve code re usability.6. It is the power of ODI , rather than writing external scripts like shell scripts or

jython scripts or perl scripts ,etc, we would include the code in ODI procedure. Then we can execute the procedure as a package step or we can execute directly.

7. We should almost never specify hard coded values like physical information such as  the database name or schema name in the designer. Because they may change depending on the execution context.

Visit www.odibestpractices.co.nr