Informatica and Teradata

Third Party Software

Informatica and Teradata

Hello all,

Could someone please assist me with an issue that I am currently experiencing?

When we currently attempt to execute workflows that use PowerExchange for Teradata PT, the workflow fails to initialise due to "resources not being available".

This appears to be due to the "IgnoreResourceRequirements" option being set to "No" in the Integration Service Advanced Properties within the Administration Console.

The Production Informatica Environment in question consists of two nodes operating in a grid.

However, there are certain existing workflows that require node resources to be explicitly defined. For example, there is a workflow that node resource explicitly defined to create an identical lookup cache in each node. This is so successor workflows executing under normal round robin load balancing circumstances can reference a consistent lookup cache, regardless of which node it is assigned to execute on.

Therefore, we cannot set the "IgnoreResourceRequirements" option to "Yes" in the Prod environment.

Has anyone encountered this sort of scenario during their implementation of PWX for TPT into an Informatica Grid environment that requires Ignore Resource Requirements to be set to No?

The error message returned is:

2012-05-07 15:35:49 : ERROR : (20697 | 1431898432) : (IS | IS_EDWACPT) : Node06_cletla4 : LM_44128 : Failed to start process [Executor - Master] of task [Session task instance [s_m_XXXX_ODS_TO_XXXX_IDS] Session task instance [s_m_XXXX_ODS_TO_XXXX_IDS]] with error [ Request [Session task instance [s_m_XXXX_ODS_TO_XXXX_IDS]:] resource requirements [PowerExchange for Teradata PT ] rejected [2] nodes [Node07_cletla5 Node06_cletla4 ] with memory available. Total nodes [2]; Available for dispatch [2]; With no memory available [0]; With no CPU available [0]; Reached MaxProcesses [0]. Request [Session task instance [s_m_CUST_XXXX_TO_XXXX_IDS]:] has been rejected on [2] nodes [Node07_cletla5 Node06_cletla4 ] because the resources [PowerExchange for Teradata PT ] are not available.].

2012-05-07 15:35:49 : ERROR : (20697 | 1431898432) : (IS | IS_EDWACPT) : Node06_cletla4 : LM_44142 : Failed to start the execution phase for the task [Session task instance [s_m_XXXX_ODS_TO_XXXX_IDS]] with error [ Request [Session task instance [s_m_XXXX_ODS_TO_XXXX_IDS]:] resource requirements [PowerExchange for Teradata PT ] rejected [2] nodes [Node07_cletla5 Node06_cletla4 ] with memory available. Total nodes [2]; Available for dispatch [2]; With no memory available [0]; With no CPU available [0]; Reached MaxProcesses [0]. Request [Session task instance [s_m_XXXX_ODS_TO_XXXX_IDS]:] has been rejected on [2] nodes [Node07_cletla5 Node06_cletla4 ] because the resources [PowerExchange for Teradata PT ] are not available.].

2012-05-07 15:35:51 : ERROR : (20697 | 1410918720) : (IS | IS_EDWACPT) : Node06_cletla4 : LM_36320 : Session task instance [s_m_XXXX_IDS]: Execution failed.

3 REPLIES
Teradata Employee

Re: Informatica and Teradata

Hi,

We had faced the similar issue actually not everything is fixed at our end but we are still trying all the options. When we faced this issue we created a new IS with one property to ignore the resource requirements and it worked. 

I hope this will give you an idea that you are not alone in having issues with Informatica TPT connection.

Regards,

Ali

Teradata Employee

Re: Informatica and Teradata

Hi,

I am new to Teradata , but seasoned in informatica. In an effort to improve things I would like to have a list of all issues that we face using Teradata PT and Informatica.

Thanks,

Sachi.

Teradata Employee

Re: Informatica and Teradata

I tried to find LM_44128 in several infa.docs(version 811, 861,901HF2), but no luck. Very same with LM_44142. Only LM_36320 is there, but this one is a bit common. 

Anyway LM more like indicates it is not error messages related to PowerExchange (as they prefix all err.messages with PWX) 

Speaking of resources, you have to consider also other variables set. It will quite change the resource availability and load-balancing ie dispatching the sessions.

Refer to LN_90_AdministratorGuide.pdf, chapter 'Defining Resource Provision Thresholds'. 

MaximumMemory

MaximumCpuRunQueueLength

MaximumProcesses - this one kind of depends on how you set 'SessionOnGrid', 'IgnoreResourceRequirements' and if you still have default:10 with two int_svc per node configuration it might allows you to have 20(sessions) + 20(commands) or just 20(sess+cmd).

Note: if you set this(maxproc) to 0, it will prevent to dispatch task to node. 

Note: IgnoreResourceRequirements can be set to enable/disable as well to n/a. ...

You may try to set above mentioned resource threshold(s) to some really high numbers (ad one digit) and load balancer will ignore that correspond threshold. So you can bypass the resource check to see if there is some hidden issue within PWX or/and PC.

So if the log said:

With no memory available [0]; With no CPU available [0]; Reached MaxProcesses [0].

it seems you are out of your resource thresholds, so no dipsatch, not even task init will occurs.

Cheers
-=[VH]=-