The debugger in Informatica: Session, Breakpoint, Verbose Data, and Mapping

As we examined in past points, planning is an assortment of source and target objects connected together by a bunch of changes. These changes comprise rules that characterize the information stream and how the information is stacked into the objectives.

What is Debugger?

The debugger is an extremely convenient utility in Informatica. At the point when we execute the planning, Informatica executes the planning in light of the change rationale characterized.

Its execution is like group mode execution where we can't see the transitional outcomes, or how the information is getting adjusted from one change to another.

Numerous multiple times we get the information in the objective as most would consider normal. With the assistance of a debugger, we can break down how the information is moving inside the planning. We can dissect the information line by column in a debugger.

The utilization of the debugger requires a meeting example, we can either reuse a current meeting that was made before to run the planning, or we can make a new investigation meeting occasion. Since during the investigation, the information will be obtained from the source, we have the choice of how to manage that information.

These choices can be set during the arrangement of the debugger.

To screen the debugger, there are two windows in the Informatica planner

Target window

Occasion window

In the target window, the objective record which will be embedded into the objective table is shown. In the case of a window, you can choose any of the change examples of the planning. From that point onward, every one of the ports of that change is apparent in this window, and you can examine the information and the way things are getting changed.

Moves toward using the debugger in a planning

Informatica creator gives the element to utilize the debugger to investigate mappings. It implies we can troubleshoot and examine any current planning. The prerequisite for the debugger is that the planning ought to be a substantial guide.

In the activity, we will troubleshoot our current planning "m_emp_emp_target" which we made prior. In our source information, we will check for a specific record of employee_name ='SCOTT'. For Scott, we will confirm the qualities are brought in Informatica and regardless of whether the record is pushed to the objective accurately.

Our source information for the "emp" table seems to be this.

The debugger in Informatica: Session, Breakpoint, Verbose Data, and Mapping

For the name "SCOTT", involving debugger we will make sure that an incentive for the "sal" (pay) section is brought in the Informatica.

Stage 1 - Open Informatica Creator and in Fashioner open the planning "m_emp_emp_target" by double tapping on it. It will open-source qualifier and target definition tables showing planning inside Mapping Designer.

Click here for more

The debugger in Informatica: Session, Breakpoint, Verbose Data, and Mapping

Stage 2 - Now start the debugger

Click on the mappings menu choice

Select Debugger from the choices

Select "begin debugger" choice

The debugger in Informatica: Session, Breakpoint, Verbose Data, and Mapping

Stage 3 - Select next on investigating planning window

The debugger in Informatica: Session, Breakpoint, Verbose Data, and Mapping

Click here for more

Stage 4 - In the following window, you will get a choice to choose meeting type. You can utilize an existing meeting, and existing reusable meetings or you can make a troubleshoot meeting example.

At the point when you utilize the current meeting, Informatica will utilize the previous meeting which you made for this planning. At the point when you select the make to troubleshoot meeting occasion, another meeting case will make for investigation.

In this model, we will choose an existing reusable meeting example. The reconciliation administration will be the default.

Select "utilize a current meeting example" choice

Click straightaway

The debugger in Informatica: Session, Breakpoint, Verbose Data, and Mapping

Stage 5 - In the new window, Informatica will provoke you to choose the current meeting for troubleshooting.

Select the meeting "s_m_emp_emp_target" and click the next button

The debugger in Informatica: Session, Breakpoint, Verbose Data, and Mapping

Click here for more

Stage 6 - In the following window there will be a choice "Dispose of target information", we select this choice as during troubleshooting we would rather not load any information in our objective table.

Select the choice "Dispose of target information."

Select objective table "emp_target"

Click the finish button.

Debugger in Informatica: Session, Breakpoint, Verbose Data, and Mapping

With the above advances, we have arranged and begun the debugger. Presently we can investigate the planning.

Stage 7 - The debugger has begun, yet it hasn't gotten any lines from the source. During troubleshooting, it gets information from source line by column. To begin get the first column from the source

Select mappings choice from the menu

Select debugger choice

Select the next example choice

Stage 8 - In the case window you will see the primary brought record from the source qualifier.

The debugger in Informatica: Session, Breakpoint, Verbose Data, and Mapping

On the off chance that you break down the occurrence window, it will show the primary record - name "SMITH" line. This isn't the record that we are searching for. So we can move to the following occasion.

Click here for more

Stage 9 - To go to the next occasion (to move to the next push)

Press the F10 button (the easy route for going to the next occasion, rather than going to planning choice then debugger choice)

In the wake of moving to the next example, the information in the case window will change to the next record.

Stage 10 - Keep squeezing the F10 button, till you reach to the expected record of the "SCOTT" worker. When you arrive at that point, the occurrence window will be like as displayed underneath

This is the example, that we were searching for. So in the occasion window, we can break down the information. Whether it is coming accurately, or any worth is absent.

In the source information, the subtleties of the "SCOTT" representative were like work = "Examiner", chief id = "7566", sal "3000."

What's more, in the debugger, for the worker "SCOTT" we have broken down this large number of subtleties, and they are coordinating with the source information, so we are guaranteed that the records were brought accurately by the source qualifier.

Utilizing breakpoint in the debugger

At the point when we are searching for a specific column of information like in the past model, then as opposed to going to each occasion of source information, we can characterize breakpoints.

A breakpoint is a condition or a bunch of a condition characterized during design of investigating with the end goal that when that condition turns out to be valid the debugger stops to that specific occasion.

For instance in the event that we characterize deptno=20 in a breakpoint, at whatever point for a record on the off chance that this condition is valid, the debugger will stop to that occasion of information.

Stage 1-To design the breakpoint

Go to the mappings menu

Select debugger choice

Select "alter breakpoints" choice

Stage 2 - You will see an "alter breakpoint" window as displayed beneath

The debugger in Informatica: Session, Breakpoint, Verbose Data, and Mapping

Stage 3 - In the breakpoint window, click on the add button

The debugger in Informatica: Session, Breakpoint, Verbose Data, and Mapping

Stage 4 - In the new window

Select the SQ_EMP as the case

Select OK button

Debugger in Informatica: Session, Breakpoint, Verbose Data, and Mapping

Stage 5 - The past window will look as displayed underneath

Debugger in Informatica: Session, Breakpoint, Verbose Data, and Mapping

Stage 6 - You have a breakpoint, presently you need to characterize the breakpoint condition. To characterize breakpoint condition

Click on the "add new condition" symbol

Another column under the condition tab will show up. Here we can design the condition.

Stage 7 - In the condition table

In the port drop-down, select the "ENAME" choice ( as we are troubleshooting for record ename='SCOTT')

In the worth box, enter esteem "SCOTT."

Select OK button

See also here -->>

Stage 8 - Now start the debugger as referenced in the past point

Go to planning menu - > select debugger choice - > select beginning debugger - > select meeting case

Stage 9 - Once the debugger is begun

Select mappings menu

Select debugger choice

Select proceed with the choice

The debugger will go to each case of the line itself and will check for the condition "ename=SCOTT". The record for which this condition is valid, the debugger will end on that occurrence. So when the information volume is high, then, at that point, rather than going for each example of source record you can design a breakpoint, and you can straightforwardly leap to that record.

When the Informatica is finished going through every one of the cases, the debugger is halted consequently. To investigate the information once more, you need to restart the debugger once more.

Read More :