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.

Similar Messages

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.

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 ?

Error -- ORA-08103: object no longer exists

Hi all,
i am getting this error during calling procedure from .Net code.
procedure is in the database.
any help appriciated

Connect directly to the DB where your procedure is located with the same user you use in .net to connect to DB
Create a temp table.
Instead of calling the procedure try selecting from the temp table.
If you can reach that temp table you should be able to see the procedure.
Make sure the procedure is compiled succesfully.It should be in valid state.
Cheers!!!
Bhushan

Object no longer exist

Hi All,
I am using select a query.
For eg.
select columns from a,b
where a.col1=b.col1
and a.col2=b.col2
and a.col3=b.col3
it throws "*ORA-08103: object no longer exists*" error for the first time.
But when i comment a join condition a.col2=b.col2 the query works fine.
When i run the same query again it throws "*ORA-00600: internal error code, arguments: [kcbgtcr_12], [1]* "
Please give some suggestion to solve this problem.
My DB version is -- Release 9.2.0.8.0

user13144724 wrote:
Please give some suggestion to solve this problem.a) Upgrade your database to a supported version (i.e. at least 10.2.0.4)
b) Post more information, like table structures, otherwise we won't have a clue
c) Raise your issue with Oracle via metalink as it's showing an internal error (although they'll probably tell you to upgrade first)

Bogus Object No Longer Exists error

I have a package which is reporting the error "ORA-08103: object no longer exists" on one of the SQL statements. I cannot figure out why though, because i checked all the objects which the SQL statement references and they are all still there, so i thought maybe it was a permissions error as some of the objects are cross-schema, so i tried logging in as the user who runs the job, and ran it myself interactively, and it worked fine.
Has anyone found this before, or know a fix? Thanks in advance,
Aaron.
(sorry if answered, i keep getting the error about an ESI error when i try to search).

Make sure that the privileges on all objects are granted EXPILICITLY to the user who is running the job (NOT thru a role). Privileges granted thru roles DO NOT cascade into a procedure. Each select, update, delete & insert required to execute the procedure must be granted explicitly. That could explain why it worked by running each step interactively.

"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

Object no longer exists

Dear Guru,
Below is the scenario for my problem encountered:
I have created a table EMP at HR schema.
Next, I created a view vw_EMP from EMP table at HR schema.
Next, I grant select privilege to UserA schema on vw_EMP
Next, I logon as UserA and create synonym as follow:
create synonym vw_EMP for hr.vw_EMP;
However, sometimes I do encounter the above error (object no longer exists) when userA trying to access vw_EMP. I am using Oracle 9i. Can you please advice what is the problem? How to overcome or any alternative to avoid this error?
Thank you.
Regards,
Kelly

Kelly,
Do you do any DDL on EMP table of HR schema?
I guess, if you do any DDL on EMP, you may loose all the grants, you may need to regarnt permission again.
Jaffar

Error :Object no longer exists

Hi All,
While executing an update statement on a table which has got more than 40 lac Records im getting an error as Object no longer exists.
i have created an index and tried.But the update is not working.Any suggestions.
Thanks in advance.

hi,
my best guess is that there is a trigger associated with your table and this trigger are using some of database objects which may have been dropped from the database. This is just an opinion since we do experience the same problem previously. Maybe you can show the error and the log perhaps?

IDCS4:JS- Error Number :30476 - Object no longer exists - Reg.

Dear All,
I created the EventListener for "before Print", Its working fine, but some times its shows the below attached Error.
"Error #:30476
Error String : The requested action could not be completed because the object no longer exist."
I used 3 scripts for "EvenListener"
(1) Main Script [before print]
(2) EventListener On
(3) EventListener Off
I placed the scripts in the below path
C:\Program Files\Common Files\Adobe\Startup Scripts CS4\Adobe InDesign\
I'm unable to find and solve this problem, Some times its working fine and some time its not working.
But this is not affected my hole project, while creating the ".ps" then before its showing the Error.
I checked so many ways and source code also, but I'm unable to solve this problem.
Please any one can suggest or give the solutions.
Thanks in advance
Regards
T.R.Harihara SudhaN

Thanks Jongware!
I can see that the code is working when integrated into my script, but I don't understand why it's working. Any explanation you can provide is greatly appreciated, or can you point me in the right direction to read up? (I'm a newbie).
I guess I was using cached variables?
The solution you provided, does it use a specific programming concept I can research more?
Thanks again!

ORA-04016 - Sequence no longer exists

Hi,
In the below scenario
1. All the sequences are dropped
2. When a process requires a value from a sequence and the sequence is not available, it is created and then a sequence.nextval is executed.
This statement is returning a ORA-04016 - Sequence <XXX> no longer exists.
Based on the following Metalink 1300837.1, we tried putting a sleep(5) between the sequence creation and fetch. The problem still occurs intermittently.
DB Version is 11.2.0.2 on Exadata with 6 nodes.
Even after an extensive search on the web, I could not find anything.
Is there any workaround for this or is there some DB patch to be applied?
Thanks

Have you tried sleeping for longer?
Alternative approaches that spring to mind are:
1) Ensure that the statements that create the sequence and those that subsequently use it are executed on the same node when executed in close succession.
2) Trap the error and retry in your code.
I'd be inclined to favour suggestion 1 if possible in your environment.
Is your code in PL/SQL?

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 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

ORA-23308 object does not exist or is invalid when DBMS_REPCAT.DROP_MASTER_

HI,
I am working on oracle 10g multimaster replication.
When i try to drop object from master site it gives me error like
SQL> BEGIN
2     DBMS_REPCAT.DROP_MASTER_REPOBJECT(
3       oname => '"AC_CHECK"',
4        type => 'TABLE',
5       sname => '"UMESH"',
6       drop_objects => FALSE);
7 END;
8 /
BEGIN
ERROR at line 1:
ORA-23308: object UMESH.AC_CHECK does not exist or is invalid
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.DBMS_REPCAT_UTL", line 2874
ORA-06512: at "SYS.DBMS_REPCAT_UTL", line 2849
ORA-06512: at "SYS.DBMS_REPCAT_UTL4", line 2926
ORA-06512: at "SYS.DBMS_REPCAT_UTL4", line 2727
ORA-06512: at "SYS.DBMS_REPCAT", line 643
ORA-06512: at line 2I can't find out the reason for it.
I more problum i am facing is when i stopped ( quiesced ) the replication activity.
my stored procedures on the master site start giving error like
sqlcode =*-23326* sqlerrm=*ORA-23326: object group "PUBLIC"."MYREPGRP" is quiesced*it means if i stop replication my database will not work while i am using asynchronous
replication.
i want my master database to work in any situation either replication is working or not.
Thnaks

Make sure the replication object you want to drop really exists.
check dba_repobject and dba_objects views.
select sname, oname, type, status, gname
from dba_repobject
where oname='AC_CHECK'
[pre]select owner, object_name, object_type
from dba_objects
where object_name='AC_CHECK'
Regarding ORA-23326.
This error occurs if the replication status is QUIESCED and you want to execute DML transaction against a replicated object.
While the replication status is QUIESCED no DML transactions are allowed against the replication objects.
Usually you want to stop the replication (suspend the master activity) if you want to perform maintenance activities (drop/add rep objects). This should be done in off hours and should be planned. You should be aware that no DML transactions are allowed while the master activity is suspended.
Also be aware that when you try to suspend the activity, the database will try to push and apply all the pending transactions. This may take some time (depends on the size of the transactions). So it is good practice to make sure there are no transactions that are waiting in DEFTRANDEST queue.
If you want to read more how the QUIESCED state affects the database activity, please refer to the following link:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14226/repmaster.htm#sthref260
Cheers,

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

Similar Messages

Maybe you are looking for