Re: how to export the database to the network dir on NT

Good and sensible advice, unlike much I've seen today in a number of the threads above.

Well said, Billy.

Paul

"Billy Verreynne" <vslabs_at_onwe.co.za> wrote in message news:3c70b4a5.3376232800_at_news.saix.net...
> yeht_at_state.gov (Bob Yeh) wrote:
>
> >Windown NT, Oracle 8.1.6 server.
> >
> >I am having trouble using the AT command to export the Oracle database
> >dump file to a network directory. The job just does not seems to run.
> > My bat file is like this:
> >
> >net use X: \\myserver\d$
> >%ORACLE_HOME%\bin\exp userid/password file=X:\mydb.dmp full=y
>
> What is the error? Check what the STDOUT of the above job has to say.
>
> Also, you are not using any error checking or exception handling in
> your script. If drive X: is already mapped, the NET USE command will
> hang waiting for a response from STDIN. STDIN does not exist in a
> batch job.
>
> It is a bad idea to dump a full db export directly across the network
> too. A dump file should/can be compressed to a much smaller size.
> Besides, the network and resource overheads for a shared mapped drive
> is much bigger than using FTP. Use Windows to copy data plays havoc
> with the o/s caching as Windows just love to cash everthing and the
> kitchen sink, and never properly clean it up afterwards.
>
> Rather dump the file locally, compress it and then use FTP to transfer
> it.
>
> It is many times more flexible ito scripting and error handling.
>
> It can support other platforms too via FTP.
>
> It has better logging - the FTP server maintains a log which can be
> used. The local FTP client also produces STDOUT which can be logged.
>
> Logging with shared drives is not really possible without a lot of
> effort and using something like audit traces.
>
> --
> Billy
>
>
Received on Thu Feb 21 2002 - 13:06:31 CST