Re: Migration:- Solaris 220.127.116.11 to 10.2.0.3
Date: Fri, 1 Aug 2008 09:25:16 -0400
Not quite identical to your scenario, but we just migrated a number of
Solaris 9 18.104.22.168 to Solaris 10 10.2.0.3. No major issues, but we did run into a little
puzzler dealing with tables that contained columns that were encrypted via DBMS_OBFUSCATION_TOOLKIT.
If these tables were part of a full export, the encrypted columns would always come with varying and erroneous lengths that were not a multiple of 8 bytes. We had to export/import these tables individually and that worked fine.
We double-checked NLS_LANG on the import/exports, validated the data for correct lengths in the source database and so forth - but could not find a reason why a full export would fail but the individual export would succeed.
We were able to reproduce this issue but as we had a fix, never did raise a S/R for it.
On Fri, Aug 1, 2008 at 7:15 AM, David cheyne <david.cheyne_at_gmail.com> wrote:
> Hi List,
> I'm in the throws of migrating a live system. We are updating our Sun boxes
> to v445's with Solaris 10 (coming from 8) and at the same time from 9i to
> 10g. I was wondering about a full import option to move the data, the DB is
> about 50Gb, so I don't think it's worth dragging it through datapump.
> I've imported a single schema (the applications data) into a 10g instance
> for testing; this worked fine. The main issues are in-house developments
> based around the live data. Developers have created tables, synonyms, views
> and database links (coming in from elsewhere) in their own schema, all of
> which accesses objects in the main schema; so plenty of scope for missing
> permissions synonyms and of course . . . tantrums! The people have also put
> tables and packages into the main schema (yes I know!) these again could be
> an issue, as they tend to access the developers own schema.
> SO after all of that mess, I think a one shot FULL import would be easier
> than trying to pick my way through that little lot. I intend to drop the
> two application schemas and reuse the already created instance for this.
> Does anybody know of issues with full imports from: Solaris 8 - 22.214.171.124 to
> Solaris 10 - 126.96.36.199.3? Or even problems afterwards. We do have problems
> importing tables with LOB's in but that is a known issue.
> Thanks for reading.
> David Cheyne
> Oracle Database Administrator