Re: Error 1455 doing export

From: Martin Laslett <mlaslett_at_hotmail.com>
Date: 11 Oct 2001 21:28:26 -0700
Message-ID: <a7d5cc21.0110112028.1dd86e1c@posting.google.com>

"Philip Ross" <philip_ross_at_my-deja.com> wrote in message news:<3idx7.1304$096.186924_at_news6-win.server.ntlworld.com>...
> I am getting an error whilst doing an export from an Oracle 8.1.5 database
> on Solaris. The error that occurs is:
>
> EXP-00008: ORACLE error 1455 encountered
> ORA-01455: converting column overflows integer datatype
>
> The structure of the table being exported is:
>
> (
> A NUMBER(38, 0) NOT NULL,
> B VARCHAR2(200),
> C BLOB,
> D DATE,
> E DATE,
> F VARCHAR2(30),
> G VARCHAR2(30),
> H VARCHAR2(20) NOT NULL,
> I VARCHAR2(1) DEFAULT 'N',
> J VARCHAR2(50)
> )
>
> Any ideas as to what could be causing this error?
>
> Thanks,
>
> Phil

Hi Phil,

Metalink shows a couple of possible options - if you are using transportable tablespaces the most likely is bug 970640.

I've cut the top of note 76670.1 and pasted it here (sorry for the size).

Cheers,
Martin

---

Bug:970640 Transportable Tablespaces can Corrupt the Data Dictionary

---

• Important: This alert has been updated on 12/Nov/1999 to include
• the information previously marked as "** Under Investigation".
• Further updates may be made as the side effects are complex.
• To check for this problem you also will need the script in [NOTE:76746.1] Versions Affected

  ---

  This issue only can only affect you if you use Transportable Tablespaces. Transportable tablespaces were introduced in Oracle8i release 8.1.5.

  The issue described here affects Oracle releases: 8.1.5.X   The issue described here is fixed in Oracle release: 8.1.6.0

Platforms Affected

---

  This issue is GENERIC and affects ALL platforms.

Description

---

  Transportable tablespaces (sometimes referred to as pluggable tablespaces)
  were introduced in Oracle 8.1. Transportable tablespaces allow datafiles
  from a database to be copied to another machine (running the same operating
  system) and 'plugged' into a different database eliminating the need   for a logical copy of the data (eg: via export/import).   

  When setting up to transport a tablespace an export of the metadata   from the source database is required for transport to the target database.
  The problem described here can cause the exported metadata to contain
  an invalid object number. This invalid object number may be silently   imported causing the next object number on the target database to be   set to a very high value. In turn this high value can reach an in-built
  limit making it impossible to create new objects (ie: tables , procedures,
  indexes or any form of object).

<snip>

Possible Symptoms

---

  Note: The effects of this problem may not be noticed until a few thousand
  object 'creations' have occurred on the target database.

  Visible symptoms from the problem include:

<snip>

Export may report errors if an attempt is made to export

     objects with high object numbers.
     Eg:  EXP-00008: ORACLE error 1455 encountered
          ORA-01455: converting column overflows integer datatype
     This side-effect is documented in [BUG:1073721]
*************************************************************************

Another piece of info states:

4. Sequence of events leading to the problem

     Import a bad transportable tablespace as per bug:970640
     Create a table in the target database
     Try to export the table.

Hope this helps. Good luck solving.

Cheers,
Martin Received on Thu Oct 11 2001 - 23:28:26 CDT