DSXchange

You need to check the success or failure of the lookup, not any kind of equality test. A lookup failure returns NULL values which will cause your contraints to always fail. Test for that instead.

Which is the better approach? To store it in CSV file or Flat file or delimited file? Everything you've mentioned is a "flat file" and a "csv" file is one flavor of a delimited flat file, it just means a specific delimiter - a comma. So... six of one. Your other option is a data...

Pick one and then "manually" build the section of the file with the other delimiter as a single varchar field.

Why would you "need" to remove that? It's perfectly valid XML.

I would have expected that the Column Import stage will do a search by column name in the source file header, and if found, would correctly associate the corresponding values Bad expectation, I'm afraid. This isn't a database table we're talking about, it is a sequential file where everything is ha...

Now was it "not helpful"? Did you try enclosing the password in quotes as it noted?

It's documented, so suggest you start here: Multiple job invocations section in the Director Client Guide pdf.

vam wrote:This parameter is actually defined at project level...

Can you be more specific about this? Where/how is it defined? How was it 'migrated' to the new environment?

Different issue now. And you haven't explained the source or nature of this "lookup column" in your constraint. How is it derived?

Sreenivasulu wrote:In DS Server there is a file called dstemplate.txt (not the exact name) which also needs to be updated

Needs to be updated? No, not typically. Can be, sure, but generally works fine out of the box on UNIX provided sendmail is alive and working on the box.

Someone does, yes. That would typically be whomever administers that system. Ask your SysAdmin.

svhari76 wrote:Any thoughts what i am doing wrong here?

Not searching the forum?

viewtopic.php?t=87169

dheerajatreya wrote:

chulett wrote:You posted in the Server forum and marked the Job Type as Parallel - which is correct?

This is in parallel version... Sorry abt that..

No problem, I moved it.

You posted in the Server forum and marked the Job Type as Parallel - which is correct?

Ah... it does need to be 1 to capture them reliably, however it seems like it should still have 'worked' after a fashion when it is set higher. From what I recall, Oracle would report the right number but put the wrong record in the reject file. It also depended on if your total row count exceeded t...