Bad export utility...bad,bad!

[Quoted] Hi all,

[Quoted] I have this weirdness that is happing when I try to use the Export utility [Quoted] in a shell script. I have Oracle installed on an AIX (v4.3) RS/6000 box and [Quoted] I'm putting together a disaster recovery plan for the Oracle install. The backup software that I'm using allows a script to be run before the backup [Quoted] and after. The script is terribly simple in that I run the Export utility to [Quoted] export a portion of the database. The export works well. That's not the problem.

The issue is that the backup software will run the script, but only if the script does not allow any text to be written to stdout. I know, I knowwhy ?!? I dunno - the only thing the backup software wants to know is the [Quoted] exit value of the script. Anyway, I try redirecting the Export's output and [Quoted] funny enough, I can't do it.

I have the script encased in an output block:

    OUTF = file.out
    {
} >> $OUTF
and Export will still write to my terminal.

I try redirecting the output in the command itself:

    Exp .. > export.out

And Export still writes to the terminal.

Ok, I thought, let's get physical with this thing. I redirect stderr to stdout and turn off stdout:

    2>&1 >&-

Nope, that doesn't work either.

Finally, I try /dev/null

    1>/dev/null

Still no luck. Export will write to the terminal no matter what.

Any ideas on how to get around this persistent, unwanted behavior.

Thanks a million!

-Dan Received on Sat Jul 21 2001 - 23:54:24 CEST