Re: Full database import

As far as i know full database import/export does not affect most objects in sys schema (fe: sql packages). Many objects are dynamical based on schema and should be created rather than imported to maintain data integrity.

In my opinion to perform succesfull import of database you should create new database with identical tablespaces (especialy if you also moving database files to new location), and after that run same scripts that was run in previous database as user sys (fe: catalog, catproc, dbmspool).

Then you ma do import specifying 'full=y' and 'ignore=y' to prevent errors due to object existence.

After that import should be succesfully _without_ errors.

Hope it helps,
Czeslaw Gryzik

Mick McRae wrote:

> Hi,
>
> I've been trying to use the import utility to import a full database
> export without a great deal of success.
>
> I created a database, with various tablespaces (ie rbs, tools, users,
> etc), added a few users with tables/views indexes etc. I then did a
> full database export.
>
> I then removed the database(all database files) and re-created it using
> the 'create database' command.
> I then ran the catalog.sql script.which also calls the catexp.sql script
> which is required for the import.
>
> I ran the import specifying 'full=y' and it sort of worked. A whole
> bunch of errors when trying to create dba_ synonyms, all_ synonyms,
> etc, as they had all ready been created from running catalog.
>
> It did import all the users objects, but then on entering sqlplus after
> the import had finished, I recieved the following errors.
> ORA-06554: package DBMS_STANDARD must be created before using PL/SQL
>
> Error accessing package DBMS_APPLICATION_INFO
> ERROR:
> ORA-06554: package DBMS_STANDARD must be created before using PL/SQL
>
> Maybe I should have run catproc also. But I assumed the import, imports
> all system objects and that I should not need to run catproc or catalog.
>
> Can anyone tell me the exact procedure for importing using the 'full=y'
> option, to re-create a database to the identical state of the database
> that the export was run from?
>
> Any help would be appreciated
> Regards,
> Mick

--
Czeslaw Gryzik
P.W.P.T. Wasko sp. z o.o.
ul. Akademicka 3A, 44-100 Gliwice
gryzio_at_wasko.gliwice.pl Received on Thu May 21 1998 - 08:17:29 CDT