DSXchange

The first thing you missed was starting your own post so the resolution of your issue can be tracked. I've split you out and linked back to the original thread. Add the missing details of your issue, we have no idea what your job design / source / target / NLS charactersets in play are...

Excellent news! Since this topic is resolved, please mark it as such using the button on the top of the page and then start a new thread for your other questions.

Any luck with this Nathan?

Not sure what logic you'd need that's not in the documentation: Modify stage: Options category: Specification This is a statement with one of the following the forms: * DROP columnname [, columnname] * KEEP columnname [, columnname] * new_columnname [:new_type] = [explicit_conversion_function] old_c...

Does parameter within parameter not work? Correct - it does not work. You would need to build the parameter string with the values substituted before passing it as a parameter. That or just pass the parameters as parameters and bind them into existing SQL. Does the source SQL really need to be 'dyn...

Those two formats are identical.

As noted, you're just not sorting it properly to match your stated requirements.

Your date mask matches the incoming string so to me that leaves your substring as suspect. You said:

vinodkumards wrote:Inside the SP,

W_Date :=to_date(substr(in_Rq,m,n),'yyyy-mm-dd')

where m,n are the xml tag positions

M would be the start position but N would be the string length, not the ending position.

Sync_GetTime -- Server Stage Load_Date (Sequential File) -> Set_Stage_Variable (Transformer) -> Save_Backup (Sequential File) I have the final sequential file to keep the transformer happy. Within the transformer I have a stage variable that is set by the input from the first sequential file. There...

You don't really need a UserVariable stage for this and it should be rather straight-forward if you are certain you are setting USERSTATUS properly. Your Sequence job should have two Job Activity stages in it, one to run the Server job that puts the value into USERSTATUS and then a following job tha...

Thanks for coming back and posting your solution. Not surprised that it was an NLS issue as there really isn't anything 'special' about the characters you mentioned.

Do you have a 'performance problem' right now? Sure, a Modify stage can be used to 'add' columns. And FYI - you haven't stated what your target is.

Ah... ok. Still doesn't change my answer. Don't let that stop others from chiming in however!

No, there isn't.

And adding in the fact that you are source a CLOB and targeting a BLOB (or even if vice versa) reinforces my advice to use another tool for this. At least it reinforces it in my mind.

Is it working for you right now? I don't see any burning reason to try to eliminate anything if it is.