From: "Eric BABOULENE" Newsgroups: comp.databases.oracle.server References: <8p3lgm$c96$1@nnrp1.deja.com> Subject: Re: Exporting a Large Table Lines: 43 X-Newsreader: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Message-ID: Date: Sat, 09 Sep 2000 10:57:13 GMT NNTP-Posting-Host: 213.228.31.170 X-Complaints-To: abuse@proxad.net X-Trace: nnrp5.proxad.net 968497033 213.228.31.170 (Sat, 09 Sep 2000 12:57:13 CEST) NNTP-Posting-Date: Sat, 09 Sep 2000 12:57:13 CEST Organization: Guest of ProXad - France Hi, If you are on a UNIX system an get enough space for a compressed export file, try this : 1. EXPORT nod my_pipe p compress < my_pipe > export_file.Z & exp userid/passwd file=my_pipe ........... 2. IMPORT mknod my_pipe p uncompress < export_file.Z > my_pipe & imp userid/passwd file=my_pipe ........... HTH Eric Yurasis Dragon a écrit dans le message ... >You try exporting from a server that has the space. >A network hit yes, but it works : > >exp userid/password@db .... > > >On Tue, 05 Sep 2000 20:36:40 GMT, EnderW wrote: > >>Hi, >> I am kind of into a problem. The client doesnot have space to export >>a large table. Well if they don't export it, they refuse to drop it. >>And they don't have the space to export it. What are my options ? >>Should I recommend them to use export with a sql statement ? if I >>remember correctly, you can put a condition in your export. That way, >>they can export and delete and export and then delete. Is there way to >>concat all these small files into one large export file ? Thanks in >>advn. >