DSXchange

Well, it is supported - but only in a Sequence job. It's called the Execute Command stage, as you've noted, and would be the preferred method of accomplishing this. If you wanted to keep the sqlldr call in your Server job (which I would not recommend as it's not restartable there) you would need to ...

Why, when loading to an Oracle 7 database, of course. In other words, hardly ever any more. And as to why those other options are not supported, you'd have to ask IBM. Automatic mode doesn't use a control file or even create any logs, it communicates directly with the Oracle direct path loader under...

Define exactly what you mean by 'Oracle APIs' in this context.

Unfortunately, that's not supported. You'd either need to go Manual mode and edit the resulting control file on the fly or stick with your own scripting to solve the problem.

Or... if you've been keeping up on recent conversations, then perhaps just this:


Will automagically resolve to true or false, no 'if-then-else' required.

You'd have to call IBM support and ask them that, heck if I know. Or perhaps wait for Mr Ostic to stumble across this thread. You'd have a better chance of that if you posted this question in the proper forum - there *is* one specific to RTI / SOA questions, ya know.

DSguru2B wrote:No one made that assertion, True, but Delete being a DML command and Truncate being a DDL command, points towards that assertion.

You do know that Ray just made that part up, yes? SQL is SQL and it either needs a trailing semi-colon or it doesn't.

DSguru2B wrote:By specifying (') in the quote character box in seqential file stage properties.

Bzzzt... thanks for playing! Was an ODBC question, my friend, not a flat file question.

Welcome Aboard, matey! :D Did you try clicking on the 'Get SQLInfo' button on the General tab of the ODBC stage? That should query the database and set that option automatically for you based on what it finds the target needs. Failing that, you should be able to manually change the Quote character t...

People, Oracle will accept any date format - as long as the proper TO_DATE mask goes along with it. And unless you are a fan of user-defined sql places where it ain't needed, I'd suggest you stick with the format that matches the sql the stage will auto-generate.

The OCI stages require the 'Timestamp' datatype to be in the following format:

YYYY-MM-DD HH24:MI:SS

As can be seen by the sql the stage generates. If you don't need to time portion that a DATE field can carry, then just tack on a zero time to the end of your date: " 00:00:00".

Kim specifically said that seeing 'both counts' should mean they are not corrupt, so no need to 'revert back' unless you are just crazy bored and looking for hours of work.

Retry the reindex as noted... with exclusive access to DataStage.

Ah. In that one they never specified their exact DataStage version, perhaps it is a '7.5.2 versus The World' kind of thing. One would need to ask over there to be sure.

You can certainly delete any old ones but I wouldn't suggest doing so for any running jobs.

Ultramundane wrote:I am confused because of previous observations. Maybe a change in behaviour for DS752?

What 'previous observations'? Are you saying that it did not work this way before you upgraded? If that's the case, that's a question to pose to support I would think.