roopalidoshi
MIS
Hi,
Right now some of the challenges we have with persistent values (parameters) for ETL sessions. Please let us know if you have any information on following points
1) To Set Persistent Value: In our workflows, the persistent values are defined at session level. Each individual session uses these parameters while running the session but these persistent values are Set Only on the success event of the Workflow.
Therefore, even if a session is successful but other successive sessions have failed then workflow would fail. Hence, persistent values are not set even when session went successfully e.g. Session Shipment_Status loaded 10 Million rows but its next session Shipment_History failed then workflow session would also fail. Next time while running this workflow, session Shipment_Status would again read those 10 Million records and then would update these 10 Million records in Teradata (as persistent value was not able to set).
QUESTION: The persistent values should be set as soon as the Session is Successful, independent on the status of its workflow. How to set persistent values at session level?
2) To Reset Persistent Value: Resetting of persistent value is needed whenever there is need to go back in the past to read data from the source system. Currently there are 2 ways to reset persistent values
A) At Informatica session level, the persistent value can be reset directly to only NULL value in the workflow manager.
OR
B) Hard coding the 'where clause' condition for insert_date and update_date in the Source-Qualifier for a mapping.
There are situations like during Disaster Recovery when we want to change the persistent value to be set in the past lets say 2 days ago (but not reset to NULL). Since we don’t want to touch mapping during production, so do you know if there are any other ways to set these parameters?
Thanks in advance.
Roopali Doshi
Right now some of the challenges we have with persistent values (parameters) for ETL sessions. Please let us know if you have any information on following points
1) To Set Persistent Value: In our workflows, the persistent values are defined at session level. Each individual session uses these parameters while running the session but these persistent values are Set Only on the success event of the Workflow.
Therefore, even if a session is successful but other successive sessions have failed then workflow would fail. Hence, persistent values are not set even when session went successfully e.g. Session Shipment_Status loaded 10 Million rows but its next session Shipment_History failed then workflow session would also fail. Next time while running this workflow, session Shipment_Status would again read those 10 Million records and then would update these 10 Million records in Teradata (as persistent value was not able to set).
QUESTION: The persistent values should be set as soon as the Session is Successful, independent on the status of its workflow. How to set persistent values at session level?
2) To Reset Persistent Value: Resetting of persistent value is needed whenever there is need to go back in the past to read data from the source system. Currently there are 2 ways to reset persistent values
A) At Informatica session level, the persistent value can be reset directly to only NULL value in the workflow manager.
OR
B) Hard coding the 'where clause' condition for insert_date and update_date in the Source-Qualifier for a mapping.
There are situations like during Disaster Recovery when we want to change the persistent value to be set in the past lets say 2 days ago (but not reset to NULL). Since we don’t want to touch mapping during production, so do you know if there are any other ways to set these parameters?
Thanks in advance.
Roopali Doshi