DSXchange

kcbland wrote:These types of structured design techniques yield multiples of improvements.

And run counter to a 'Best Practices' document I was just sent from IBM. I was flumoxed to read that landing data in Server jobs was frowned upon and specifically mentioned as a 'Thou Shall Not'.

Just wanted to check as there is a "classic" bug where the job retains the proper initialization name but the contents could be a completely different job. If the parasite job is from another category, then it will promote to that other category and look like it didn't promote when you look in the "...

For grins, open the job that is inside the VERSION project and see if it is the same job you initialized.

Working fine for me.

Details, man! Which plug-in are you importing through? What client version is installed on your server? Source database version?

ray.wurlod wrote:It's free, and worth every penny.

Damning with faint praise?

Bala R wrote:Hi,
Can we set the file name in the 'Wait for file activity' in job sequence as a parameter.

Sure, very common approach.

Yes, but that's what got you into trouble in the first place.

Version Control is a client tool. The Version Control repository(s) live on your server, typically your development server but could technically be anywhere I suppose. As to how it works - read the manual and/or the online help. Chapter 2 outlines the Methodology and lays the foundation for the spec...

Whomever installed the plug-in in the projects where it does work didn't do it correctly. You need to find your Server installation media and rerun the install. It will default to 'Maintenance Mode' and allow you to install new plug-ins. This way it not only gets into all existing projects but also ...

Sorry, no - with the advent of Version Control I haven't released a job since the 4.x release.

First order of business would be to search the forums as this has been discussed quite a bit over the years.

Usually has to do with CLOB fields or others of that ilk, that or columns declared as NUMBER with no precision in Oracle. Anything like that in your source table?

Or the good 'ol Mark One Eyeball?

That's a substantial difference and should be readily apparent.

The Version Control project is "special" and requires more than a import to get it back to where it was. Read this thread for some specifics on what extra bits it needs.

Besides the fact that you haven't properly ended the first sql statement, you can't use User Defined SQL like this in one link, break it up into two. All columns defined in the stage need to be bound into each sql statement.

At worst case, add it to your script - either that or put a fully pathed (instead of a relative one) reference to sqlplus there. These are my entries in dsenv ORACLE_HOME=/usr/oracle/product/9.2.0.6; export ORACLE_HOME PATH=$DF30DIR/bin:$PATH:$ORACLE_HOME/bin. You don't literally have a dot at the e...