DSXchange

Well... not attachments of any kind, but it should support images as long as they are hosted somewhere accessable. So it would be possible (and I seem to recall at least one person actually doing this here) to take a screen print of a job, save it as a .jpg or .bmp (etc) and putting it on an image h...

bryan wrote:But I never saw any additional info to debug..its just blank with just the message "From Previous Run". Jobs design varies.

Did you try double-clicking on the log entry? They usually aren't blank, it's just that you need to double-click on them to see all of the gory details.

How are you running these scheduled jobs? The concept of master sequencers jobs needing to 'reset or recompiled' manually before they can be run again can be handled by a wrapper script around the dsjob command. As to your main question, I've never actually done this in Production but that is my und...

jzparad wrote:I'm trying to determine if it's worth the effort of exporting, rebuilding and importing the project.

Nope, not in my mind. As far as I know all it does is create three (or four?) special hash files in the project to track things and add a routine or two, other than that... [shrug]

First off, you can't have more than one Input link to a transformer. Secondly, that's exactly what @OUTROWNUM does - track the number of output records per link. That's what I assumed the OP meant by "I want the value to be assigned based on the number of input rows from one link". Assuming "input f...

Yup, pretty standard practice. If done properly, the hash will improve performance. Build the hash based on the records to be processed, not everything in the target for starters. You may even be able to 'kick it up a notch' by only using the OCI stage for the updates and bulk loading (via sqlldr) t...

snassimr wrote:I want that the value be assigned based on number of input rows from one link

Then use @OUTROWNUM instead.

That's what I was afraid of. The "X then Y" update actions are the slowest performing actions you can use, especially if you pick the wrong one. To run the 'else' action, the first action must fail so you are doing double work for those. To me, those two update actions are to be avoided at all costs...

You could also use a Unix utility like crontab to schedule it for multiple times. As noted, using the DataStage 'scheduler' does put your job into cron (or at for a one-off) on a UNIX server. On a Windows server, it is building an AT entry for you. No reason to do that yourself, though you may find...

Basically, the answer to your question is 'no'. However, rather than hijack this thread (since your question isn't answered by scheduling a job multiple times) please repost your question as a new topic. This way we can help you with your particular issue without taking this topic off into the weeds...

Do not consider using any kind of a 'random' number generator for surrogate key handling. Any perceived perfomance gain from doing so will quickly degenerate as the size of your target table grows. The methodologies Arnd mentions are the tried-and-true ones and have been discussed to death here, so ...

Talk to your DBA first and see if you even have permissions to drop and rebuild them. You'd need scripts to do that for you in the long run, scripts that could be run before and after job or even before and after stage. Some of the considerations for this isn't the number of rows you are loading but...

There's been quite a few posts on the subject of handling Oracle DATE fields that a search will turn up. This one for example. Read throught it, search for some other posts (oracle and timestamp as keywords seemed to work well ) and then let us know if you have any other questions.

Force it to use an ASCII transfer rather than relying on the auto option. Then it will 'always' handle the difference in the line terminators correctly.

A Sequencer is just another DataStage job, so you run them via the Job Activity stage like any other. You have to propogate your sub-sequencer errors up to the parent sequencer via one of the 'Utility' routines - UtilityWarnToLog for instance - when any job in a sub-sequencer fails. The warning or f...