DSXchange

You can't import over read-only objects. So I guess you're setting them to read and then trying the import. I've never done this, so I can't help much other than to say make sure your dsx file also shows them as read. Are they even in your dsx file?

Why use the Merge and not the Join?

What's the error message?

Try using tnsping and your dsn entry name. If that doesn't resolve, use the fully qualified name.

Either change your datatype in the stage to VARCHAR or use ICONV on date columns because this stupid stage requires DS BASIC internal date values when the datatype is DATE.

Feel free to use the Integration forum for such topics.

Not only will they sell you the software with the security leaks, they'll sell a service to detect the leaks, and then they'll tell you wait for the next service pack to fix the leaks, which in turn adds newer leaks, and the cycle keeps repeating. Meanwhile everything on that machine is broken becau...

kcbland, ODBC Enterprise stage works when we are loading from an UNIX box to SQL Server on Windows. There are several posts in this forum about it. Okay, maybe I'm totally wrong here, but my quick read of every post with ODBC and ENTERPRISE in it never talked about someone using the WRITE loading m...

Why aren't you using UPSERT? It's a Unix box talking to a Windoze box, how is a bulk load supposed to work?

cfuller wrote:Thanks for the prompt response.
:D

Benefits of being a Premium (and Charter) Member

Hmmm. The internal file corruption suggests one of the files the job uses had an internal problem. My guess is maybe your project had a disk space issue on its file system while the job was running. The problem could be in the RT_CONFIG, RT_STATUS, or RT_LOG file associated to the job. The easiest w...

Nope. Not using Server. You could consider writing a generator script that writes a .dsx file, after considerable time figuring out the structure of the file. Then, import the job and you're ready to go.

Each constraint is ALWAYS evaluated for every source row. Each stage variable is evaluated for every source row. If you have multiple output links, it makes sense to use a stage variable to hold a result if that result is needed in more than one constraint. If you have one output link, there should ...

With Inter-processing checked on the job properties, the Transformer stage will essentially achieve the same effect. Remove the IPC stages and scratch your head one last time. Folks do strange things.

Only mechanism I know is to recompile the base job.