DSXchange

gssr wrote:see the log file for the Oracle specific message

The error will be in the log, hence the message.

So... this issue is specific to using parameter sets rather than 'regular' parameters? And by 'lost' you mean they are not passed, the job always takes the default value - is that correct?

In my mind, it would be easier to work with a .dsx export.

Hmmm... why is this not a job parameter?

OK, then you know what to do.

Yes.

There are 22 other posts on issus with SMALLDATETIME, did none of them help?

Search for "failed to register this user for sql" here and see if any of the previous posts on that same subject help.

Or that, the equivalent of using the DIGITS transform.

[sigh] So... after resetting, you do not have a log entry that says "From previous run..."?

Good to know, thanks for posting that.

Save the re-index for when no-one can see jobs in the Repository.

Didn't ask you to run the job again, just Reset it and see if the log entry I mentioned gets added to the log.

No, as that just means the job blew up. Got any more details? Also try Resetting the job and post the 'From previous run...' information that adds to the log, if any.

No, there's no way to do it at the category level. So you have to create the new category, copy the contents over you want at the job level and then delete the old category once it's empty. Still better than one at a time, however.

Any chance you have some non-numeric characters in the field? Based on the name, maybe a "%"?