Re: V10.2.0.1 exp/imp ORA-00910: specified length too long for its datatype
- From: "sol beach" <sol.beach@xxxxxxxxx>
- To: "Jared Still" <jkstill@xxxxxxxxx>
- Date: Wed, 19 Mar 2008 10:00:08 -0700
THANKS ALL.
The solution which i was hoping to avoid was to drop the database
& create it using UTF8 characterset.
+ imp inlogic/inlogic file=/u05/orasupp/orcl/datapump/inlogic.dmp log=
test-imp123.log tables=TBLCUSTOMREPORT buffer=32000000
Import: Release 10.2.0.1.0 - Production on Wed Mar 19 09:53:58 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 -
64bit Production
With the Partitioning, OLAP and Data Mining options
Export file created by EXPORT:V10.02.01 via direct path
import done in UTF8 character set and UTF8 NCHAR character set
import server uses AL32UTF8 character set (possible charset conversion)
. importing INLOGIC's objects into INLOGIC
. importing INLOGIC's objects into INLOGIC
. . importing table "TBLCUSTOMREPORT" 1474 rows imported
IMP-00017: following statement failed with ORACLE error 942:
"ALTER TABLE "TBLCUSTOMREPORT" ADD CONSTRAINT "CR_ORGID_FK" FOREIGN KEY
("OR"
"GANIZATIONID") REFERENCES "TBLORGANIZATION" ("ORGANIZATIONID") ON DELETE
CA"
"SCADE ENABLE NOVALIDATE"
IMP-00003: ORACLE error 942 encountered
ORA-00942: table or view does not exist
About to enable constraints...
IMP-00017: following statement failed with ORACLE error 2430:
"ALTER TABLE "TBLCUSTOMREPORT" ENABLE CONSTRAINT "CR_ORGID_FK""
Import terminated successfully with warnings.
+ echo Wed Mar 19 09:53:58 PDT 2008
Wed Mar 19 09:53:58 PDT 2008
++ date
+ END='Wed Mar 19 09:57:42 PDT 2008'
On Wed, Mar 19, 2008 at 9:47 AM, Jared Still <jkstill@xxxxxxxxx> wrote:
> On Wed, Mar 19, 2008 at 9:35 AM, Jared Still <jkstill@xxxxxxxxx> wrote:
>
> >
> >
> > It would appear that the database to be imported into needs to have been
> > created with NLS of WE8ISO8859P1, or other single byte character set.
> >
>
> Sorry, other way round. Importing database needs multibyte charset.
>
>
> --
> Jared Still
> Certifiable Oracle DBA and Part Time Perl Evangelist
>
- References:
- V10.2.0.1 exp/imp ORA-00910: specified length too long for its datatype
- From: sol beach
- Re: V10.2.0.1 exp/imp ORA-00910: specified length too long for its datatype
- From: Riku Räsänen
- Re: V10.2.0.1 exp/imp ORA-00910: specified length too long for its datatype
- From: Jared Still
- Re: V10.2.0.1 exp/imp ORA-00910: specified length too long for its datatype
- From: Jared Still
Other related posts:
- » V10.2.0.1 exp/imp ORA-00910: specified length too long for its datatype
- » Re: V10.2.0.1 exp/imp ORA-00910: specified length too long for its datatype
- » Re: V10.2.0.1 exp/imp ORA-00910: specified length too long for its datatype
- » Re: V10.2.0.1 exp/imp ORA-00910: specified length too long for its datatype
- » Re: V10.2.0.1 exp/imp ORA-00910: specified length too long for its datatype
- » Re: V10.2.0.1 exp/imp ORA-00910: specified length too long for its datatype
- » Re: V10.2.0.1 exp/imp ORA-00910: specified length too long for its datatype
- » Re: V10.2.0.1 exp/imp ORA-00910: specified length too long for its datatype
- » Re: V10.2.0.1 exp/imp ORA-00910: specified length too long for its datatype
- » Re: V10.2.0.1 exp/imp ORA-00910: specified length too long for its datatype
- » Re: V10.2.0.1 exp/imp ORA-00910: specified length too long for its datatype
- V10.2.0.1 exp/imp ORA-00910: specified length too long for its datatype
- From: sol beach
- Re: V10.2.0.1 exp/imp ORA-00910: specified length too long for its datatype
- From: Riku Räsänen
- Re: V10.2.0.1 exp/imp ORA-00910: specified length too long for its datatype
- From: Jared Still
- Re: V10.2.0.1 exp/imp ORA-00910: specified length too long for its datatype
- From: Jared Still