DSXchange

Do the two VERIFY.SQL using the pathname and the FIX option and, if necessary, add entries to UV.ACCOUNT to describe any project that is not described there. After that you should have two projects. Then you can use both, or delete one from Administrator client. As usual, take a backup (a UNIX copy)...

As has so often been explained, we at DSXchange simply don't do "urgent". If it is urgent, as you say, sign up for premium service with your support provider, and learn how expensive "urgent" is. DSXchange is a community of volunteers who post as and when they can, and then only if they have someth...

Yes.

Search the forum, you are far from the first to encounter this error. Posting the exact and complete error message would have been useful as well.

From that, I deduce that "someone" made an operating system copy of the project, hence the "duplicate schema" reference. I presume that, when you try to delete the obsolete project, that you get an error. Is that the case? If so, what is that error? I think that this is a recoverable situation, thou...

You have NOT sourced the dsenv file.

If you had, that line in your script would read or

More useful would be to post (or even just to examine) that part of the generated OSH relating to the lookup stage and its inputs and output record schemata.

I don't suppose you'd consider "lots" to be an adequate answer? How about 1.0 and 1.5.2 ? Seriously, though, there is a "what's new in this release" that comes out with each release. You should have one for your current release somewhere at your site. For earlier versions you may have some luck traw...

Before you go any farther, try VERIFY.SQL specifying the pathname of the schema, rather than its name. For example

Others also have data obfuscation routines available. But is that what you mean by "masking"?

That's a feasible configuration file for a four CPU machine, but note that processing nodes are not related to CPUs. For example if monitoring indicates that no CPU is exercised to more than 50% of its capacity, then an eight node configuration file would be just as feasible. For smaller jobs you mi...

Craig means, of course, that your DBA can tell you, not that your DBA is the cause of the problem!

I suspect you've uncovered a bug in the client. Involve your support provider.

Welcome aboard.

Can you be more specific about what you mean by "masking"?