DSXchange

Ah, so that's the ticket... thanks. Now I see why you might want to Raise() something to convert the delimiters 'to the next higher-level delimiter'.

You're deleting 30M out of how many total rows? May be more efficient to rebuild the table with just what you want to keep if the percentage is high enough.

Things like the concatenation operator (obviously you can concatenate) or functions are not supported in the Filename property of the Sequential file stage. So, you have a couple of options as I see it... First, is this parameter in this job used in multiple places or just in the filename? If the la...

Nope, no such. The 'Oracle bulk loader' which leverages sqlldr does not support any kind of row update capability. Hence the name 'bulk loader'. You could use Oracle's MERGE or plain sql in the OCI stage, however.

OK, make that two people.

Wow... this is not a minor task you are attempting to undertake, especially for someone that ranks themselves 'new to the product'. There's no document or URL for anything like this, so what you'd need to do is export some simple jobs from the Manager to dsx or xml format and start from there. Learn...

Gopinath wrote:In one of my existing Jobs, we are using a SQL query to fetch records from different tables. One of the Join condition used is LIKE option between two columns from two different tables.

That's what they are doing now. For some reason there's a need to change that.

Does the webservice need xml? Doesn't seem like it from what you've said so far.

And in Server Speak, 'join stage' means hashed file stage.

... as long as you understand that 'for whole project level' means 'make it the default in future sequence jobs'. That will not affect any current jobs.

It can happen infrequently when you use the 'Delete before' option. As Ray noted, there can be situations where it can't delete everything completely and you get errors of this nature.

It's a pretty low-level OCI code error and from googling around there is a bug in the 10.2.0.1 version of the client that causes this. No mention of CLOBs that I saw.

That's an Oracle package, so any SQL can leverage it. Doesn't really help with a BLOB though, more for CLOBs from what I've seen.

ps. If your 'app' doesn't support it, use another tool that does to verify your BLOB is transferring intact. If you're unsure, ask your DBA.

Sorry, but that's got nothing to do with this particular problem.

Thanks. I'll give those a spin.

One thing to note - I'd originally tried angle-bracket notation after reading the multi-valued fields but it returned the entire field to me, not the first entry. I'll give it another spin, make sure I didn't do something stoopie but wanted to mention that.