DSXchange

You'll have to manually create the file as 64BIT because the GUI does not allow you to specify 32BIT or 64BIT, it's 32BIT by default. Search the forum, there's a lot of history on this.

And free, too.

Instead of: cd /here/there/everywhere/scripts ./runmyscript.ksh You should just do /here/there/everywhere/scripts/runmyscript.ksh You should write scripts that can be executed from anywhere and have enough logic to handle not requiring a directory change. Beginner programmers do this, rather than fu...

Whack them. If the Client session is disconnected, then do a kill -15 else kill -9. You should do this regularly, because this problem has always existed with the product. Sometimes when viewing data the user kills the Designer rather than wait for that activity to finish. Those processes go nuts on...

Hence the bind issue, trying to stuff one datatype into a non-supported value for the driver. Well, sometimes the last shot is the one that works. We knew the SQL was the issue, just the datatypes when the connection is made and the SQL prepared was the issue. Don't worry about the datatype inconsis...

How do you know the problem is with the command stage? Are there other stages within this job doing things at the same time? If the job simply creates a directory at the opportune moment, why not use a Sequencer job to do the same thing rather than "gimmick" a row to trigger the command stage? How a...

or just fully qualify everything

There's two opinions as to what the original poster asked, and has subsequently failed to clarify: 1. log of the import action in the GUI client or 2. logfiles of the job designs. 1. There's no client-side log create during import to reflect failed jobs on import, unless you consider that dialog box...

How about some really simple SQL:

No, BIND means that the prepared SQL has to have aligned streaming data flowing into the BIND variables. If the amount of columns of streaming data doesn't match the number of BIND variables, you get BIND messages. That's why we've focused on the SQL.

In Oracle, truncate requires ownership of the table because a truncate is really an ALTER statement.

That possible issue could be a data type on one of your columns. The messages relate to the SQL, so that's about all that's left. I suspect tech support will get a call from you.

Nothing funny there. Are you using INSERT ROWS WITHOUT CLEARING as your SQL action? Any chance you're using the TRUNCATE then INSERT?

Okay, but what's the SQL statement, can we take a look at that?

dsjob is installed as part of the PC client. Just use it in a .bat script.

Use the Search facility, there's a lot of commentary on how to use one. For a date, check out macro DSJobStartTimestamp.