Category: Informatica

Developing Global and Local repositories in Informatica

informatica

Informatica repository is used to store metadata information which will reside in a relational database. We can develop local and global repositories to share metadata information. Global Repository is the hub of the repository domain which is used to store common objects that multiple developers can use through shortcuts. A global repository cannot be converted to local repository and these objects may include operational or application source definitions, reusable transformations, mapplets and mappings. Informatica local repository is any repository within the domain that is not the global repository and it is used for development. These local repositories can create shortcuts to objects in shared folders in the global repository and can promote local repository to global repository. DataTerrain, with years of experience and reliable experts, is ready to assist. We have served more than 250 customers in the US and over 70 customers worldwide. We are flexible in working hours and do not need any long-term binding contracts.

Read More +

What are Partition Points in Informatica

Informatica

The partition points in Informatica mark the thread boundaries in a pipeline and divide the pipeline into stages. These can be retained or deleted based on the following transformations in the pipeline. ● Source Qualifier and Normalizer Transformation – controls the integration service in Informatica to extract data from source and passes it to the source qualifier and deletion cannot be done for this partition point. ● Rank and Unsorted Aggregator Transformation – ensures that the integration service in Informatica groups rows properly before sending it to the transformation and you can delete the partition points if the pipeline contains only one partition or it passes all rows in a group to a single partition before they enter the transformation. ● Target Instances – controls how the writer passes data to the targets and cannot delete this partition point. ● Multiple Input Group Transformation – ensures that the integration service uses one thread to process each partition at a custom transformation that requires one thread per partition and cannot delete this partition point. DataTerrain, with years of experience and reliable experts, is ready to assist. We have served more than 250 customers in the US and over 70 customers worldwide. […]

Read More +

Factors that affect Grid Recovery in Informatica

Informatica Integration

When an Informatica workflow is run on a grid, service processes and DTM processes run on different nodes and behavior also depends on flowing factors. ● High availability option – Workflows fail over to another node if the node or service shuts down, if availability is not high, a workflow can be manually restarted on another node to recover it. ● Recovery strategy – A recovery strategy can be configured for tasks within the workflow and when the workflow suspends the recovery, behavior depends on the recovery strategy configured for each task. ● Shutdown mode – When an Informatica Integration Service can specify that the service completes, aborts, or stops processes running on the service, the failover and recovery behavior depend on which service process is shut down. ● Running mode – If the workflow runs on the grid, the Informatica Integration Service can recover workflows and tasks on another node. ● Operating mode – If the Informatica Integration Service runs in safe mode, recovery is disabled for sessions and workflows. DataTerrain, with years of experience and reliable experts, is ready to assist. We have served more than 250 customers in the US and over 70 customers worldwide. We are […]

Read More +

Overview of Grid processing in Informatica

informatica

When an Informatica PowerCenter domain has multiple nodes then workflows and sessions can be configured to run on a grid. The performance and scalability in Informatica can be increased by running the service on each available node of the grid. The integration service distributes workflow and sessions based on the configuration done on the workflow or the sessions. When it comes to workflow, it distributes the Session, Command and predefined Event-Wait tasks within workflows across the nodes in a grid. The integration service in Informatica distributes session threads across nodes in a grid. It is important to note that you must have the server grid option to run workflows and sessions on grid. DataTerrain, with years of experience and reliable experts, is ready to assist. We have served more than 250 customers in the US and over 70 customers worldwide. We are flexible in working hours and do not need any long-term binding contracts.

Read More +

Guidelines to create Key Ranges in Informatica

Informatica

The key range partitioning in Informatica distributes rows of data based on a port or set of ports that you define as the partition key. Guidelines to create key ranges are mentioned below. ● The partition key must contain at least one port. ● The range for each port in the partition key should be specified. ● The Informatica PowerCenter standard date format can be used to enter dates in key ranges. ● The workflow manager does not validate overlapping string, numeric ranges, the gaps, or missing ranges. When you define key range partitioning at a source qualifier transformation, the Informatica Integration Service defaults to pass-through partitioning if you change the SQL statement in the Source Qualifier transformation. If a row contains a null value in any column or falls outside of the key ranges then the integration service sends that row to the first partition. DataTerrain, with years of experience and reliable experts, is ready to assist. We have served more than 250 customers in the US and over 70 customers worldwide. We are flexible in working hours and do not need any long-term binding contracts.

Read More +

Overview of Deployment groups in Informatica

Informatica groups

Deployment groups in Informatica are used as containers that allow smart grouping of objects to facilitate the deployment between different folders, repositories, and environments. Deployment Groups consists of two different types such as Static and Dynamic. Informatica Deployment Groups can contain folders, mappings, mapplets, reusable transformations, sources, targets, workflows, sessions, and tasks and can help transfer these objects into multiple folders across repositories in different domains. Static group is generally used for one-off objects transfers and also you can annually add a specific version of your objects. Dynamic group is generally used for recurring objects transfers. This dynamic group is also a Query-driven object list capturing the latest version of frequently updated objects DataTerrain, with years of experience and reliable experts, is ready to assist. We have served more than 250 customers in the US and over 70 customers worldwide. We are flexible in working hours and do not need any long-term binding contracts.

Read More +

Tracing levels types in Informatica

Informatica ETL

Informatica tracing levels can be configured at the transformation session levels and has 4 different types of tracing levels. None – This level is applicable at session level only and the integration service uses the tracing levels configured in the mapping Terse – Log initialization information, error messages and notification of rejected data in the session log file. Normal – Integration service logs initialization and status information, errors encountered and skipped rows due to transformation row errors. Summarizes session results but not at the level of individual rows. Verbose Initialization – In addition to normal tracing the integration service logs additional initialization details; names of index and data files used and detailed transformation statistics. Verbose Data – The Informatica Integration Service logs each row that passes into mapping. When you configure the tracing level to verbose data, the Integration Service writes row data for all rows in a block when it processes a transformation. DataTerrain, with years of experience and reliable experts, is ready to assist. We have served more than 250 customers in the US and over 70 customers worldwide. We are flexible in working hours and do not need any long-term binding contracts.

Read More +

What is Stored Procedure Transformation in Informatica

Informatica BI

Stored Procedure Transformation in Informatica is a passive transformation and can be used in both connected and unconnected mode. The stored procedures are stored and run within the database and it also contains a pre-compiled collection of PL-SQL statements. Some of the tasks you can do with stored procedures areCheck the status of a target database before loading data into it.Determine if enough space exists in a database.Perform a specialized calculation.Dropping and recreating indexes. Informatica stored procedures must exist in the database before creating a stored procedure transformation and the stored procedure can exist in a source, target or any database with valid connection to the integration service. DataTerrain, with years of experience and reliable experts, is ready to assist. We have served more than 250 customers in the US and over 70 customers worldwide. We are flexible in working hours and do not need any long-term binding contracts.

Read More +

Where to use Informatica and DataStage

Datastage and Informatica

DataStage is an ETL tool that extracts data, transforms and loads data from source to the target. DataStage facilitates business analysis by providing quality data to help in gaining business intelligence. Informatica is used for Data integration. Informatica offers the capability to connect & fetch data from different heterogeneous sources and processing of data. These are the major differences between Informatica and DataStage, you can select the relevant tool based on the requirement: ● Multiple Partitions: Informatica offers partitioning as dynamic partitioning which defaults a workflow, not at every Stage. It also offers other partitioning choices as well at the workflow level. Whereas, DataStage offers 7 different types of multi-processing partitions. ● User Interface: Informatica offers access to the development and monitoring effort through its 4 GUIs – offered as Informatica PowerDesigner, Repository Manager, WorkflowDesigner, Workflow Manager. Whereas, DataStage caters to development and monitoring its jobs through 3 GUIs – IBM DataStage Designer(for development), Job Sequence Designer(workflow design) and Director(for monitoring). ● Type of Link: To link two components in Informatica, link at the column level and connect each and every column between the two components. While, In DataStage, link at the component level, and then map individual columns. This […]

Read More +