DSXchange

Maybe the author of whatever post you stripped this from? Since you didn't include that information or a link back to the original post, who knows? Your problem is going to be the fact that any comprehensive post on the subject will be a Premium one nowadays, like this one. You could check the FAQ o...

I think you're just asking for more work if you do that, Roy. There will be even more chances for people to put things in the 'wrong' place.

Exactly, between the Loop stages and the User Variables stage you should be all set.

I haven't had any problems like that... can you post the entire text of the error message? Also curious how you managed to convert that SQL Server database to Oracle.

Yes.

The biggest hurdle in XML generation seems to be the XPath statements needed. Best Practice is to import the metadata for your target XML and let DataStage generate it for you automatically. Do you have or can you get (or generate) an xsd for this? The other big hurdle is proper designation of the r...

Have you tried it as 'dsadm', Roy?

I've got one protected project and can swear I could compile there. You may not be able to open a job in the Designer and compile, but may have to go the Manager / Multi Job Compiler route - don't recall.

... and if you upgrade to 7.5.x of DataStage you'll find they no longer bother to log this message.

not real elegant, but it works. Yes, that's what you have to do. The OCI stage doesn't natively support the Oracle TIMESTAMP datatype, only DATE, so you need to wrap it up yourself with an appropriate 'TO_TIMESTAMP' function call that matches the way the TIMESTAMP was declared in the target table. ...

ray.wurlod wrote:Can't you simply use the Business Manager role to allow this?

Yes. The 'Production Manager' role, technically. Also 'dsadm' or the equivalent 'administrative' user.

poorna_76 wrote:Is there a way we can define a generic ODBC connection for different Databases on the same server, so that we can import table definitions for all the tables in all databases on that Server, using the same DSN?

No that I'm aware of.

Depends on your version of DataStage. With 7.5.x the OCI stage is certified for 10g. Before that (since it is not) you're best to stick with using a 9i client to access the 10g database. This could mean no change in the dsenv file or your jobs if you still have the 9i client installed.

Sounds like you've put the 64bit Oracle library in your shared library path in the dsenv file. Change it to the 32bit library (usually lib32 instead of just lib), then stop and restart DataStage.

Have you checked the help for the stage? There is a good explanation of how the Error Codes tab works there. If you've imported the metadata for the SP, you should be able to use the Load button to bring your return codes in automatically. Otherwise just type them in. One thing isn't clear to me is ...

Yes, just keep 'Adding to schedule' with unique Invocation IDs.