Hi,

In informatica one of our mappings are using oracle target table. Daily it runs in production and complete in 10 min. but suddenly its just running and running. we stopped it forcely. what could be the potential cause for its continuous run?

Thanks.

There could be many reasons for this. One that comes to my mind is database statistics. When was the last time you gathered stats? The other reasons could be duplicate keys on the target table or if you have setup your session to collect all kinds of stats and data in the logs (it would just take longer but not a whole lot) or huge lookup source with no calculated cache settings….I could go on with this but it would be useless. I would like you to provide some information. Tell me about the version, the OS, the DB version, and all other architectural details. And tell me a bit about your mapping as well. If you want, go ahead and paste the session log here. I will take a look at it, see if I can find the issue and then remove it from the site.

Kirtan

Hope this helps…
Kirtan

Kirtan

In case of Lookup Transformation, Informatica also sorts the data by condition ports sequence. In cases where lookup cache is needed to be written to the physical disk, this sorting operation itself can become time consuming. But this could be advantageous if you can select the rows to be processed from the source qualifier in the same sorted order as the lookup condition ports sequence. So, if cache data for a particular key is in memory, then most probably the data for the adjacent keys will also be in memory. In this case, the time that lookup transformation would take to lookup data would keep increasing for each row as it would have to keep digging deeper in the file for each new row. Eventhough it sounds bad, it’s not it’s better than having data in random order. With appropriate indexes on the source tables, this operation could become very fast.

Wherever possible, use sorted data for these transformations. It is advisable to count appropriate amount of cache settings for each transformation that uses caching. Also one must consult the DBAs to come up with a good indexing strategy for all source tables.

Transformations that use caching for their process are…

Lookup Tranformation
Joiner Tranformation
Aggregator Tranformation
Rank Tranformation
Sorter Tranformation

This setting tells Informatica about the number of values that are stored in the repository when the session is started. The way Informatica processes this value is the key. Every time during the life of a session when this value is reached, Informatica queries the repository to get the next value for the Seq. Generator. So if you have this value set to 1, Informatica will query the repository database for every row that asks for a value from this transformation. And as you can imagine, this would definitely add some time to your the life of a session run.

If you set this number to some higher value like 15000, Informatica will query the repository after every 15000 rows. That may not necessarily be a bad thing. It would not have a major impact on total execution time. If the number is set to zero this setting would no more be a factor. Because then Informatica would NOT store the value of in the repository. Instead, it would be kept in the session memory.

The sequence number is kept on the server if the value is set to zero. In all other cases where it is set to be 1 or greater, the value is stored in the repository and the Informatica server process retrieves it from the database.

hope this helps…

Kirtan

Create table t1 (a number, b number);

insert into t1 values (1,1);
insert into t1 values (1,2);
insert into t1 values (1,3);
insert into t1 values (2,1);
insert into t1 values (2,2);
insert into t1 values (2,3);
insert into t1 values (3,1);
insert into t1 values (3,2);
insert into t1 values (3,3);

select * from t1 order by 1,2;

####
(A hint aside: You must specify the order in which you want the data to be back. It is completely wrong to say that oracle will return the data in order it was inserted.)
####

A B
----- ------
1 1
1 2
1 3
2 1
2 2
2 3
3 1
3 2
3 3

Now, let’s say you want to retrieve all the records from table t1 in a fashion where all the values in column B that belong to the group Column A should be shown side by side. Something like

A Val1 Val2 Val3
-- ---- ---- ----
1 1 2 3

One way would be to write a procedural code that stores different values of a group in an array or a series of variables and then displays them on screen or returns them to the calling program.

Or

You could just write a simple SQL statement that does it for you. You could write a piece of code that looks like this…

select
a
,max(decode(b,1,b,null)) col1
,max(decode(b,2,b,null)) col2
,max(decode(b,3,b,null)) col3
from t1
group by a;

A COL1 COL2 COL3
—– ——- ——- ——-
1 1 2 3
2 1 2 3
3 1 2 3

3 rows selected

… and you won’t have to worry about supporting an object such as a function or a procedure.

What if you had null values in one of the columns.

update t1 set b=null where a=2 and b=2;

One row updated

select
a
,max(decode(b,1,b,null)) col1
,max(decode(b,2,b,null)) col2
,max(decode(b,3,b,null)) col3
from t1
group by a;

A COL1 COL2 COL3
—– ——- ——- ——-
1 1 2 3
2 1 3
3 1 2 3

3 rows selected

There are many ways to write pivot queries. This is probably the easiest way of doing it.

Using Informatica to perform pivot operation.

You can use the Normalizer Transformation to generate rows out of columns. But to pivot values in rows into columns you would have to use Aggregator Transformation. You have to use the *FIRST* function to achieve this. Here is an example…

Suppose you have a source table with this data that is a record of monthly expenses for each of your departments. create table deptexp (sales_id number(5), mon char(3), amt number(10,2));

insert into deptexp values (1,’JAN’,100);
insert into deptexp values (1,’FEB’,120);
insert into deptexp values (1,’MAR’,135);
insert into deptexp values (2,’JAN’,110);
insert into deptexp values (2,’FEB’,130);
insert into deptexp values (2,’MAR’,120);
Commit;

You want to load this data after denormalizing it into this structure.
create table deptexp1 (DEPT_ID number(5), JAN_AMT number(10,2), FEB_AMT number(10,2), MAR_AMT number(10,2))
The data after our process would look like…
DEPT_ID JAN_AMT FEB_AMT MAR_AMT
1 100 120 135
2 110 130 120

Do the following to accomplish this.
1. Create an Aggregator transformation with the following ports and expressions:
NAME IN/OUT EXPRESSION GROUP BY
DEPT_ID IN YES
MONTH IN NO
AMOUNT IN NO
JAN_AMT OUT FIRST(AMOUNT, MONTH='JAN')
FEB_AMT OUT FIRST(AMOUNT, MONTH='FEB')
MAR_AMT OUT FIRST(AMOUNT, MONTH='MAR')
APR_AMT OUT FIRST(AMOUNT, MONTH='APR')
2. Connect the DEPT_ID, MONTH and the AMOUNT ports from the Source Qualifier to the Aggregator.
3. Connect the JAN_AMT, FEB_AMT, MAR_AMT, etc. ports to the target.
And that would do it…

Hope this helps…

Kirtan

Here are the details…


This was truly interesting and funny!

Let’s see how houston treats us!!!