Re: exp/imp (Transportable Tablespace)

On Nov 12, 1:54 pm, Frank van Bortel <frank.van.bor..._at_gmail.com> wrote:
> Tom76 wrote:
> > Transportable Tablespace feature
>
> > source db: 9i
> > target db: 10g
> > OS: source and target is Linux.
> > Tested a migration of few application tablespaces using Transportable
> > Tablespace feature. Packages, procedures did not get migrated.
> > There is no option to specify paackages or procedures to be
> > exported(exp or imp). So I guess they get exported/imported
> > automatically.
> > No errors during the transportable tablespace procedure. Any idea why
> > the packages and procedures did not get migrated.
>
> Time for the concept manual athttp://tahiti.oracle.com...
>
> Where (what tablespace) are procedures stored?
> And what tablespace did you transport?
>
> And as A is not equal to B, no procedures, only data.
> Unless you transported tablespace A of course - in which
> case you lost your database.
>
> And import/export will export procedures, packages and
> functions of a specific user, if you do an export on that
> level - also documented on tahiti, but in the Utilities
> manual.
> --
> Regards,
> Frank van Bortel
>
> Top-posting is one way to shut me up...

The traditional export and import utilities do not have parameters that allow selecting stored procedures, functions, or packages by themselves.

You can obtain the code via user or full database exports. Look at the rows=n option.

If you need only selected objects then it is also easy to extract stored procedure code form dba_source and then just run this into the target database. Oracle provides the dbms_metadata package to do this but we just use a query to extact the source, grants, and synonyms on the procedure.

HTH -- Mark D Powell -- Received on Mon Nov 12 2007 - 12:59:37 CST