DSXchange

You get this when you go to insert the final 'product' of your manipulations into Oracle. What does your field's value look like then? What does your sql's date mask say? The two don't match.

You've already gotten them. Drop the degree of parallelism down or be prepared for it to occasionally crater if too many other parallel queries have been requested by other folks/jobs at the same time.

Discuss that with your DBA. It's not a DataStage issue.

Ouch... there's more than one place to change that, doing it only in DS_JOBS blew your RI in the project. First off, I'd suggest you undo that change to get everything back... However, with all the other monkey shines like reindexing, I wonder if that is even possible anymore. I'm not sure what this...

You said 'both routines are executing fine'... what is making you say it is not differentiating between argument values? Any issue here is either in the way you are calling the routine or how the routine itself is written, otherwise they 'work fine'. You'd need to provide specific examples of either...

it sounds like this 7.1 bug means there's no way of getting it compiled once there. Am I right in this? From what I recall, yes - but you really should check to see for yourself as we skipped your particular version. Does the Multi-Job Compiler allow you to compile read only jobs? You are correct i...

Actually, a reinstall of the client is pretty quick and painless. I'd suggest you give that a try first and then we can burn some braincells if that doesn't work.

No ideas off the top of my head, but I think that you should explain exactly what this means to help set the scene properly:

We recently implemented proper user groups/privileges on our DS development environment

Try it again, Mr Guru seems to have fixed it. It didn't work for me earlier, either, asked me to log in - classic example of what happens when you link from your own search results instead of straight to the topic. Works now.

If know the original post says 'Foxpro' but .dbf files are DBase files AFAIK and those have been around for ages. As noted, should be perfectly do-able.

You could define it as a numeric datatype, which would automagically do that for you, or you could check out the FMT function.

I believe this is a known bug with your version. They've since corrected it in 7.5.x so that your 'dsadm' user can promote into a Protected project. In the meantime, I think the workaround is as you've noted - to temporarily lower your shields and hope no-one notices the momentary lapse in protectio...

Neither one is 'better', the answer depends on what order you need them sorted in downstream from there.

How is your sequential metadata setup? Looks like you are generating XML and then asking it to be read and written as a sequential file. You'll need to be careful there and define a single large varchar column, I would think.

How is this any different from this post? Hint- it's not and was asked and answered in the other thread.