ORA-39112: Dependent object type

hi,
i had exported in one database.Based on the export file i have imported another dataabse.i got the below error,
ORA-39112: Dependent object type
how to solve this issues?.
By
siva

Hello kn,
Please refer to the following link [ORA-39112: Dependent object type |http://ora-39112.ora-code.com/|Click]
*009*
Edited by: 009 on Dec 16, 2009 10:22 PM

Similar Messages

ORA-39112: Dependent object type OBJECT_GRANT - using Datapump

Hi, all.
I am importing full database from 10g to 11g, using datapump:
impdp system/aroeira directory=DATA_PUMP_DIR full=y dumpfile=saodlx_full.dmp logfile=saodlx_full_imp.log PARALLEL=6
I got error message below with partitioned table:
ORA-39112: Dependent object type OBJECT_GRANT:"SHR04" skipped, base object type TABLE:"SHR04"."SHR04_ARMAZENAGEM_DTL" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"SHR04" skipped, base object type TABLE:"SHR04"."SHR04_ARMAZENAGEM_DTL" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"SHR04" skipped, base object type TABLE:"SHR04"."SHR04_ARMAZENAGEM_DTL" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"SHR04" skipped, base object type TABLE:"SHR04"."SHR04_ARMAZENAGEM_DTL" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"SHR04" skipped, base object type TABLE:"SHR04"."SHR04_ARMAZENAGEM_DTL" creation failed
ORA-39112: Dependent object type OBJECT_GRANT:"SHR04" skipped, base object type TABLE:"SHR04"."SHR04_ARMAZENAGEM_DTL" creation failed
Please, anybody can help me?
Thanks in advance.
Leonardo.

Which exact versions are you dealing with?
There are a couple of MOS notes about this topic: *Compatibility Matrix for Export And Import Between Different Oracle Versions [ID 132904.1]* and *Export/Import DataPump Parameter VERSION - Compatibility of Data Pump Between Different Oracle Versions [ID 553337.1]*
It is recommended that both databases have the latest patchset installed.
Also, you can troubleshoot the issue generating an SQL file with tables creation for the original dump (SQLFILE parameter to impdp), and extract and create those tables alone to see if there is something wrong there.
Regards.
Nelson

Impdp with error ORA-39083,ORA-00942,ORA-00959,ORA-39112,help!!!

Hi,Friends,
I did import a dump file, should be a schema by data pump.Got these errors:
ORA-39083: Object type TABLE failed to create with error
followed error:
ORA-00942: table or view does not exist
or
ORA-00959: tablespace 'USERS2' does not exist
ORA-39112: Dependent object type %s skipped, base object type %s creation failed ORA-39082: Object type created with compilation warnings
Would anybody here can help me out?Thanks!

Either pre-create the users2 tablespace in the target database, or use remap_tablespace parameter to specify the target tablespace instead of users2.
As usual, complete syntax is in the doc - http://download.oracle.com/docs/cd/B19306_01/server.102/b14215/dp_import.htm#sthref342

TYPE OR TABLE DEPENDENCY OF OBJECT TYPE (ORA-2303)

제품 : SQL*PLUS
작성날짜 : 2004-05-20
==================================================
TYPE OR TABLE DEPENDENCY OF OBJECT TYPE (ORA-2303)
==================================================
PURPOSE
Type이나 table의 dependency가 있는 type을 drop하거나 replace하고자
하면 ORA-02303 error가 난다. 이 error의 원인을 알아보도록 한다.
Explanation
Object의 attribute나 method를 수정하기 위해서는 object type을 drop하고 재생성
해야 한다. Type이나 table의 dependency가 있는 type을 drop하거나 replace하고자
하면 ORA-02303 error가 난다. Object type은 type (nested table 또는 VARRAY)
또는 object table로써 구체적으로 표현된다. 만약 data의 보존이 필요하다면
temporary table에 manual하게 옮겨놓아야 한다.
SQL Reference guide에 의하면 DROP TYPE FORCE 옵션은 recommend하지 않는다.
왜냐하면 이 옵션을 쓰게 되면 복구가 불가능하고 dependency가 있던 table들은
access하지 못하는 결과를 초래한다.
Example
아래의 query 1, 2, 3은 dependency을 확인하는 query문이다.
1. Find nested tables
select owner, parent_table_name, parent_table_column
from dba_nested_tables
where (table_type_owner, table_type_name) in
(select owner, type_name
from dba_coll_types
where elem_type_owner = '<typeOwner>'
and elem_type_name = '<typeName>');
2. Find VARRAYs
select owner, parent_table_name, parent_table_column
from dba_varrays
where (type_owner, type_name) in
(select owner, type_name
from dba_coll_types
where elem_type_owner = '<typeOwner>'
and elem_type_name = '<typeName');
3. Find object tables
select owner, table_name
from dba_object_tables
where table_type_owner = '<typeOwner>'
and table_type = '<typeName>'
and nested = 'NO';
Example ) Logon as Scott
/* Create an user defined object type */
SQL> create type object_type as object (
col1 number,
col2 varchar2(20))
Type created.
/* Create nested table type */
SQL> create type object_ntable as table of object_type
Type created.
/* Create varray type*/
SQL> create type object_varray as varray(5) of object_type
Type created.
/* Create parent table with nested table and varray */
SQL> create table master (
col1 number primary key,
col2_list object_ntable,
col3_list object_varray)
nested table col2_list store as master_col2
Table created.
/* Create object table */
SQL> create table object_table of object_type (col1 primary key)
object id primary key;
Table created.
ORA-2303 results if attempt to drop type with dependencies
SQL> drop type object_type;
drop type object_type
ERROR at line 1:
ORA-02303: cannot drop or replace a type with type or table dependents
위의 queery 1,2,3을 이용하여 object type dependency을 확인한다.
-- Find nested tables utilizing object type
SQL> select owner, parent_table_name, parent_table_column
from dba_nested_tables
where (table_type_owner, table_type_name) in
(select owner, type_name
from dba_coll_types
where elem_type_owner = 'SCOTT'
and elem_type_name = 'OBJECT_TYPE');
OWNER PARENT_TABLE_NAME PARENT_TABLE_COLUMN
SCOTT MASTER COL2_LIST
-- Find VARRAYs utilizing object type
SQL> select owner, parent_table_name, parent_table_column
from dba_varrays
where (type_owner, type_name) in
(select owner, type_name
from dba_coll_types
where elem_type_owner = 'SCOTT'
and elem_type_name = 'OBJECT_TYPE');
OWNER PARENT_TABLE_NAME PARENT_TABLE_COLUMN
SCOTT MASTER COL3_LIST
-- Find object tables
SQL> select owner, table_name
from dba_object_tables
where table_type_owner = 'SCOTT'
and table_type = 'OBJECT_TYPE'
and nested = 'NO';
OWNER TABLE_NAME
SCOTT OBJECT_TABLE
참고)
bulletin : 11576 처럼 utility을 이용하는 방법이 있다.
우리는 여기서 주의하여야 할 것은 script $ORACLE_HOME/rdbms/admin/utldtree.sql
을 내가 보고자 하는 user에서 돌려야 한다는 것이다.
$sqlplus scott/tiger
SQL> @$ORACLE_HOME/rdbms/admin/utldtree.sql
SQL> exec deptree_fill('TYPE','SCOTT','OBJECT_TYPE');
PL/SQL procedure successfully completed.
SQL> select * from ideptree;
DEPENDENCIES
TYPE SCOTT.OBJECT_TYPE
TYPE SCOTT.OBJECT_NTABLE
TABLE SCOTT.MASTER
TYPE SCOTT.OBJECT_VARRAY
TABLE SCOTT.MASTER
TABLE SCOTT.MASTER_COL2
TABLE SCOTT.OBJECT_TABLE
Reference Documents
Korean bulletin : 11576
<Note:69661.1>

Hi Carsten,
Thanks for the sharp hint. It works.
However, when I create a table using the schema, it gives me this error:
varray DOC."LISTOFASSIGNEDNUMBER"."ASSIGNEDNUMBER"
ERROR at line 14:
ORA-02337: not an object type column
Here is the script:
CREATE TABLE CUSTOMMANIFEST (
ID NUMBER PRIMARY KEY,
DOC sys.XMLTYPE
xmltype column doc
XMLSCHEMA "http://www.abc.com/cm.xsd"
element "CustomManifest"
varray DOC."LISTOFMANIFESTPORTINFO"."MANIFESTPORTINFO"
store as table MANIFESTPORTINFO_TABLE
(primary key (NESTED_TABLE_ID, ARRAY_INDEX))
organization index overflow
varray DOC."LISTOFASSIGNEDNUMBER"."ASSIGNEDNUMBER"
store as table ASSIGNEDNUMBER_TABLE
(primary key (NESTED_TABLE_ID, ARRAY_INDEX))
organization index overflow
LISTOFASSIGNEDNUMBER itself is complexType and not sure where is the error....
You may note there are more than two hierachy/levels...
Thanks.

Full import/export from 10gR2 to 11gR1 / ORA-39083: Object type PROCACT_SYS

Hi,
I did a full db export/import (data pump - skipped existing objects) from 10gR2 to 11gR1 (win2003 server). it looks like everything went fine except with this error:
is this a serious error? what should I do to fix this error?
ORA-39083: Object type PROCACT_SYSTEM failed to create with error:
ORA-20000: Incompatible version of Workspace Manager Installed
Failing sql is:
BEGIN
declare ver varchar2(100) ; dummy integer; compile_exception EXCEPTION; PRAGMA EXCEPTION_INIT(compile_exception, -06550); invalid_table EXCEPTION; PRAGMA EXCEPTION_INIT(invalid_table, -00942); procedure createErrorProc is begin execute immediate 'create or replace function system.wm$_check_install return boolean is begin return true ; end;' ; end ; begin
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PROCOBJ
ORA-39083: Object type PROCOBJ failed to create with error:
ORA-29357: object AUTO_TASK_CONSUMER_GROUP already exists
Failing sql is:
BEGIN
dbms_resource_manager.create_consumer_group('AUTO_TASK_CONSUMER_GROUP','System maintenance task consumer group','ROUND-ROBIN');COMMIT; END;
ORA-39083: Object type PROCOBJ failed to create with error:
ORA-06550: line 2, column 1:
PLS-00201: identifier 'BMS_SCHEDULER.DISABLE' must be declared
ORA-06550: line 2, column 1:
PL/SQL: Statement ignored
Failing sql is:
BEGIN
bms_scheduler.disable( 'SYS."WEEKNIGHT_WINDOW"',force=>TRUE);
dbms_scheduler.set_attribute_null( 'SYS."WEEKNIGHT_WINDOW"','SCHEDULE_NAME');
dbms_scheduler.set_attribute_null( 'SYS."WEEKNIGHT_WINDOW"','START_DATE');
dbms_scheduler.set_attribute_null( 'SYS."WEEKNIGHT_WINDOW"','END_
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/POST_SYSTEM_ACTIONS/PROCACT_SYSTEM
Processing object type DATABASE_EXPORT/SCHEMA/PROCACT_SCHEMA
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE
ORA-39083: Object type TABLE failed to create with error:
ORA-00439: feature not enabled: Partitioning
Failing sql is:
CREATE TABLE "SYSTEM"."LOGSTDBY$APPLY_PROGRESS" ("XIDUSN" NUMBER, "XIDSLT" NUMBER, "XIDSQN" NUMBER, "COMMIT_SCN" NUMBER, "COMMIT_TIME" DATE, "SPARE1" NUMBER, "SPARE2" NUMBER, "SPARE3" VARCHAR2(2000)) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 STORAGE( BUFFER_POOL DEFAULT) TABLESPACE "SYSAUX" PARTITION BY RANGE ("COMMIT_SCN") (PARTITION "P0" VALUES LESS THAN (0) PCTFREE 10 PCTUSED 4
ORA-39151: Table "SYSMAN"."AQ$_MGMT_NOTIFY_QTABLE_T" exists. All dependent metadata and data will be skipped due to table_exists_action of skip
ORA-39151: Table "SYSMAN"."AQ$_MGMT_NOTIFY_QTABLE_H" exists. All dependent metadata and data will be skipped due to table_exists_action of skip
Edited by: Odeh on Jul 29, 2009 12:49 PM
Edited by: Odeh on Jul 29, 2009 1:12 PM

Pl see if these MOS Docs help
730373.1 - ORA-39083 ORA-20000 Incompatible Version of Workspace Manager Installed
743097.1 - IMP-00017 ORA-20000 Importing older version of OWM into a higher version
HTH
Srini

IMPDP Help needed please...ORA-39083: Object type PROCOBJ failed to create

OS=Win2003
DB=10gR2
Version = 102.0.4
Hi,
I am running a impdp on a 30gb file and well it seems to have gone fine (much faster then it normally does to be honest), but towards the end it fails, and when researching this error, it seems to be very vague and I was wondering if someone can help me. Below is the log, but I have taken parts out of it that are not relevant.
Import: Release 10.2.0.4.0 - Production on Wednesday, 16 April, 2008 15:22:18
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "SYSTEM"."IMPGEMDEV041608" successfully loaded/unloaded
Starting "SYSTEM"."IMPGEMDEV041608": system/********@iworksdb directory=DATA_PUMP_DIR dumpfile=expdpgemdev.dmp job_name=impgemdev041608 TABLE_EXISTS_ACTION=APPEND SCHEMAS=GEMDEV LOGFILE=IMPIWORKS_BOON.log REMAP_SCHEMA=GEMDEV:IWORKS REMAP_TABLESPACE=IWORKS_INDEX:IWORKS_IDX REMAP_TABLESPACE=IWORKS_IOT:IWORKS_IDX REMAP_TABLESPACE=IWORKS_TABLES:IWORKS_TABLES EXCLUDE=GRANT exclude=statistics STREAMS_CONFIGURATION=N
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"IWORKS" already exists
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/TABLESPACE_QUOTA
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/TYPE/TYPE_SPEC
ORA-31684: Object type TYPE:"IWORKS"."T_NUMBER_TAB" already exists
ORA-31684: Object type TYPE:"IWORKS"."T_VARCHAR2_TAB" already exists
Processing object type SCHEMA_EXPORT/TABLE/TABLE
ORA-39152: Table "IWORKS"."SYS_TOKENTYPE" exists. Data will be appended to existing table but all dependent metadata will be skipped due to table_exists_action of append
ORA-31684: Object type PACKAGE:"IWORKS"."CONT_FEE_DEF_UC" already exists
ORA-31684: Object type PACKAGE:"IWORKS"."COPAYCALCFLAG" already exists
ORA-31684: Object type VIEW:"IWORKS"."VWTREE" already exists
ORA-31684: Object type VIEW:"IWORKS"."V_ROUTE_DTL_GROUP" already exists
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
Processing object type SCHEMA_EXPORT/TABLE/INDEX/FUNCTIONAL_AND_BITMAP/INDEX
Processing object type SCHEMA_EXPORT/POST_SCHEMA/PROCOBJ
ORA-39083: Object type PROCOBJ failed to create with error:
ORA-06550: line 2, column 11:
PLS-00103: Encountered the symbol "VARCHAR2" when expecting one of the following:
:= . ( @ % ;
The symbol ":=" was substituted for "VARCHAR2" to continue.
ORA-06550: line 3, column 12:
PLS-00103: Encountered the symbol "VARCHAR2" when expecting one of the following:
:= . ( @ % ;
The symbol ":=" was substituted for "VARCHAR2" to continue.
ORA-06550: line 4, column 19:
PLS-00103: Encountered the symbol "VARCHAR
ORA-39083: Object type PROCOBJ failed to create with error:
ORA-06550: line 6, column 16:
PLS-00103: Encountered the symbol "RAYSQLACCESS9889405" when expecting one of the following:
* & = - + ; < / > at in is mod remainder not rem
<an exponent (**)> <> or != or ~= >= <= <> and or like LIKE2_
LIKE4_ LIKEC_ between || multiset member SUBMULTISET_
The symbol "* was inserted before "RAYSQLACCESS9889405" to continue.
ORA-06550: line 7, column 17:
PLS-00103: Encountered the symbol "SQL" when expectin
Job "SYSTEM"."IMPGEMDEV041608" completed with 2831 error(s) at 15:30:37
Any help will be much appreciated

I can not seem to find any object named PROCOBJ.
As for the object called RAYSQLACCESS9889405...no idea what this is.
I checked the source for any invalid objects and none.

ORA-30626: function/procedure parameters of remote object types not support

Hello,
I am trying to create a dynamic LOV.
I have a table and package in a remote database, I am connecting to the database using dblink. When I access package I am getting error
ORA-30626: function/procedure parameters of remote object types are not supported
However I can access table with [email protected], not the package!
How can I solve this problem?

Did you ever get an answer/workaround to this? I'm having similar problems in 10g.

ORA- 31684 Object type already exists while import

Hi All,
I wrongly imported a user schema "AP_PD@SRV01" to user "A_IT@SRV02" (Instead of "AP_IT@SRV02").
User AP_IT and Tablespaces are already exists and used remap option while import.
remap_schema=AP_PD:A_IT (instead of mapping to user AP_IT, I misspelled as A_IT)
remap_tablespace=AP_PD_DATA:AP_IT_DATA remap_tablespace=AP_PD_INDEX:AP_IT_INDEX
After successful import to "A_IT@SRV02", I deleted the user "A_IT"
SQL> DROP USER A_IT CASCADE;
I restarted the import to the correct user schema .. i.e AP_IT@SRV02
remap_schema=AP_PD:AP_IT remap_tablespace=AP_PD_DATA:AP_IT_DATA remap_tablespace=AP_PD_INDEX:AP_IT_INDEX
and import was completed with the following errors
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"AP_IT" already exists
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_SPEC
ORA-31684: Object type PACKAGE:"AP_IT"."DBMS_NUMSYSTEM" already exists
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
ORA-31684: Object type PACKAGE_BODY:"AP_IT"."DBMS_NUMSYSTEM" already exists
Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 3 error(s) at 07:53:32
My questions ...
1.Can I assume that import was success as these objects were already exists.
2.Does this effect in anyway to the end users if I ignore this errors assuming import was successful.
3.If import is not a success then what should be my next step to import successfully.
Thanks.

Ven wrote:
Hi All,
I wrongly imported a user schema "AP_PD@SRV01" to user "A_IT@SRV02" (Instead of "AP_IT@SRV02").
User AP_IT and Tablespaces are already exists and used remap option while import.
remap_schema=AP_PD:A_IT (instead of mapping to user AP_IT, I misspelled as A_IT)
remap_tablespace=AP_PD_DATA:AP_IT_DATA remap_tablespace=AP_PD_INDEX:AP_IT_INDEX
After successful import to "A_IT@SRV02", I deleted the user "A_IT"
SQL> DROP USER A_IT CASCADE;
I restarted the import to the correct user schema .. i.e AP_IT@SRV02
remap_schema=AP_PD:AP_IT remap_tablespace=AP_PD_DATA:AP_IT_DATA remap_tablespace=AP_PD_INDEX:AP_IT_INDEX
and import was completed with the following errors
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"AP_IT" already exists
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_SPEC
ORA-31684: Object type PACKAGE:"AP_IT"."DBMS_NUMSYSTEM" already exists
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
ORA-31684: Object type PACKAGE_BODY:"AP_IT"."DBMS_NUMSYSTEM" already exists
Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 3 error(s) at 07:53:32
My questions ...
1.Can I assume that import was success as these objects were already exists.
2.Does this effect in anyway to the end users if I ignore this errors assuming import was successful.
3.If import is not a success then what should be my next step to import successfully.
Thanks.You mentioned AP_IT schema and tablespaces already exist before doing first import itself.
Did you check the list of objects in AP_IT schema before performing import?
The following error is just an informational message and can be ignored:
ORA-31684: Object type USER:"AP_IT" already exists
But, the other 2 errors which says that package +"AP_IT"."DBMS_NUMSYSTEM" already exists+ means you have package in AP_IT schema and it wasn't replaced from the dump you imported. If you need the package from the dumpfile, you can drop the package and can import PACKAGE alone.
Hope this helps.
Regards,
Murali Mohan

Need help on defining object-type dependent attributes for documents

Hi everyone,
I'm trying to define different attributes for documents (attachments), depending on document type.
I performed customizing activities as specified in IMG notes (define structure and table for the attributes, attribute model, register attribute model with table and structure, map model to object type, map object type to document type)
But I didn't find any new BOL in CM GenIL component with my attributes...
I already have type-independent attributes defined, and I see them in the CMDocument BOL.
I don't know how to use my attributes, nor in code niether in UI.
Did I miss something?
Thanks,
Yulia

return self.amount+self.depositamount;I counld not find any amount field in your type definitions
if self.status='OPEN' thenIs it w_accountt.status ?? since there is no status field in accountmanager_t type
return self.currentamount-self.withdrawalamount;same comments for currentamount
member function deposit(d_accountt account_t,d_transno number default 1) return account_t asWhere as your return expression is a number??

ORA-31684: Object type PACKAGE_BODY: already exists while doing Import

Hello,
While doing IMPDP actvity i am getting messages like ORA-31684: Object type PACKAGE_BODY:"APPS"."AZ_DELETE" already exists.
Complete Import log file, same messages were encountered like already exists .
Can you please let us know, whether it is ignorable, beacuse object already exists Or any workaround.
Thanks,
DBA

Can you please let us know, whether it is ignorable, beacuse object already exists Or any workaroundI wouldn't say its ignorable.We don't know if the package body is same or not.Was you requirement to import full schema? If so did you drop all the objects or schema and then imported?
Anand

Ora-31684: Object type already exists with TABLE_EXISTS_ACTION=REPLACE

I want to export using expdp my procedures / functions /packages and triggers from a dev system use impdp to import the new versions into a test system
However, I just get ora-31684: Object type PACKAGE_BODY already exists all the time
I have set TABLE_EXISTS_ACTION=REPLACE but that has made no difference
expdp username/xxxxx@devdb parfile=scripts/cloud_code.par
cloud_code.par:
SCHEMAS=aspasia
DIRECTORY=cloud_upg
DUMPFILE=cloud_code.dmp
LOGFILE=cloud_codeexp.log
INCLUDE=procedure
INCLUDE=function
INCLUDE=package
INCLUDE=trigger
# INCLUDE=index
# INCLUDE=sequence
# INCLUDE=synonym
JOB_NAME=CLOUD_CODE
impdp username/xxxxx@testdb SCHEMAS=aspasia DIRECTORY=cloud_upg DUMPFILE=cloud_code.dmp LOGFILE=cloud_codeimp.log TABLE_EXISTS_ACTION=REPLACE
sample from the logfile:
Import: Release 11.2.0.1.0 - Production on Mon Jan 16 10:53:43 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Release 11.2.0.1.0 - 64bit Production
Master table "ASPASIA"."SYS_IMPORT_SCHEMA_01" successfully loaded/unloaded
Starting "ASPASIA"."SYS_IMPORT_SCHEMA_01": username/********@testdb SCHEMAS=aspasia DIRECTORY=cloud_upg DUMPFILE=cloud_code.dmp LOGFILE=cloud_codeimp.log TABLE_EXISTS_ACTION=REPLACE
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
ORA-31684: Object type PACKAGE_BODY:"ASPASIA"."SERVICE_LEVELS_K" already exists
ORA-31684: Object type PACKAGE_BODY:"ASPASIA"."SERVICE_LEVEL_OPT_K" already exists
ORA-31684: Object type PACKAGE_BODY:"ASPASIA"."SERV_LEV_CHRG_SETUP_K" already exists
ORA-31684: Object type PACKAGE_BODY:"ASPASIA"."SHEET_SETUP_DML_K" already exists
ORA-31684: Object type PACKAGE_BODY:"ASPASIA"."SHEET_SETUP_FORM_K" already exists
ORA-31684: Object type PACKAGE_BODY:"ASPASIA"."SITES_DML_K" already exists
ORA-31684: Object type PACKAGE_BODY:"ASPASIA"."SITES_FORM_K" already exists
ORA-31684: Object type PACKAGE_BODY:"ASPASIA"."SITES_UTL_K" already exists
ORA-31684: Object type PACKAGE_BODY:"ASPASIA"."SITE_EMP_VIEWINGS_DML_K" already exists
ORA-31684: Object type PACKAGE_BODY:"ASPASIA"."SPA_GMAIL" already exists
ORA-31684: Object type PACKAGE_BODY:"ASPASIA"."SPA_OAUTH" already exists
ORA-31684: Object type PACKAGE_BODY:"ASPASIA"."SUMMARY_PDF_K" already exists
ORA-31684: Object type PACKAGE_BODY:"ASPASIA"."SUPPLIERS_DML_K" already exists
ORA-31684: Object type PACKAGE_BODY:"ASPASIA"."SUPPLIER_FORM_K" already exists
ORA-31684: Object type PACKAGE_BODY:"ASPASIA"."SUPPLIER_UTL_K" already exists
ORA-31684: Object type PACKAGE_BODY:"ASPASIA"."SYSTEM_IMAGES_DML_K" already exists
ORA-31684: Object type PACKAGE_BODY:"ASPASIA"."TASKS_K" already exists
ORA-31684: Object type PACKAGE_BODY:"ASPASIA"."TENANCY_REPORTS_K" already exists
ORA-31684: Object type PACKAGE_BODY:"ASPASIA"."TENANTS_DML_K" already exists
ORA-31684: Object type PACKAGE_BODY:"ASPASIA"."TEXT_MESSAGING_K" already exists
I've searched the forums and can't seem to find a solution as everyone just recommends TABLE_EXISTS_ACTION=REPLACE
I have also tried adding INCLUDE=PACKAGE_BODY to the impdb command but that still gives the same result and none of my packages have been updated
Thanks
Robert

Thanks for your reply, that would explain why it doesn't work :)
I am trying to update the test databases code with all the code from the development system (serveral hundred objects) ... I can just genereate and run a "drop <object_type> <object_name>" from user_objects on the test database first .... or just create scripts from user_source .... but it would be easier (and save a little time) just to export and import in one go

Impdp ORA-31684: Object type USER:"USERNAME" already exists

Hi,
I use expdp/impdp to duplicate one schema in a database like this:
expdp system/manager@DB SCHEMAS=SCHEMANAME
then I drop destination Schema like this
drop user SCHEMANAME_NEW cascade;
create user SCHEMANAME_NEW identified by PW default tablespace TABLESPACENAME;
and impdp like this
impdp system/manager@DB FULL=Y REMAP_SCHEMA=SCHEMANAME:SCHEMANAME_NEW
and I get this error:
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"SCHEMANAME_NEW" already exists
I know that the import was successful, but this error breaks my hudson build.
I tried to add exclude like this
impdp system/manager@DB FULL=Y REMAP_SCHEMA=SCHEMANAME:SCHEMANAME_NEW exclude=USER:\"=\'SCHEMANAME_NEW\'\"
I need to get rid of this error.
Thx

You get this error because you precreated the user. All you need to do is add
exclude=user
to either your expdp or impdp command. Or let impdp create the user for you. If you need it to have a different tablespace you can just use the
remap_tablespace=old_tbs:new_tbs
This should take care of the default tablespace on the create user command.
Dean

ORA-39083: Object type TRIGGER failed to create with error:

i m getting these two error when i import data using impdp.
ORA-39083: Object type TRIGGER failed to create with error:
ORA-00942: table or view does not exist
i have exported (expdp) data from production db, when i importing (impdp) the dump file to the test db i m geting the above two errors.
example:
ORA-39083: Object type TRIGGER failed to create with error:
ORA-00942: table or view does not exist
Failing sql is:
CREATE TRIGGER "NEEDLE"."CC_BCK_TRG" BEFORE INSERT OR UPDATE
ON NIIL.cc_bck_mgmt REFERENCING NEW AS NEW OLD AS OLD FOR EACH ROW
DECLARE
w_date DATE;
w_user VARCHAR2(10);
BEGIN
SELECT USER,SYSDATE INTO w_user,w_date FROM DUAL;
IF INSERTING THEN
:NEW.cretuser :=w_user;
:NEW.cretdate :=w_date;
END IF;
IF UPDATING THEN
:NEW.modiuser :=w_user;
:NEW.modidate :=w_date;
END IF;
END;
status of the above trigger in pro db is valid. and source table also exist even though i m getting error when i import
please suggest me...

perhaps you don't have table... (impdp created trigger before create table)
check about "NIIL.cc_bck_mgmt" table.
and then create it (trigger) manual ;)
Good Luck.

ORA-00902 when altering object types in a PL/SQL procedure

The types are altered to the same, so why gives it an error?
Here is how to see the error:
1.     Create the described objects below in an Oracle database (I used 8.1.7).
2.     Create a bpel-project using the procedure (via a database adapter), and deploy it.
3.     Check to see it works.
4.     Drop the object-types and create them again, and recompile the procedure.
5.     Activate the bpel-process again - and it will fail with error code 902: invalid datatype (and ORABPEL 11811).
CREATE OR REPLACE
TYPE T_TEST AS OBJECT
( AAR NUMBER,
BILAGNR NUMBER
CREATE OR REPLACE
TYPE T_TESTS
IS TABLE OF T_TEST
CREATE OR REPLACE
PROCEDURE TestAlterType (aType T_TESTS) IS
BEGIN
NULL;
END;
Regards,
Flemming

In such situation, I changed the BPEL wrapper package and made the BPLE generated wrapper package an Invalid Object (Ref below if needed). Now, I tested the Application from BPEL console. Then I got the Application Package is not exists. (Basically an error condition).I think now the Toplink cache gets disrupted. Then I corrected the BPEL generated Wrapper Package. Then executed the BPEL wrapper Package in database. Now I used BPEL console to test it again. It worked fine...
This way you can avoid Restarting the OPMN..
(One easy Step to Make Invalid Object)
1) Intentionally remove the ending ';' in the BPEL wrapper packages. And run the script in database. This Package body will become invalid.

Error in creation of Object Type from XML passed

Hi,
I am facing a problem creating a appropriate a object type for a XML.
Below are the details:
XML Passed
<mer_offer_action_data>
<form_id>
134039588
</form_id>
<action_cd>
OA
</action_cd>
<offer_decline_reason_cd>
</offer_decline_reason_cd>
<start_dt>
</start_dt>
<candidate>
<ds_prs_id>
109315
</ds_prs_id>
<ds_prs_id>
110534
</ds_prs_id>
<ds_prs_id>
110059
</ds_prs_id>
</candidate>
</mer_offer_action_data>
Types Declaration
+CREATE OR REPLACE type MER_OFF_CANDIDATE
AS
OBJECT
DS_PRS_ID NUMBER
CREATE OR REPLACE TYPE MER_OFF_CANDIDATE_t
AS
TABLE OF MER_OFF_CANDIDATE;
CREATE OR REPLACE type MER_OFFER_ACT_DATA
AS
OBJECT
FORM_ID NUMBER,
ACTION_CD VARCHAR2(6),
OFFER_DECLINE_REASON_CD VARCHAR2(6),
START_DT VARCHAR2(11),
CANDIDATE MER_OFF_CANDIDATE_t
CREATE OR REPLACE TYPE MER_OFFER_ACT_DATA_t
AS
TABLE OF MER_OFFER_ACT_DATA;
CREATE OR REPLACE type MER_OFFER_ACTION_DATA
AS
OBJECT
MER_OFF_ACT_DATA MER_OFFER_ACT_DATA_t
/+
My Declaration
+merOffActDataXML xmltype;
merOffActData MER_OFFER_ACTION_DATA := MER_OFFER_ACTION_DATA(MER_OFFER_ACT_DATA_t());+
Inside Pl/SQL block
+-- Converts XML data into user defined type for further processing of data
xmltype.toobject(merOffActDataXML,merOffActData);+
when I run the Pl/Sql block it gives me error
ORA-19031: XML element or attribute FORM_ID does not match any in type ORADBA.MER_OFFER_ACTION_DATA
which means the object type mapping is wrong
I would like to know whether the object type I had created is correct or not.
Thanks for your help
Beda

Bedabrata Patel wrote:
Below are the details:The details except for a description of the problem
I am facing a problem creating a appropriate a object type for a XML.And which error you are getting
Error in creation of Object Type http://download.oracle.com/docs/cd/E11882_01/server.112/e10880/toc.htm
And which version of Oracle you are getting the unknown error creating the unknown problem.

ORA-39112: Dependent object type

Similar Messages

Maybe you are looking for