Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: 2GB Problem with Oracle 8.0.5 an Windows 2000 Server

Re: 2GB Problem with Oracle 8.0.5 an Windows 2000 Server

From: Sybrand Bakker <sybrandb_at_hccnet.nl>
Date: Wed, 18 Aug 2004 19:32:32 +0200
Message-ID: <4g47i0tg3vfgdl02s9uldekg3qk9ttj102@4ax.com>


On 18 Aug 2004 08:05:37 -0700, d.speh_at_donau-touristik.at (Dani Speh) wrote:

>Hi ,
>I have a problem with that database.Every night I make a full export
>from an Production db an an import to an standby db. Everything runs
>fine till yesterday. Import ends with an Error 2237 (Invalid file
>size).I looked at the datafiles and saw the error in the indexfile.
>The indexfile is 2.02 GB and import will not create such a large file.
>I've tried to create the indexfile later( with import INDEXFILE=) but
>import still wants to make a big file.Tonight I'll try the compress
>option.I hope this works. But if not can anybody help me with this
>problem?
>
>
>Dani

You badly need to read the export documentation in the Oracle Server Utilities manual. Indexes are not exported at all, they are recreated during import. The size of your indexfile is not a concern. The compress option doesn't compress the dump file, but it does make sure tables with multiple extent will be recreated as a table with a single extent.
You can safely forget about the compress option : it won't work. You'd better concentrate on getting out of the stone age and upgrade to 9i.

--
Sybrand Bakker, Senior Oracle DBA
Received on Wed Aug 18 2004 - 12:32:32 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US