DSXchange

hitmanthesilentassasin wrote:I am having trouble with basic transformer timestamp columns.

What kind of problem, exactly? Sometimes best to start with the problem rather than your perceived solution to it.

i need to use Java, no other way. I doubt that very much. As do I. We're more than happy to help with DataStage issues here but for "batch read write in java code" help you should be posting elsewhere. By that I mean a forum that specifically supports Java developers. Once it is developed...

That's not possible as it becomes just a string rather than SQL code to execute when bound into the existing SQL.

Use CHAR columns rather than VARCHAR columns. That or explicitly pad them yourself using Right().

Nope. And that's primarily because there really isn't a reason for a Server job to log warnings... unless it has a 'real' problem. I've written literally thousands over the years and they would run night after night without issue. If you have specific warnings that you're not sure how to deal with, ...

Note that there is also a FAQ posting on the subject.

And will also require a static source.

Was curious how you are doing on this...

Sort in the database and then add a Sort stage set to "Don't sort already sorted'.

ps. What is your idle timeout?

I'm a little lost with your requirement and why anything you are doing would require Java. What's your database? Why do you think you need Java? DataStage can load several files at once so you don't need to load each new file that are being generated "every minute" individually. If you rea...

Peoples, that's not a "workaround" that's a RESOLUTION. Changed.

India2000 wrote:Is it required to create and call a separate seq job for reject notification that runs every 4 hrs?

A separate something, yes.

Raftsman wrote:I guess I need to clarify information in more detail, my apologies.

No, not really.

Contact your official support provider for details. All we know is it couldn't allocate 160MB of memory but I couldn't for certain say where. Suspect the ETL server rather than the database. Was this a one time error?

Of course, Ray is generally a pretty good guesser.