DSXchange

If you can, delete your second post. It's kind of... messed up and doesn't look to add anything that's not already in the first one. You need to put some conditional logic around the setting of your stage variables if there are null values in there you want to 'skip'. Try this for the derivation of ...

What he said.

In addition, I'd suggest doing a search of this forum for the word 'loop' or 'looping'. You'll find a number of posts from people in the same (or at least a very similar) boat, along with quite a bit of discussion on the details.

It doesn't have anything to do with the database iteself. Wire Drivers are a type of ODBC connection that do not require client libaries. DataDirect has a nice little page here that should help explain the difference.

Unless they are 'wire' drivers, ODBC typically (always?) needs the client to piggy-back over - regardless of database.

(the process I went thru: selected jobs in dev, performed get dependant..., initialized the batch, selected the batch from VC opened test project and promoted the batch as compile + read only) Roy, your process sounds fine and I don't believe your issue should be related to Version Control. Can you...

Welcome. :D This is the kind of thing I'd suggest you report to Ascential support. Smells like a bug to me and, if so, they would need to know about it and be able to recreate it for there to be a chance that they can fix it. As an alternative, is there any way for you to shorten the where clause? P...

There is an init.ora parameter that enables SERIALIZABLE transactions and which must be set before you have any hope of this option working correctly. Other than that... could be a number of things.

Yes, this is a result of your Transaction Isolation setting. Change it back to the default of 'Read Commited'. Going to a command line and issuing 'oerr ORA 08177' may help explain what's going on and then again it may not. Many of the error message descriptions there are blank, for some silly reaso...

my unix admin says its a big maintaince issue if i want to call or use shell scripts from a job in server..... Huh? I'm unsure what the 'big maintenance issue' would be. This is a very common thing - server jobs leveraging shell scripts. We routinely use scripts to manipulate files, do bulk loads, ...

You can also do a couple of things from the Director. 1. Turn off the display of Categories. It may take awhile to show all jobs in a large project with this option off, but it will help find what you are looking for. You may want to dial up the refresh interval before you do this so it doesn't try ...

How are you stopping the job? You need to do it in a way that causes the job to end 'abnormally' so the commit does not happen. I think you can do that from the command line but I don't know the syntax off the top of my head. I'll double-check when I get into the office. One sure fire way is to tack...

ray.wurlod wrote:If you want a detailed reply, you might be better off posting on ADN.

And this was...? Why go there when you can get the Full Wurlod right here?

I was wondering if it was something along those lines. However, I expected it to be more of a static list, not something it monitored over time - but as long as we know the darn thing works....

Yah... who answers the Answerer?

Why would a simple search for 'before' or 'after' fail to return any results unless done as an 'Exact Match'?

Interestingly, a search for 'before-job' finds hits but says it will highlight 'beforejob' and therefor doesn't seem to highlight anything.

Something seems amiss.