IMP_FULL_DATABASE role required

Question

Hi,
A strange issue...
I am trying to import atwo tables from one DB to other in solaris but it asks for IMP_FULL_DATABASE role but the target schema has been granted the role already....
Kindly help.........
impdp parfile=/u01/ora10gr2/dolphin/dwh/importUCSDB_DOLPHIN_DMP_20081212081546
+.par+
Import: Release 10.2.0.3.0 - 64bit Production on Friday, 12 December, 2008 8:15:
+46+
Copyright (c) 2003, 2005, Oracle.  All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit
Production
With the Partitioning, OLAP and Data Mining options
Master table "DOL_DMP"."DP_IMP_DOL_DMP_20081212081546" successfully loaded/unloa
ded
Starting "DOL_DMP"."DP_IMP_DOL_DMP_20081212081546":  parfile=/u01/ora10gr2/dolph
in/dwh/importUCSDB_DOLPHIN_DMP_20081212081546.par
Processing object type TABLE_EXPORT/TABLE/PROCACT_INSTANCE
ORA-39083: Object type PROCACT_INSTANCE failed to create with error:
ORA-26723: user "DOL_DMP" requires the role "IMP_FULL_DATABASE"
Failing sql is:
BEGIN
sys.dbms_logrep_imp.instantiate(object_owner=>'DOLPHIN3', object_name=>'RVGRUPPE
+', object_type=>'2', export_db_name=>'UCSDB', inst_scn=>'2819167066', ignore_scn+
+=>'2819124206');COMMIT; END;+
My Parfile is .....
USERID=dol_dmp/dol_dmp@ecdcbhs1
JOB_NAME=dp_imp_dol_dmp_20081212122318
DUMPFILE=exportucsdb_DOLPHIN_DMP_%U.dmp
LOGFILE=importUCSDB_DOLPHIN_DMP_20081212122318.log
FULL=N
PARALLEL=2
DIRECTORY=DP_EXPORT_DIR
+#EXCLUDE=STATISTICS+
TABLE_EXISTS_ACTION=TRUNCATE
+# TABLE_EXISTS_ACTION=REPLACE+
INCLUDE=TABLE:"IN ('ZAHLUNGSEMPFANG','RVGRUPPE')"
REMAP_SCHEMA=dolphin3_t:dol_dmp transform=oid:n
+#REMAP_TABLESPACE=PHIN_DATA1:DOL_DATA PHIN_IDNX:DOL_IDX+
Any suggestions????????????????
Edited by: user10707066 on Dec 12, 2008 3:30 AM

Answer 1

Vijay,
Procact_instance are procedural actions that need to take place during an export and import. These are actions that people register with the datapump code and are called during export and import. They are completely independent of the datapump code.
You state the you already created the schema. Which schema did you create? If it is the one that is doing the import, then that should be fine. the other schema that needs the imp_full_database should be created when the import job is run. The problem you are having seems to be an issue with the procedural action. Maybe the best thing to do is to file a bug and supply a dumpfile where this is reproducible. That would be an easier way to determine what exactly is going on.
The only other thing I can think of is if you are chaning versions (export from 10.1 and import on 10.2) or any combination. The reason I'm asking is because I wonder if the procedural action changed between version and the writer of the procedural action didn't take into account that this would have to be supported.
So, if you are able to enter a bug through oracle support, you should tell them about the versions of where the export and import are happening, and if you can supply a dumpfile, that would also help. I would think that a dump file with only the metadata should be enough to reprocude it, but you can try this before entering a bug.
Not knowing what the procedural action is, or what it is trying to do, I'm not sure there is much more I can determine.
Good Luck
Dean