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

Similar Messages

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

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

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

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.

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

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.

Issue with Materialized View ORA-08103: object no longer exists

I have a materialized view which gets refreshed(COMPLETE Refresh) every 2 minutes. However there are few scheduled programs which queries this materialized view, some of the queries in the scheduled program take longer to run. When the materialized view refresh time overlaps with this query executing from the program i get this error: ORA-08103: object no longer exists.
I know that COMPLETE refresh doing TRUNCATE + INSERT is causing the issue, could someone suggest a workaround for this. But i need to do a COMPLETE refresh.

Why would a TRUNCATE cause an "object no longer exists" ?
Which job encounters this error ? The MV Refresh job or the programs that are querying the MV ? How does it resolve ? Automatically -- meaning that the next refresh/query does not raise the error ?

"ORA-21700: object does not exist or is marked for delete" select from ADT

Posted this in OLAP section as well, but since this is Object technology, I thought I would repeat it here. Sorry about the duplication.
BTW, I'm using Oracle9i 9.2.0.4.1.
I'm trying to create a script that can automate the process of generating abstract data types for use in an OLAP_TABLE function. I'm following the examples in the documentation. Everything runs great the FIRST time I run my script, but when I drop my types and re-create them, when I run the next SELECT statement against the OLAP_TABLE function, I get:
ERROR at line 1:
ORA-21700: object does not exist or is marked for delete
My script drops the ADTs before creating, but somehow they are not REALLY being dropped.
SET ECHO ON
SET SERVEROUT ON
DROP TYPE ts_table_6;
DROP TYPE ts_row6;
CREATE TYPE ts_row6 AS OBJECT(
CONJ2002 VARCHAR2(400),
CONJ2002_DATA number(16),
PERIOD VARCHAR2(10),
PERIOD_NAME VARCHAR2(20));
CREATE TYPE ts_table_6 AS TABLE OF ts_row6;
SELECT CONJ2002, period, period_name, conj2002_data FROM TABLE(OLAP_TABLE(
'REFVLMTA DURATION QUERY',
'ts_table_6',
'limit CONJ2002 to first 3',
'MEASURE CONJ2002_DATA from CONJ2002.DATA
DIMENSION CONJ2002 from CONJ2002
DIMENSION PERIOD from PERIOD WITH
ATTRIBUTE PERIOD_NAME from period.name'));
Again, it works the first time, but not the second time. I need to bump up the ADT names to ts_row7 and ts_table_7. SQL Plus says the types are being dropped.
Any ideas?
Dan Vlamis [email protected]

Hi Dan
What append if you do a connect between the DROP and the CREATE statements?
Chris

Start VM failed: Domain CCCCCCCC already exists with ID NNN

Hi,
I try to start an Oracle VM (currently stopped), the job related to the start action fails and the VM is not started.
The job log is:
Message: OVMAPI_6000E Internal Error: OVMAPI_5001E Job: 1427440127270/Start Vm: ora-aa-u004/Start Vm: ora-aa-u004, failed. Job Failure Event: 1427440128820/Server Async Command Failed/OVMEVT_00C014D_001 Async command failed on server: ovms-aa-us001.mgmt.mydom.com. Object: ora-aa-u004, PID: 32049, Server error: Command: ['xm', 'create', '/OVS/Repositories/0004fb0000030000b3397000b8916714/VirtualMachines/0004fb0000060000b17c866636533d63/vm.cfg'] failed (1): stderr: Error: Domain '0004fb0000060000b17c866636533d63' already exists with ID '199' stdout: Using config file "/OVS/Repositories/0004fb0000030000b3397000b8916714/VirtualMachines/0004fb0000060000b17c866636533d63/vm.cfg". , on server: ovms-aa-us001.mgmt.mydom.com, associated with object: 0004fb0000060000b17c866636533d63 [Fri Mar 27 08:08:48 CET 2015] [Fri Mar 27 08:08:59 CET 2015]
Previously I tried to migrate it to another Server of the same pool, the migration Job was successful, the VM resulted running, but actually it was cycling rebooting itself every minutes, after a few steps of the booting process. So I killed it (stopped it) and migrate it back (while in a stopping state) to the original server. When I start it on the original Server, I get the error above.
Please note that "xm list" on the Server doesn't show that this VM 0004fb0000060000b17c866636533d63 is running, nor that any VM with ID 199 is running.
Any suggestion? Thanks
Oscar

I don't think that advsiing to change the UUID inside the vm.cfg file is too beneficial. It might solve the immediate problem, but it won't make the "ghost" dom go away, which will need a OVMS boot to get rid off.
Further more it seems like Oracle has fixed this issue and will likely roll the patch out in an upcoming update to xen. Users who have OVM under CSI can request a patch mentioning this BUG: 20687187
I just received that patch and I will try that out tonight.
Cheers,
budy

ORA-27038: created file already exists

BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
CORE 11.2.0.1.0 Production
TNS for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
RMAN-03009: failure of backup command on t1 channel at 01/06/2013 21:24:49
ORA-19504: failed to create file "/oradbs/disk_bakup/amx53s/amx53s_arch_060113_1747"
ORA-27038: created file already exists
MY RMAN SCRIPT:
export ORACLE_HOME
ORACLE_SID=amx53s
export ORACLE_SID
date=`date '+%d%m%y_%H%M`
JOBLOG=/oradbs/disk_bakup/amx53s/amx53s.rman_$date.log
$ORACLE_HOME/bin/rman target / NOCATALOG log "$JOBLOG" <<EOF
run {
allocate channel t1 type disk;
backup
format '/oradbs/disk_bakup/amx53s/amx53s_offline_$date'
tag='amx53s_offline'
database;
backup
format '/oradbs/disk_bakup/amx53s/amx53s_arch_$date'
tag='amx53s_ARC_Tape_backup'
archivelog all delete input ;
backup current controlfile format '/oradbs/disk_bakup/amx53s/amx53s_Ctl_$date';
crosscheck backup;
release channel t1;
}

Hi,
format '/oradbs/disk_bakup/amx53s/amx53s_offline_$date'Can you modify output file format to amx53s_offline_%p_%s_$date to add piece number set number to make the outpfile name unique? Because here RMAN is creating a backup set with the name you are providing, and then for next backup set, it uses same name and thats why returns you error message of "file already exists". If you second backup set is created on next minute, file name will be different, but if in the same minute, file name will be same and this error will come.
Salman

Type already exists?

I am using Add-Type but I am getting the error:
Cannot add type. The type name 'TestSetup' already exists.
Can I tell if a type already exists and remove it so that I will not get this error?
Thank you.
Kevin Burton

This is way outside of my experience, so please ignore this if this isn't actually helpful.
I've been playing around with a way to test if a type has been added or not.
Here's my test code for adding a new type:
# Get list of currently loaded assemblies
$before = [appdomain]::currentdomain.getassemblies()
# Add a new type
# Example 1 from http://technet.microsoft.com/en-us/library/hh849914.aspx
$source = @"
public class BasicTest{ public static int Add(int a, int b) { return (a + b); } public int Multiply(int a, int b) { return (a * b); }}
Add-Type -TypeDefinition $source
# Get updated list of loaded assemblies
$after = [appdomain]::currentdomain.getassemblies()
# Console output with information about the differences in assemblies
Write-Host "Before: $($before.Count)"
Write-Host "After: $($after.Count)"
Compare-Object -ReferenceObject $before -DifferenceObject $after
Here I'm testing for the type, based on finding the class name:
# Class name to test for
$className = 'BasicTest'
# Get list of currently loaded assemblies
$loaded = [appdomain]::currentdomain.getassemblies()
$ErrorActionPreference = 'SilentlyContinue'
$foundType = $loaded | Where { ($_.GetExportedTypes()).Name -eq $className }
$ErrorActionPreference = 'Continue'
If ($foundType) { Write-Host 'Type found' }
Else { Write-Host 'Type not found' }
Perhaps I'm totally misunderstanding what you're trying to accomplish and this won't be helpful as all, but this was interesting nonetheless.
EDIT: Wow, the answer to this ends up being WAY easier than I made it. See below.
Don't retire TechNet! -
(Maybe there's still a chance for hope, over 12,225+ strong and growing)

ORA-08103: object no longer exists during APEX 2.2 to 3.0 upgrade

I am trying to upgrade an APEX 2.2 installation on 10.2.0.2 Enterprise Edition on SLES-10 with 400MB shared_pool and 1 GB sga_target. During the upgrade, the session crashes due to ORA-00600: internal error code, arguments: [ktspgfb-1]. I cannot drop the FLOWS_030000 user and 523 corrupt blocks in sys7.dbf including objects source$, argument$ and obj$. So far, I have restored the database and corrupted it 3 times. Each time, I redownloaded apex.zip from technet.oracle.com.
Here are the errors:
...PAGE 1300: Application Comparison
...PAGE 1301: Application Comparison Counts
...PAGE 1400: Report Layouts
...PAGE 1401: Create Report Layout
...PAGE 1402: Create Report Layout
...PAGE 1405: Edit Report Layout
...PAGE 1406: Create Report Query
...PAGE 1500: Application Builder
...PAGE 1550: User Interface Defaults
...PAGE 1552: UI Defaults - Column Defaults LOV
...PAGE 1553: UI Defaults - Column Defaults
...PAGE 1555: UI Defaults - Table Defaults
begin
ERROR at line 1:
ORA-08103: object no longer exists
ORA-06512: at "FLOWS_030000.WWV_FLOW_API", line 7733
ORA-06512: at line 18
ERROR:
ORA-00603: ORACLE server session terminated by fatal error
ERROR:
ORA-03114: not connected to ORACLE
SP2-0359: memory exhausted
Mon Apr 30 11:31:46 2007
Incremental checkpoint up to RBA [0x175.153ac.0], current log tail at RBA [0x175.2e77b.0]
Mon Apr 30 11:32:05 2007
Beginning log switch checkpoint up to RBA [0x176.2.10], SCN: 8173962186001
Thread 1 advanced to log sequence 374
Current log# 1 seq# 374 mem# 0: /lv01/oracle/dev10data/log01.dbf
Mon Apr 30 11:34:24 2007
Errors in file /lv01/oracle/dev10db/10.2.0/admin/dev10_plato/udump/dev10_ora_11590.trc:
ORA-00600: internal error code, arguments: [ktspgfb-1], [], [], [], [], [], [], []
Mon Apr 30 11:34:49 2007
Errors in file /lv01/oracle/dev10db/10.2.0/admin/dev10_plato/udump/dev10_ora_11590.trc:
ORA-00603: ORACLE server session terminated by fatal error
ORA-00600: internal error code, arguments: [ktspgfb-1], [], [], [], [], [], [], []
Mon Apr 30 11:35:02 2007
Errors in file /lv01/oracle/dev10db/10.2.0/admin/dev10_plato/bdump/dev10_pmon_7541.trc:
ORA-00600: internal error code, arguments: [ktspgfb-1], [], [], [], [], [], [], []
Mon Apr 30 11:35:15 2007
Errors in file /lv01/oracle/dev10db/10.2.0/admin/dev10_plato/bdump/dev10_pmon_7541.trc:
ORA-00600: internal error code, arguments: [ktspgfb-1], [], [], [], [], [], [], []
Mon Apr 30 11:37:18 2007
Completed checkpoint up to RBA [0x176.2.10], SCN: 8173962186001
Mon Apr 30 11:37:43 2007
Errors in file /lv01/oracle/dev10db/10.2.0/admin/dev10_plato/bdump/dev10_p000_12471.trc:
ORA-00600: internal error code, arguments: [ktspgfb-1], [], [], [], [], [], [], []
Mon Apr 30 11:37:54 2007
SMON: Parallel transaction recovery slave got internal error
SMON: Downgrading transaction recovery to serial
I now have 523 corrupt blocks in sys7.dbf:
DBVERIFY: Release 10.2.0.2.0 - Production on Mon Apr 30 11:50:21 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
DBVERIFY - Verification starting : FILE = /lv01/oracle/dev10data/sys7.dbf
Page 188161 is marked corrupt
Corrupt block relative dba: 0x01c2df01 (file 7, block 188161)
Completely zero block found during dbv:
Page 188162 is marked corrupt
Corrupt block relative dba: 0x01c2df02 (file 7, block 188162)
Completely zero block found during dbv:
Page 188163 is marked corrupt
Corrupt block relative dba: 0x01c2df03 (file 7, block 188163)
Completely zero block found during dbv:
Page 188164 is marked corrupt
Corrupt block relative dba: 0x01c2df04 (file 7, block 188164)
Completely zero block found during dbv:
Any ideas why this is happening? I see a number of current bugs for ORA-00600: ktspgfb-1, but most knowledge base articles refer to 9.0.1 or 9.2.

After upgrading to 10.2.0.3 and doubling the shared_pool_size and sga_target, I was able to upgrade to APEX 3.0 without errors.

ORA-08103: object no longer exists

Dear Experts,
I have a very tricky situation here.
A background job runs daily on our Production, which kinds of populates a lot of tables in another database (warehouse).
This morning, the job failed with an error: ORA-08103: object no longer exists
This error came while populating a table through a procedure.
I checked that the procedure and table both are in valid state and there are proper grants in place.
Also, we had faced the same problem few days back for the same table. We did not change anything. Simply re-ran the job and it went fine. Now also, we are re-running teh job and waiting to check if it goes fine.
Any ideaas why this error would come?
Thanks.

Leo, Thanks very much for your inputs. The proceudre does not use any views.
Here is the code:
PROCEDURE GS_SKILLS_SP
IS
err_num NUMBER:=0;
err_msg VARCHAR2(100):=null;
status VARCHAR2(1):='Y';
proc_name VARCHAR2(60):='GS_SKILLS_SP';
table_name VARCHAR2(100):='GS_SKILLS_DIM';
BEGIN
RPT_GS.Z_PRO_TRUNCATE_TABLE('GS_SKILLS_DIM');
INSERT INTO GS.GS_SKILLS_DIM
       (SKILL_ID,
    SKILL_CODE,
    SKILL_NAME,
    DESCRIPTION,
    PARENT_SKILL_ID,
    SKILL_PATH,
    IS_ACTIVE,
    PARENT_SKILL_PATH,
    PC_ID,
    PC_NAME,
    DIS_ID,
    DIS_NAME,
    LEVEL_ID,
    LEVEL_NAME)
SELECT SK.SKILL_ID,
    SK.SKILL_CODE,
    SK.SKILL_NAME,
    SK.DESCRIPTION,
    SK.PARENT_SKILL_ID,
    SK.SKILL_PATH,
    SK.IS_ACTIVE,
    SK.PARENT_SKILL_PATH,
    null,
    null,
    null,
    null,
    null,
    null
FROM    SKILLS_DIM    SK
WHERE UPPER(SK.SKILL_CODE) LIKE 'GS%'
AND SK.IS_ACTIVE = 'Y'
UNION
SELECT SK.SKILL_ID,
    SK.SKILL_CODE,
    SK.SKILL_NAME,
    SK.DESCRIPTION,
    SK.PARENT_SKILL_ID,
    SK.SKILL_PATH,
    SK.IS_ACTIVE,
    SK.PARENT_SKILL_PATH,
    SK_ASSOC.PC_ID,
    SK_ASSOC.PC_NAME,
    SK_ASSOC.DIS_ID,
    SK_ASSOC.DIS_NAME,
    SK_ASSOC.LEVEL_ID,
        SK_ASSOC.LEVEL_NAME
FROM    SKILLS_DIM        SK,
    SKILLS_OBS_ASSOC_DIM SK_ASSOC
WHERE SK.SKILL_ID=SK_ASSOC.SKILL_ID
AND UPPER(SK.SKILL_CODE) LIKE 'GS%'
and sk.is_active='Y'
AND SK_ASSOC.LOB_NAME = 'Global Services' ;
COMMIT;
INSERT INTO GS.GS_SKILLS_DIM
       (SKILL_ID,
    SKILL_CODE,
    SKILL_NAME,
    DESCRIPTION,
    PARENT_SKILL_ID,
    SKILL_PATH,
    IS_ACTIVE,
    PARENT_SKILL_PATH,
    PC_ID,
    PC_NAME,
    DIS_ID,
    DIS_NAME,
    LEVEL_ID,
    LEVEL_NAME)
SELECT SK.SKILL_ID,
    SK.SKILL_CODE,
    SK.SKILL_NAME,
    SK.DESCRIPTION,
    SK.PARENT_SKILL_ID,
    SK.SKILL_PATH,
    SK.IS_ACTIVE,
    SK.PARENT_SKILL_PATH,
    null,
    null,
    null,
    null,
    null,
    null
FROM    SKILLS_DIM    SK
/*WHERE UPPER(SK.SKILL_CODE) LIKE 'GS%'
AND SK.IS_ACTIVE = 'Y'*/
/*changed on 16/04/2008 for RQ34634(PRIME168) */
where sk.is_active='Y'
and exists(select 1 from GS.GS_RES_PROFICIENCY_DIM gs_sk where gs_sk.skill_code=sk.skill_code)
and not exists(select 1 from gs.gs_skills_dim rpt_sk where rpt_sk.skill_code=sk.skill_code)
UNION
SELECT SK.SKILL_ID,
    SK.SKILL_CODE,
    SK.SKILL_NAME,
    SK.DESCRIPTION,
    SK.PARENT_SKILL_ID,
    SK.SKILL_PATH,
    SK.IS_ACTIVE,
    SK.PARENT_SKILL_PATH,
    SK_ASSOC.PC_ID,
    SK_ASSOC.PC_NAME,
    SK_ASSOC.DIS_ID,
    SK_ASSOC.DIS_NAME,
    SK_ASSOC.LEVEL_ID,
        SK_ASSOC.LEVEL_NAME
FROM    SKILLS_DIM        SK,
    SKILLS_OBS_ASSOC_DIM SK_ASSOC
WHERE SK.SKILL_ID=SK_ASSOC.SKILL_ID
/*changed on 16/04/2008 for RQ34634(PRIME168) */
and sk.is_active='Y'
and exists(select 1 from GS.GS_RES_PROFICIENCY_DIM gs_sk where gs_sk.skill_code=sk.skill_code)
and not exists(select 1 from gs.gs_skills_dim rpt_sk where rpt_sk.skill_code=sk.skill_code)
AND SK_ASSOC.LOB_NAME = 'Global' ;
COMMIT;
IF (err_num = 0) then
   INSERT INTO GS_ERROR
             (PROC_NAME,
          TABLE_NAME,
              ERR_CODE,
              ERR_MSG,
              CREATED_DATE,
              STATUS)
              VALUES(proc_name,table_name,err_num,err_msg,SYSDATE,status);
    COMMIT;
END IF;
EXCEPTION
WHEN OTHERS THEN
      err_num:=SQLCODE;
      err_msg:=SUBSTR(SQLERRM,1,100);
      status:='N';
      ROLLBACK;
      INSERT INTO GS_ERROR
             (PROC_NAME,
          TABLE_NAME,
              ERR_CODE,
              ERR_MSG,
              CREATED_DATE,
              STATUS)
              VALUES(proc_name,table_name,err_num,err_msg,SYSDATE,status);
      COMMIT;
END GS_SKILLS_SP;

Java.sql.SQLException: ORA-08103: object no longer exists

hi, Everyone:
i want to insert one colume to a temp table,
so i did the following
1: drop the table
2: recreate the table with the new colume in it.
we i run my application, there is a
"java sql exception ORA-08103: object no
longer exists ". looks like the table
doesn't exist in database any more. but
it is really still there.
thanks
hongjie
null

I was able to resolve this error by using on commit preserve rows, instead of on commit delete.

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

Similar Messages

Maybe you are looking for