DSXchange

Just convert it to day-month-year format and then strip your delimiter with something like Convert().

So, what is your 'workaround'?

What 7.x version are you running? There's definitely a 'Move to...' option on the File menu and right-hand panel right-click menu, I have no idea why it wouldn't be there for you unless your version is old - though I thought that option has always been there. And no, there's no setting that I've eve...

You certainly should be able to, either by dragging or by the right-click 'Move to...' option. Neither works for you?

Use the Manager.

It should support the 'Windows standard' control-click and shift-click selection methods, do those not work well enough for you for this?

Actually, I don't believe DataStage ships with any Teradata ODBC drivers. Did you purchase some? Why not use the native Teradata stages?

Has nothing to do with RAC, so put that out of your mind. Yes, multiple nodes create multiple connections and locks so you need to be careful how your data is partitioned to avoid situations like that. Does the issue not occur if you run the jobs on 1 node only?

priyadarshikunal wrote:I don't think its one of the datastage inbuilt routines.

It's not.

It's more about the hardware than the O/S IMHO and I don't see how going from three servers to one is going to get 'better' performance unless the new server is a beast.

Wasn't meant to be. :( Putting an issue in your own post let's us not only track it without going off on tangential discussions in other people's topics but also means the Subject can match the topic at hand, we have your particulars for job type and DataStage version plus you can mark the post as '...

Sounds like you may not have configured the connection correctly. Can you post both the uvodbc.config and .odbc.ini entries you created?

Don't know SQL Server but what is the data type of the target column in the actual table? (not the job)

Either in a Sequence job or 'before job', check using one of the methods posted and then 'throw the error'. That could mean calling DSLogWarn or DSLogFatal or just setting the return status to a non-zero value.

The amount of work varies depending on how it was created. Pathed? Just copy it. Account-based? Create a VOC record using SETFILE (or a 'do nothing' job) and then copy it.