top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration Why to Join

    Get Free Article Updates

Facebook Login
Site Registration

Scheduling options of Informatica Tool Workflows/Jobs

+2 votes
1,463 views

Informatica ETL tool has a built-in scheduler, which is used to schedule the workflows or jobs to run at specified time intervals.

The steps to locate scheduler:

  • Login to the workflow manager.
  • Open any folder.
  • Select the workflow that needs to be scheduled.
  • Go to the toolbar, click on workflow->edit. You will get a window.

enter image description here

Click on the scheduler tab on that window.
enter image description here

The below window is the place Where you can specify the scheduling times.
enter image description here

The scheduling options are independent of the operating system (Unix or windows) where the informatica services are installed. Various scheduling options available in informatica


Run options: The run options are used to specify when to run the workflow. There are three types of run options available in informatica. They are

  1. Run on Integration Service Initialization: When the informatica services are restarted, the integration service runs the workflow.
  2. Run on Demand: By default this option is checked. You have to manually run the workflow. The workflow is not in scheduled state.
  3. Run Continuously: The integrations service runs the workflow continuously until the End on date option or End after number of runs reached.

Start Options: The start options are used to specify the date and time from which the workflow starts to run. If you specified the scheduling options now and specified a future start date, then the workflow runs from that date onwards. Two options available:

  1. Start Date: Start date of the workflow.
  2. Start Time: Start time of the workflow.

End options: The end options are used to specify when the workflow should be removed from scheduling. There are three options available:

  1. End on: The workflow stops running after this date.
  2. End after: The workflows stops running after the specified number of runs.
  3. Forever: Workflow runs forever. There is no end date for the workflow.

Scheduling Options: The scheduling options are used to specify the intervals at which the workflow should run. The scheduling options are:

  1. Run Once: The workflows runs only one time at the specified start date and time.
  2. Run every: This option is used to specify the workflow to run every X days , Y hours and/or Z minutes.
  3. Customized Repeat: This option allows more flexibility to run the workflow daily or weekly or monthly.

posted Apr 29, 2014 by Shatark Bajpai

  Promote This Article
Facebook Share Button Twitter Share Button Google+ Share Button LinkedIn Share Button Multiple Social Share Button


Related Articles

Informatica PowerCenter is given with a set of options to take care of the error handling in your ETL Jobs.

Error Handling Functions
We can use two functions provided by Informatica PowerCenter to define our user defined error capture logic.

ERROR (): This function causes the PowerCenter Integration Service to skip a row and issue an error message, which you define. The error message displays in the session log or written to the error log tables based on the error logging type configuration in the session. You can use ERROR in Expression transformations to validate data. Generally, you use ERROR within an IIF or DECODE function to set rules for skipping rows.
Ex: IIF (TRANS_DATA > SYSDATE, ERROR ('Invalid Transaction Date'))

Above expression raises an error and drops any record whose transaction data is greater than the current date from the ETL process and the target table.

ABORT (): Stops the session, and issues a specified error message to the session log file or written to the error log tables based on the error logging type configuration in the session. When the PowerCenter Integration Service encounters an ABORT function, it stops transforming data at that row. It processes any rows read before the session aborts. You can use ABORT in Expression transformations to validate data.

Ex: IIF (ISNULL (LTRIM (RTRIM (CREDIT_CARD_NB))), ABORT ('Empty Credit Card Number'))

Above expression aborts the session if any one of the transaction records are coming without a credit card number.

Default Port Value Setting
Using default value property is a good way to handle exceptions due to NULL values and unexpected transformation errors. The Designer assigns default values to handle null values and output transformation errors. Power Center Designer let you override the default value in input, output and input/output ports.

Default value property behaves differently for different port types;
1. Input ports: Use default values if you do not want the Integration Service to treat null values as NULL.
2. Output ports: Use default values if you do not want to skip the row due to transformation error or if you want to write a specific message with the skipped row to the session log.
3. Input/output ports: Use default values if you do not want the Integration Service to treat null values as NULL. But no user-defined default values for output transformation errors in an input/output port.

Default Value Use Case

Use Case 1
Below shown is the setting required to handle NULL values. This setting converts any NULL value returned by the dimension lookup to the default value -1. This technique can be used to handle late arriving dimensions.
enter image description here

Use Case 2
Below setting uses the default expression to convert the date if the incoming value is not in a valid date format.
enter image description here

Error Handling Settings
Error handling properties at the session level is given with options such as Stop on Errors, Stored Procedure Error, Pre-Session Command Task Error and Pre-Post SQL Error. You can use these properties to ignore or set the session to fail if any such error occurs.
Stop on Errors: Indicates how many non-fatal errors the Integration Service can encounter before it stops the session.
On Stored Procedure Error: If you select Stop Session, the Integration Service stops the session on errors executing a pre-session or post-session stored procedure.
On Pre-Session Command Task Error: If you select Stop Session, the Integration Service stops the session on errors executing pre-session shell commands.
Pre-Post SQL Error: If you select Stop Session, the Integration Service stops the session errors executing pre-session or post-session SQL.
enter image description here

READ MORE
Contact Us
+91 9880187415
sales@queryhome.net
support@queryhome.net
#280, 3rd floor, 5th Main
6th Sector, HSR Layout
Bangalore-560102
Karnataka INDIA.
QUERY HOME
...