Hi faculties,
I perform an export of a schema from one DB to another one. Is it
necessary to do some post maintainence tasks after the import is over?
By tasks i mean tasks like index reorganization.

Thanks in advance
Jackal

"jackal" <jackal_on_work (AT) yahoo (DOT) com> wrote


You can run statistics and recompile all invalid objects. Check your import
log file for any errors.

Hi,
Thanks for replying. can you elaborate on stats gathering? What stats
should i gather...whole schema or just indexes?

Regards
Jackal

jackal wrote:

jackal wrote:
Only indexes doesn't make sense.

Also exp has a parameter you can use to have imp generate statistics

--
Sybrand Bakker
Senior Oracle DBA

I generally run a script to re-create all public synonyms, and
re-create the grants - just in case.

jackal wrote:
Sometimes you may want to change the passwords of some users so they
are not the same as production. Also, see if you want to remove and
dblinks that may exist.

If you grep the export file for "CREATE IND" you may see that the
indices are created as part of the import. If you have time or undo
constraints, sometimes it can be better to not create the indices until
after you import the data. Either way, the indices are new so they
don't need to be reorganized. Even in normal operations it is rare for
indices to _need_ to be reorganized (massive deletes being a big
exception).

Besides what the others said, there may be application specific tasks.
There may also be other issues depending on the purpose of the import,
as for example if you are upgrading or migrating.

jg
--
@home.com is bogus.
These people might want to think about carryforward writedowns Novell
may have that could help Oracle's tax situation, as well as the fact
that Oracle needs a _server_ oriented Linux distribution:
http://searchopensource.techtarget.c...180607,00.html