DSXchange

I was wondering if Roy was under the weather or something, what with no Poll posted in quite some time. And me, I get the first vote! Not sure what will happen around here. Company was acquired and they've chosen a different tool for any future development on new projects. However. existent projects...

One way would be to click on the poster's name and in their profile you can 'find all posts' by them. They are sorted in reverse date order, so hopefully it would be somewhere near the top and easily recognizable.

It's not an issue that needs a patch. It is a well known permissions issue that a search would have turned up.

Sounds like your error is actually coming from the IWay Connector and not ODBC itself. So perhaps that's a limitation of that particular product or a setting there?

Typically one would write a custom routine to get the row count - either via a DSGetLinkInfo call or a check of the output file itself. You can then pass that row count back from the routine and use the value in a trigger:


Would be one approach.

A 'custom' trigger? That just means you provide the entire trigger expression, like 'A = B' or 'Stage.$JobStatus = DSJE.RANOK' or some such. Documented in the Help.

No, you are facing 'the same issue' precisely because you have 'not mentioned as key'. Mark the first two fields as keys and try it again! Or is that a typo in your post?

Timestamp in DataStage is fine for loading into an Oracle DATE. You've confused me - is the Oracle field a DATE or a TIMESTAMP? Not in the job in the database.

If you are loading a TIMESTAMP then a Char or VarChar in the job should be fine.

Get used to it, most of Ray's jokes fall squarely in the "I'll take Groaners for 1000, Alex" category.

Rerun as 'Right and Left Only'.

You've not only posted your problem in someone else's thread, but mixed a PX job problem in with a Server one. Best if you repost this in a new thread in the PX forum. That way we also know what your version number and O/S platform is, right now we'd have to guess.

Did you mark any fields as Keys in the Pivot stage? It looks like you should have three fields in the stage and the first two should be marked as keys. The third one, with a derivation of "version1,version2,version3,version4,version5", should not be a key field.

The answer depends on if you truly mean an Oracle TIMESTAMP field or are trying to populate an Oracle DATE field. The latter is supported natively by the OCI stages, the former is not. I'm assuming you really mean TIMESTAMP. Since you'll need to fall back on User Defined SQL to leverage the TO_TIMES...

You'll need a login, but once there you will find the patch under the Recommended Patches in the Software Updates for DataStage: User-defined SQL in Oracle OCI Stage ALL DataStage 7.5.1 05/26/2005 e73423_ALL_751.zip Description: Oracle OCI stage (ORAOCI9) incorrectly binds the lookup column values t...

Already been suggested - twice.