only after I remember when I see the error in the log file :-(. More
seriously it doesn't actually matter for my purposes except that the
difference between
import terminated successfully without warnings and
import terminated successfully with warnings is easy to miss.
--
Niall Litchfield
Oracle DBA
Audit Commission UK
*****************************************
Please include version and platform
and SQL where applicable
It makes life easier and increases the
likelihood of a good answer
******************************************
"Norman Dunbar" <Norman.Dunbar_at_lfs.co.uk> wrote in message
news:E2F6A70FE45242488C865C3BC1245DA702685A64_at_lnewton.leeds.lfs.co.uk...
> Niall,
>
> have you rtried setting STATISTICS=NONE on the export ?
>
> Regards,
> Norman.
>
> -------------------------------------
> Norman Dunbar
> Database/Unix administrator
> Lynx Financial Systems Ltd.
> mailto:Norman.Dunbar_at_LFS.co.uk
> Tel: 0113 289 6265
> Fax: 0113 289 3146
> URL: http://www.Lynx-FS.com
> -------------------------------------
>
>
> -----Original Message-----
> From: Niall Litchfield [mailto:n-litchfield_at_audit-commission.gov.uk]
> Posted At: Tuesday, July 23, 2002 3:47 PM
> Posted To: server
> Conversation: Imported DB runs SLOWER on faster machine
> Subject: Re: Imported DB runs SLOWER on faster machine
>
>
> I agree that Daniel is right. However by default you *do* get stats on
> import - just estimated stats. I know this because moving an 816 export
> to
> an 817 instance *always* gives a dbms_stats error on import. Ignoring
> this
> and reanalyzing works just fine.
>
>
>
Received on Tue Jul 23 2002 - 13:59:59 CDT
