DSXchange

How are you 'reading' it? That stage should support parameters - the Folder stage does for example.

What happens when you simply do not check/enable the 'Generate procedure call' option on the Stage/Syntax tab? Create the anonymous block yourself the way it needs to be to call this SP and let us know the result.

I'm not really following what your problem is any more. How many IN parameters does the SP need? When you 'Generate' the sql via the stage, from what I recall it will automatically generate code with every column defined in your stage passed to the SP in the anonymous block it builds - so they need ...

This is all fine and dandy. However, the answer is clear - there cannot repeat can not be duplicate key values in a hashed file. Period. End of story. In spite of what has been posted as to how the records may look the same to the naked eye, there must be differences between them. Period. End of sto...

When the job aborts, Reset it from the Director and give us the contents of a log entry labelled 'From previous run...' if it shows up. Also check the size of your hashed file directory - is either the DATA.30 or OVER.30 file over 2GB in size? Lastly, have you enabled the 'write caching' option in t...

Sure - don't send any rows down the link.

All you need is a transformer and an OCI stage. Put a stage variable in the transformer so the compiler won't beef. Use a constraint of @FALSE so no rows go down the link. When the job runs, the only thing that will happen is the truncate. Done.

You need to upgrade to the 'latest release' for your platform, at which point the stage will support Oracle, DB2 and Sybase.

kcbland wrote:I hate a horked up project.

Even worse - with all projects horked up you've got what we call a horkestra.

Yes, running the REINDEX command with users connected will hork things up and make all jobs disappear. Ensure all users are disconnected (bounce things if you need to) and then rerun - you should be fine.

What about the last row? Better to sort descending and take the first occurance.

I don't believe this is a bug but rather a known limitation of distributed hashed files. You cannot cache them - individual parts, yes - but the whole, no. Should be documented somewhere...

It is confusing - but doesn't it all come down to maintaining a Type 2 SCD at the end of the day?

Searching for 'failover' got 27 hits, not all relevant of course, but ones like this one is. It discusses failover, something I was able to help setup at one site. There's nothing built into DataStage to make it qualify as 'Highly Available' or provide anything like transparent failover. And no addi...

You've gotten two different answers, Sam, because you haven't said if you are trying to read a file with header and trailer records or are trying to create one.

Be in that directory when you launch 'dssh' - it will prompt you for the rest.