DSXchange

Not sure where anyone said that it didn't but yes - Oracle has a COALESCE function and as people noted, it returns the first non-null value in a list of values.

The loop will do whatever you code it to do. If it needs to wait, code in a routine using the 'sleep' function.

I ran your query in Toad and got your results. Ran the same thing in OCI View Data and my results matched the sort order from Toad.

What are your settings for NLS_COMP and NLS_SORT?

Still... you can only use valid values in any job parameter there, it doesn't allow you to magically make one up. Assuming you are actually on UNIX as noted, and you've managed to be accessing SQL Server all along, you could use the ODBC stage to call the stored procedure. Or consider taking whateve...

Thanks for the more clearly... was pretty sure but not 100% Wurlod proof sure.

Clear it out, let us know.

Again, a search is the first suggested path you should take. 18 matches on this one.

I got 14 matches when I searched for "Non-pipe (or non-virtual data set) with .v in its name". Did none of them help?

Not that I am aware of.

With the server shut down? I don't believe that would be a problem. You may still have to manually clear any shared memory segments and 'hung' ports that remain before it will restart, however.

If the site hosts a web service that could deliver that data, then yes. Otherwise (AFAIK) you'd need to find some other way to retrieve that and either leverage it via an External Source stage or just land the data and process it from there like 'normal'.

Why not just read their message and stop sending the parameters it is telling you are not being used? Better solution.

That's not a 'failure' but rather just informational. It will tell you things like the 'server' param isn't used, which is normal for UNIX. Those messages can be ignored or you can remove the offending parameters from your call.

If you just need to know the differences when the keys match, then no. Two jobs, perhaps, if you also needed to report where a key did not exist in the other table. Job1 both situations, Job2 just the missing from the other 'direction'.

Technically, you could do the comparison all in Oracle with a fugly query, case statements, all columns, derived change flags, etc etc.