X-Received: by 10.224.130.195 with SMTP id u3mr26718476qas.1.1367721931447; Sat, 04 May 2013 19:45:31 -0700 (PDT) X-Received: by 10.49.134.36 with SMTP id ph4mr612691qeb.30.1367721931400; Sat, 04 May 2013 19:45:31 -0700 (PDT) Path: news.cambrium.nl!textnews.cambrium.nl!feeder1.cambriumusenet.nl!feed.tweaknews.nl!209.85.216.87.MISMATCH!l3no2192765qak.0!news-out.google.com!y6ni0qax.0!nntp.google.com!m7no2219082qam.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.databases.oracle.server Date: Sat, 4 May 2013 19:45:31 -0700 (PDT) In-Reply-To: <1ef17e20-4b53-4c36-8227-849b4719d318@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=148.177.1.211; posting-account=PUA9dQoAAAAWB6fqjaJDJmTx7eb4x-f4 NNTP-Posting-Host: 148.177.1.211 References: <1ef17e20-4b53-4c36-8227-849b4719d318@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <7d10f95c-33b4-4a98-9967-82a6c5684f95@googlegroups.com> Subject: Re: NLS_LENGTH_SEMANTICS = CHAR import is too slow From: zigzagdna@yahoo.com Injection-Date: Sun, 05 May 2013 02:45:31 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Xref: news.cambrium.nl On Saturday, May 4, 2013 4:38:13 PM UTC-4, zigz...@yahoo.com wrote: > I am converting a database from its current character set WE8ISO88591 to = AL32UTF8 I am using NLS_LENGTH_SEMANTICS to CHAR so I do not have to increa= se column lengths. I follow Oracle instructions: 144808.1 313175.1 Except i= mport which takes way too long. I took a full export of WE8ISO8859p1 Databa= se and now importing it in AL32UTF8. It is always difficult to prove where = the slowness is coming from; but I think it has to do something with NLS_LE= NGTH_SEMANTICS. On the same server; if new database was in WE8ISO8859P1, a = 5 million row table import took 2 hours; but in Al32UTF8 with NLS_LENGTH_SE= MANTICS it is taking 1 day!!! Any idea how to improve the performance of im= port.