DSXchange

As Chuck noted, the display order is... not what most people expect. Keep looking, your Sequencer job is in there!

And, yes, what you are doing is perfectly fine.

I'm sorry, but is there a question in here somewhere? I could take a guess (mostly from the title of the thread) but I'd rather not.

Is it supported? I'd say 'no' based on what's in the most recent version (7.5) of the readme: This version of the product is intended for use on the following operating systems: HP HP-UX 11.00/11.11 HP/Compaq Tru64 5.1/5.1A/5.1B IBM AIX 5.1/5.2 Red Hat Linux Advanced Server 2.1/3.0 Sun Solaris 2.7/2...

Are both of the timestamps in the format you posted? If so, then you can simply compare them without having to anything special. It also seems that you've got your field delimiters backwards - you should be using a space for both the date portion and the time portion, but only take the time up to th...

Dennis, et. al. - On the off chance that you might not be aware, there have been some critical updates released for the phpBB software used here. These patch some "exploits" script kiddies out there have found that let them do nasty things to the boards using this software if they stumble across the...

Well, if you really need to do this in a DataStage job... Drop the first ODBC stage and simply start with a Transformer. It looks a little weird but works great for generating test data or in your case - a single row. You'll need to define a Stage Variable in it so that the job will compile, but oth...

That or .dsx required.

Peter - on the off chance you are still in search of information on this topic, you may want to check out Replicate1 from MIMIX... formerly called Omni Replicator. Should be able to handle your requirements, I believe.

It's exactly what it says it is - a unique constraint on your target table was "violated", meaning you tried to insert a unique record that already existed. The error will report the constraint name (not table name) that was violated, so you can use a tool like TOAD or SQL*Plus to check if you are n...

I'm in the same boat as Mike. Got burned by it "back in the day" and haven't used it since.

True, a 'pure' Reject Link will capture all rejects. However, that doesn't mean you can't capture just the database errors in a previous link. Create yet-another-link that comes after your target links but before the Reject Link (if you have one). Add a contraint that checks the DBMS return code of ...

Sorry, not a PX guru... just remember stuff I see posted. Someone else will have to help with the gory details. Or you could search through the forum again for those keywords, I doubt it's the first time the question has been asked.

Excellent! Exactly the information I was looking for... thanks for taking to time to post all that here. :D

This is a Server job question? You are in the wrong forum, technically.

The error means your OCI stage is not properly setup. Even if you use custom sql, you must put something in the Tablename property of the stage, even if it's not used.

I'd be curious as well... honestly. We're capturing job metrics but I'd really like to know what the value add is for this sudden spurt of interest in capturing logs.

Maybe I'm missing out on something!