DSXchange

Any database/key constraint violations can generate a warning. Data types/format mismatches can cause warnings, to name a few. Browse the website for more specific examples.

Are there any surrounding warning messages. Run the job again for maybe 2 records and see if any more messages are there. Also try resetting the job, this brings some more info to the log file at times.

In the command activity stage you have to give the fully qualified path of the file.

By a simple equal sign (=).

Clear the status file, clear the log, make sure their size remains in check. Make a copy of that job and delete the original one. compile the second job. And btw, there is no command line compile, i believe Kumar was referring to resetting the job.

At the unix level, try running the cat command and see whats present there.

Yup.Its cat.

As it says, see your dba. The enterprise stage needs more privileges than a regular OCI stage. Read your Oracle Enterprise Stage pdf file.

Ultramundane wrote:Awk keeps track of the open files and once opened it will only append to the files. Using this method you do not need to get the unique filenames. Awk will overwrite/create when opened (used first time) and will append for the rest.

O yea thats right. Just needs testing it. Nice...

No i mean the product (first column) is being repeated, need to get only unique values to build file names.

Yea, but the duplicates need to be removed plus some more manipulation.

I doubt the OS has anything to do with it. I am on unix (HP-UX). Even i tried it but of no avail.

You can do it in jobcontrol or in after job subroutine.

Not to mention, The odbc enterprise user guide and reference guide.

Your better off emailing to the site webmaster than posting it here. Heres the email address:
webmaster@dsxchange.com