DSXchange

The important distinction is whether that period is present in the actual data, hence the request to check it via some mechanism other than the data viewer. The viewer is known to apply formats to the data it shows, its purpose is more about checking the actual value of a data element rather than it...

Or leave off the redirection and use that methodology in the Filter option of the stage.

Perhaps this might help: viewtopic.php?p=402895

There no special list somewhere, those details are stored with each job. You only option is to iterate through a list of all jobs in the project and check, one by one, for whatever condition it is you are looking for.

Yes. As documented.

Another impossible requirement.

ASAP help comes from your official support provider, not from an all volunteer forum where people post when and if they can. Not to mention that typically the quickest way to get help is self service, have you tried searching the forums for a unique portion of that error message? An exact search for...

What's the resolution? If you just meant "never mind" let me know and I'll delete this topic.

kduke wrote:I thought the job locks no longer stop an export in version 8.

That could very well be but it's not something I recall being posted here before. Can anyone confirm or deny?

Moved thread and renamed subject to something more meaningful.

Me, I'd be curious what exactly "8 mins to initialize the next job" means and why that would be happening.

1. Well, your proc is being called now, something it wasn't doing before so the correction to the type helped. Now you've got other errors to work through. The 'invalid characters' errors are fairly common and you may find some answers by searching the forums here but since all of your errors seem t...

1. Well, your proc is being called now, something it wasn't doing before so the correction to the type helped. Now you've got other errors to work through. The 'invalid characters' errors are fairly common and you may find some answers by searching the forums here but since all of your errors seem t...

Then your trigger expression is correct as long as you are using the stage name as I noted.

The log hashed file was corrupted in that other post, hence the request from Ray for them to run tests on it. You've got a different issue. Let's start with this - is there an "RT_BP6487.O" directory in the project?

Hmmm... the OCI stage can, don't recall that as a feature of the ODBC stage.