Re: Import fail after 7.1.3 upgrade?
Date: 21 Feb 1995 01:15:28 GMT
Message-ID: <3iberg$kik_at_hustle.rahul.net>
In <3i46h0$350_at_hustle.rahul.net> Dan Bikle <dbikle_at_rahul.net> writes:
>Hi there,
>Please consider this scenario.
>You have a 7.0.16 dbs. A table named EMP which is owned by SCOTT
>resides in the dbs.
>You upgrade the dbs to 7.1.3.
>You export SCOTT.EMP and then drop it.
>Your attempt to import SCOTT.EMP fails due to an improper data
>type conversion.
>A friend of mine swears he ran into this problem.
>He says it can be avoided by running a "special" version of catexp.sql
>after the 7.0.16 -> 7.1.3 upgrade.
>If you have run into this problem please let me know. If you have
>a dbs which has been through the 7.0.16 -> 7.1.3 upgrade please
>run the above experiment & tell me the results.
>I attempted to query the rtss bug database, but their modem seems
>to be on vacation (it does pick up the phone but the terminal
>server is silent). I called support. The analyst said to keep
>trying. I think it's busted. you try: atdt14155989450
>-Dan
>---------------------------------------------------------------------------
>Daniel B. Bikle/Independent Oracle Consultant
>dbikle_at_alumni.caltech.edu | 415/854-9542 | P.O. BOX 'd' MENLO PARK CA 94026
>---------------------------------------------------------------------------
I found out more.
The problem is with the export views, not a data type conversion.
It's a known problem. refer to rtss bulletins:
106203.591, 106203.637
and bug : 219654
The easiest work-around appears to be this:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^To workaround this problem, simply issue the following ALTER TABLE statement to all tables created before V7.1.3, then you will be able to export:
'ALTER TABLE <problem_table> PARALLEL (degree 1 instances 1);'
For further information or clarification, call Oracle Worldwide Support. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The above text came directly from 106203.591.
The bulletin 106203.637 contains a big sql script which might be a big risk if your modem drops bits here & there (like mine does).
One clarification of the above statement. The bug does not prevent export. It prevents IMPORT.
From now on, I will rename tables I wish to rebuild rather than dropping them. Once rebuilt, that is the time to drop.
-Dan
Daniel B. Bikle/Independent Oracle Consultant dbikle_at_alumni.caltech.edu | 415/854-9542 | P.O. BOX 'd' MENLO PARK CA 94026
Received on Tue Feb 21 1995 - 02:15:28 CET