DSXchange

But we all know the suggestion was to use a specific PX stage.

Good Lord, Grasshopper - patience.

You'll need to find your own place to 'stick it' as there isn't one here. Yet. However, there are plenty of file sharing sites where you can upload it if you haven't got one of your own. I'm sure a google will turn up several choices.

The 'logs' are hashed files in the job's Project. So, no - you won't be able to access them outside of DataStage. And if you have so many errors that the log either becomes unwieldy or perhaps even corrupted you'll need to take special measures. I'd suggest you turn off the automatic 'Refresh' optio...

No clue if somewhere in that morass of an IBM site you can find documentation for 7.5.x but if it helps at all here's a link to the 8.0 docs:

http://www-1.ibm.com/support/docview.ws ... 03&rs=2321

Note: these are not necessarily free. Some are, some aren't. [shrug]

Now i want that both the rejected files to be collected in one file. So i tried putting first reject file in overwrite mode and the second in append mode. Finally i get a file which has records rejected due to constraint only thats second file but no records from first reject file. Sequential files...

You can either reinvent the wheel or download the wheel, your choice.

ETLStats

'Nuff said.

Aha! :D

Glad you got it sorted out.

So... you don't have the SOA Edition / RTI?

I'm a little lost on how you can 'schedule ETL jobs as Web services', too.

sudeepmantri wrote:Well if you are not comfortable with the routines, there is one more option of column generator.

In a Server job?

The only reason I mentioned the exit code was this snippet: Command<3> = 'EXIT 0;' You'll always get the exit code of sqlplus itself, your error shows that you couldn't launch / connect to it cleanly. I was concerned about the times where you connect to and exit from sqlplus just fine but the sql yo...

Why would you both mark this as and post it in the Server forum?


(waves to Ray)

I counsel... patience.

Upgrade. There's only a couple of 'work arounds' in that version - either stop using parameters and hard-code everything or replace the Execute Command stage with a Routine Activity stage that executes the command using DSExecute. You'll have full control over the parameters there.

Welcome. Google is a wonderful thing, turned this up for me lickety split:

Isolation Levels

Next time, please try to pick a more descriptive and appropriate title for your posts.

I'd suggest a couple of additional logging statements to see if that helps. Put in calls to DSLogInfo for things like the Command just before you execute it or anything else you'd like to confirm. I'd also try removing the "-S" option temporarily and see if that is hiding something useful. I persona...