DSXchange

It's a client problem.

Windows XP? Service Pack 2 installed? If so, get the patch from the eServices website.

Or perhaps... StringToDecimal

Yes, you would need to use an Oracle user which has the permissions needed to bulk load into that table.

'Before Job' is a bit of misnomer as the job has actually started at that point. Regardless, a job cannot set its own parameter values - it's too late at that point. Your controlling process, whatever actually runs the job, that process needs to do all of the parameter setting.

If you haven't done so already, Ross - go back and edit your original post. Many people here don't seem to realize you can do that.

That... doesn't make a whole lot of sense. First comment would be that your QA project should hold 'read only' jobs and be fed from Version Control just like production. Dev should be the only project where jobs can be 'worked on'. Dev jobs ready for testing are 'Initialized' into Version Control an...

No, but the first thing to try would be to reindex the project. Search the forums for DS.REINDEX (try an 'exact' match) for many discussions on the subject.

And all I'm trying to say is - unless something has changed - that "Reject Event" *is* a warning - marked yellow and causing your jobs to finish with a Finished (see log) status.

Dat's all.

Still curious about the other potential issue...

I'm pretty sure we don't get a Warning event though. My server is down at the moment so I cannot check. I think the job just completes with Finished (see log) status, which we propagate back to the calling Sequence as a Warning. A status of 'Finished (see log)' means there are warnings in the job l...

If I do programming I need to check for uncompiled jobs and have to compile and run them.(How to go about it ?) I would seriously reconsider this point. If a job is uncompiled there's no way I'm going to assume I can simply compile and run it... who know's why it is in that state? Now, aborted jobs...

Generally doesn't mean anything, as it's not typically a problem with the sql itself - more of a issue with how it plays in OCI and how well it matches to the column definitions. Speaking of which, I would suggest that you not do a 'select *' when pulling data from a database. You are at the mercy o...

I'm assuming those are Oracle DATE fields, but I'm not sure why you would get that particular error. How are the columns defined in the stage? If you have the DATE fields as 'Date' try switching them to 'Timestamp'. Also try ditching the TO_CHAR function as it really shouldn't be needed. If your DAT...

Vincent has posted in this thread information on getting them to work in 7.1. There's also something here where I posted a snippet from the 7.5.1 readme which talks about changes made to the functionality in the latest release. Hope that helps.

Thanks for posting that. Always good when a searcher can find questions and answers all in one post.