MINI MINI MANI MO

Usage:
perl ore_destimport.pl <connect-identifier> <migration-dir-name>

Example:
 perl -I$ORACLE_HOME/R/migration/perl $ORACLE_HOME/bin/ore_destimport.pl oraclesid /tmp/example

Arguments
==========
connect-identifier : connect string to connect to the target database
migration-dir-name: directory where dmp files for import are located.
    zip file created by srcexport.sh should be unzipped into this directory.

What does this script do
======================== 
This script
a)Imports RQSYS schema data
b)Imports ORE user schema if not existed
c)Generates a script to populate rq$script table in sys with data from source db
This script needs to be run MANUALLY to complete the import. The script should be run by a user with dba privileges.
e.g. sqlplus / as sysdba 
IMPORTANT: Please note that all scripts in rq$script data is deleted at the
 target db and loaded with data from the source when the script is executed.

You will be prompted for the password for "system" user.

Assumption:
==========
ORE is setup on the target database. In addition,
a) rqsys schema is present on the target db. (note that the script will automatically recreate rqsys if it is not present).
b) ORE related metadata in sys schema is setup (This should be the case if ORE setup completed successfully. Note that this script does not create any metadata in sys schema. It generates a script that deletes the data in rq$script tables and populates it with data from the source db).
c) No ore user schema with datastore is present on the target
d) There already exists user schema which is the grantee of datastore being imported.

Side-effects:
=============
Will create temporary directory (database) object RQMIG_TEST_DIR that points to migration-dir-name

Potential issues:
=========================
Import (impdp) can fail if the target db tablepsace does not match the source db.
Possible solutions:
a)create the appropriate tablespace and then rerun the script (OR)
b)modify imp_ore_user.sh. Change impdp command to use REMAP_TABLEPSACE parameter

Access privilege to datastore fails to be imported if the grantee does not exist in target database.
Possible solutions:
a)create all grantee schema before importing datastores 

WORKAROUND: CREATE MINING MODEL privilege missing 
===========
If the data mining models for a schema do not get migrated,
 the user may be missing "create mining model" privilege.
Run the script <migration-dir-name>/grant_mining.sql, 
then re-execute imp_ore_user.sh. (this would have been run by ore_destimport.pl)
Example :<migration-dir-name>/imp_ore_user.sh <dbuser> <dbpwd> <instancename>
 
Any items that were missed during the last import will get migrated now.