DSXchange

swadeep wrote:Main table is one database and error and log tables are in different database.

This concerns me. If they are truly in "different databases", wouldn't they require different connection details? I'm sure the stage is only asking for one. Is this even supported outside of DataStage?

I've always heard that it is a hard coded limit and required a "patch" from the vendor to change. Contact your official support provider and see what they suggest. One suggestion I would wager you'd hear would be to run fewer jobs at the same time if the "very busy" part is from ...

Since you marked this as a Server job question, I've moved it to the Server Edition forum. In an attempt to take this question seriously, first tell us what you have tried so far. I'd also be curious if this is a real problem you are facing as the problem definition, specifically the source & ta...

Things are typically written to "/tmp" because they are temporary in nature and that area should be cleared on a regular basis by outside processes. If you'd like to move them someplace else, that's fine, just make sure it has enough space, is dedicated to just 'temporary' processes and yo...

Client side. There's a good script here at Kim Duke's site. Scroll down for the Scripts.zip link which includes the DataStageBackup.bat file that many of us here have used.

You've already stated it's in the log as a Red / Fatal log message, yes? If so and the job doesn't abort, the next question should (IMHO) go to support.

An Oracle VARCHAR2 can support up to 4000, unless the version is very old.

Might be thinking of the OCI stage, from what I recall there was an option there to "treat warnings as fatal". Fatal errors should be by their very nature... well, fatal. May need to pass that one by support.

Two plus years and ~400 posts later we seem to have a new entity in the host known as karthi_gana. Welcome!

D'oh!

<searches for finger emoticon>

No worries... I may have been a bit thick lately.

Yup, we're sure.

Those of us old enough to have been using DataStage before there were Sequence jobs were writing the same thing as Server jobs for years... magical, special Server jobs with no stages on the canvas, but Server jobs none-the-less.

The server job in DataStage 7.5 hava a query: select * (fields) from table where date_field <= 'DD/MM/YYYY', the job works fine. For what it's worth, I would never have done it that way, either your original or your "fix". You are banking on defaults all lining up correctly for a string c...

Can you update the default, set a new one?

kennyapril wrote:This has to be done in a single job.

OK, I'll bite... why?