Truncate table ORA-02266

Hi,
when I truncate some tables I have ORA-02266 error. Any Idea or solution ?
Many thanks.

Hi,
>>1-Is there any way to disable all primary key constarints and all dependencies on all >>tables of a schema and after operation turn back ?
See this example below:
SQL> alter table aet_em disable constraints aetem_pk;
alter table aet_em disable constraints aetem_pk
ERROR at line 1:
ORA-02297: cannot disable constraint (SGMS.AETEM_PK) - dependencies exist
SQL> select table_name,constraint_name,status from user_constraints where r_constraint_name='AETEM_PK';
TABLE_NAME                     CONSTRAINT_NAME                STATUS
AET_IEM                        AETIEM_FK2                     ENABLED
SQL> alter table aet_em disable constraints aetem_pk cascade;
Table altered.
SQL> select table_name,constraint_name,status from user_constraints where r_constraint_name='AETEM_PK';
TABLE_NAME                     CONSTRAINT_NAME                STATUS
AET_IEM                        AETIEM_FK2                     DISABLED
SQL>After performed this operation, you need to enable the foreign keys manually.
Cheers

Similar Messages

Problem with truncate table in procedure ora -00054

hi do anybody know where is mistake ???
the procedure has problem with truncate table
ora - 00054: resource busy and acquire with NOWAIT specified
ora - 06512 at "POVAPSYS.HMAN_P_REFRESH", line 6
ora - 06512 at "POVAPSYS.POVAPSYS", line 6
ora - 06512 at line 1
this is my procedure....
AS
BEGIN
execute immediate 'TRUNCATE TABLE hman_t_max';
INSERT INTO hman_t_max SELECT * FROM hman_v_max;
COMMIT;
END;

2.MAKE SURE THAT OTHER THAN YOU ANYBODY IS TRYING TO
COMPILE AND RUN THE PROCEDUREShould he make sure that anybody is running the procedure?
3.MAKE SURE THAT ANY PARALLEL QUERY IS RUNNING IN THE
SERVER SIDE,THATS KEEPS THE RESOURCE BUSYShould he make sure any parallel query is running in the server side to keep the resource busy?
Gita,
I COULDN'T RESIST HAVING ONE SUGGESTION FOR YOU. Please look at the impact of your English in the reply before posting. Check if that sends reverse message!
Cheers
Sarma.

How to truncate the Dimensions: ORA-02266

I simply want to truncate the dimensions of star schema.
First I truncate the fact table with Sql, that works.
Then truncating a dimension fails with this error:
Truncate table fcDwh.DIM_DEPS
Error report:
SQL Error: ORA-02266: unique/primary keys in table referenced by enabled foreign keys
02266. 00000 - "unique/primary keys in table referenced by enabled foreign keys"
*Cause: An attempt was made to truncate a table with unique or
primary keys referenced by foreign keys enabled in another table.
Other operations not allowed are dropping/truncating a partition of a
partitioned table or an ALTER TABLE EXCHANGE PARTITION.
*Action: Before performing the above operations the table, disable the
foreign key constraints in other tables. You can see what
constraints are referencing a table by issuing the following
command:
SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = "tabnam";
If the fact table is already empty, I don't violate any foreign key constraint.
Or am I wrong with this?
The constraints below:
OWNER CONSTRAINT_NAME CONSTRAINT_TYPE TABLE_NAME SEARCH_CONDITION R_OWNER R_CONSTRAINT_NAME DELETE_RULE STATUS DEFERRABLE DEFERRED VALIDATED GENERATED BAD RELY LAST_CHANGE INDEX_OWNER INDEX_NAME INVALID VIEW_RELATED
FCDWH SYS_C0019008 C DIM_DEPS "DIMENSION_KEY" IS NOT NULL ENABLED NOT DEFERRABLE IMMEDIATE VALIDATED GENERATED NAME 07-SEP-07
FCDWH DIM_DEPS_DIMENSION_KEY_PK P DIM_DEPS ENABLED NOT DEFERRABLE IMMEDIATE VALIDATED USER NAME 07-SEP-07 FCDWH DIM_DEPS_DIMENSION_KEY_PK

Try using NumberFormat class:
NumberFormat currency = NumberFormat.getNumberInstance();
currency.setMinimumFractionDigits(2);
currency.setMaximumFractionDigits(2);
String s = currency.format(anyFloatValue);
..

Raising ora-01426 error while truncating table

Hi,
We have a procedure which executes in the following process for few set of tabls
1. disables the constraints
2. truncating the tables
3. enabling the constraints
but after processing for 5 tables, while truncating the error throws
BEGIN <procedure name >; END;
ERROR at line 1:
ORA-01426: numeric overflow
ORA-06512: at "<procedurename> ", line 33
ORA-06512: at line 1
this line 33 point to execute immeidate 'truncate table < table name>
Can i know what would be reason for throwing ' numeric overflow' error while truncating table..
Thanks in advance

user9080289 wrote:
thanks.
My oracle verision is 11gThen you could have the bug described there. Follow the instruction how to workaround (monitoring flush, set stats to low value) or apply the patch #8226471.
Nicolas.

ORA-02266: unique/primary keys in table referenced by enabled foreign keys

Hi,
I am trying to delete data from a table by dropping a partition. I have identified all the child tables by running the following command.
select 'select count(*) from '||table_name||' where employee_id = 100;'
from dba_constraints
where constraint_type='R'
and r_constraint_name in
(select constraint_name from dba_constraints
where constraint_type in ('P','U') and table_name='EMPLOYEE);
'SELECTCOUNT(*)FROM'||TABLE_NAME||'WHEREEMPLOYEE_ID_ID=100;'
select count(*) from PT_ORDERS where employee_id = 100;
select count(*) from PT_DEP where employee_id = 100;
select count(*) from PT_SKILLSET where employee_id = 100;
I dropped the partition for employee_id 100 in all of the child tables. The select count(*) returns 0 rows for each of the above.
When I try to run the below command on the EMPLOYEE table, I get 'ORA-02266: unique/primary keys in table referenced by enabled foreign keys'.
alter table EMPLOYEE drop partition EMP_ID_100;
I cant see why I am unable to drop this partition now as there is now child data in any of the referenced tables. Any suggestions or help on this would be greatly appreciated.
Thanks.
Rgs,
Rob

You should disable foreign key constraints first and drop partition. Deletion of rows or dropping partitions in childs don't work in this case
as you have the global dependency:
<PRE>
SQL> create table scott.t (x int primary key, y int)
2 partition by list (y) (
3 partition p_1 values(1), partition p_2 values(2))
4 /
Table created.
SQL> create table scott.t_c (x int references scott.t(x), y int)
2 partition by list (y) (
3 partition p_1 values(1), partition p_2 values(2))
4 /
Table created.
SQL> insert into scott.t values(1,1)
2 /
1 row created.
SQL> insert into scott.t values(2,2)
2 /
1 row created.
SQL> insert into scott.t_c values(1,1)
2 /
1 row created.
SQL> insert into scott.t_c values(2,2)
2 /
1 row created.
SQL> commit;
Commit complete.
SQL> alter table scott.t_c drop partition p_2;
Table altered.
SQL> alter table scott.t drop partition p_2;
alter table scott.t drop partition p_2
ERROR at line 1:
ORA-02266: unique/primary keys in table referenced by enabled foreign keys
SQL> select constraint_name from dba_constraints
2 where owner = 'SCOTT' and constraint_type = 'P'
3 and table_name = 'T';
CONSTRAINT_NAME
SYS_C0011058
SQL> select constraint_name from dba_constraints
2 where owner = 'SCOTT' and constraint_type = 'R'
3 and r_constraint_name = 'SYS_C0011058';
CONSTRAINT_NAME
SYS_C0011059
SQL> alter table scott.t_c disable constraint SYS_C0011059;
Table altered.
SQL> alter table scott.t drop partition p_2;
Table altered.
SQL> alter table scott.t_c enable novalidate constraint SYS_C0011059;
Table altered.
</PRE>
I guess you should consider such option as Referencial partitioning (with some restrictions).
Best wishes,
Dmitry.

ORA-01502: Index or Partition is in unusable status. while truncating table

Hi All,
One of our Devlopers compalined that he is getting ORA-01502 : Index or partition is unusable status while truncating the a table in our Dataware house production database. He is using the following commands.
Alter index <index_name> unusable;
Truncate table <table_name> ;
He is running a scripts to truncate each table and ecah time he is passing the table name as an input parameter to script. He is using same method to truncate four tables each having a BITMAP and a REGULAR index. For two tables every thing is working fine, but for other two tables the he is getting ORA-01502 for BITMAP indexes. It a weekly process and every week he is getting the same issue. I checkd the Index status, they are in valid status only.
For a work around I have created a table with BITMAP and regular index in our dev database. made the indexes unusable, checked their status. I truncated the table. Importent thing here is the Indexes are becoming vaild when I truncate the table.
I suspect that my devloper's Indexes were already in unusable status (before he use the command ALTER INDEX), when he truncated the table, oracle trying to validate the index and throwing the error ORA-01502 because the Indexes are in unusabel statsu for a while.
I tried searching for the mechanism of truncate table command and its effect on Indexes. But I did not find any luck, no one is speaking about index when truncating the table. Can any one please help me????
Sorry for lengthy post. Any help is greatly appriciated and I thank every one in advance.

DDL for Indexes getting ORA-01502 error
CREATE BITMAP INDEX DWHMGR.ACT_TXN_LN_STG_01_XN3 ON DWHMGR.ACCT_TXN_LINE_TERM_BAL_STG_01 (TERM_BAL_CD ASC) TABLESPACE "BALFD_INX_04" NOLOGGING PCTFREE 1 INITRANS 2 MAXTRANS 255 STORAGE
( INITIAL 8M NEXT 8M MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT );
CREATE BITMAP INDEX DWHMGR.ACCT_TERM_BAL_STG_01_XN3 ON DWHMGR.ACCT_TERM_BAL_STG_01 TERM_BAL_CD ASC) TABLESPACE "BALFD_INX_04" NOLOGGING PCTFREE 1 INITRANS 2 MAXTRANS 255 STORAGE
( INITIAL 8M NEXT 8M MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT );
Indexes that have no issues.
CREATE INDEX DWHMGR.ACCT_TERM_BAL_STG_01_XN2 ON DWHMGR.ACCT_TERM_BAL_STG_01 (ACCT_REF_NB ASC) TABLESPACE "BALFD_INX_04" NOLOGGING PCTFREE 1 INITRANS 2 MAXTRANS 255 STORAGE (INITIAL 8M
NEXT 8M MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT );
CREATE BITMAP INDEX DWHMGR.ACCT_PRC_STG_01_XN1 ON DWHMGR.ACCT_PRC_STG_01 (ACCT_ORG_CD ASC) TABLESPACE "BALFD_INX_04" NOLOGGING PCTFREE 1 INITRANS 2 MAXTRANS 255 STORAGE ( INITIAL 8M
NEXT 8M MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT );
Please look at the DDL of the indexes and let me know if you need any other information.

Stuck with ORA-02266...even through I've already disabled the FK constraints...?

I'm working to help some people on a structure I really don't know much about...they're trying to truncate the table.
When trying to truncate table1:
I got the ORA-02266: unique/primary keys in table referenced by enabled foreign keys error,
I went through and have disabled every FK on the table....so, I'm a bit puzzled why I keep getting the same error.
I was thinking of disabling the PK...to see if for some reason that was holding things back (so far out of a bunch of tables, this is the ONLY table not responding to having all FK's disabled).
However, when I try to disable the PK I get:
ORA-02297: cannot disable constraint (owner.table1_pk) - dependencies exist
I've been looking around, and was going to maybe try the disable constraint with the cascade option, but, I'm not familiar with the cascade in this context...what will this do?
Will it cause any problems with this or other tables when I try to re-enable the PK constraint on table1?
Thank you in advance,
cayenne

Thank you, this looks like I'm on the path to untangling this mess.
One question, please...would disabling the PK constraint with the CASCASE clause take care of this? What would this do exactly...disable the other tables' FK constraints..?
If so, would it re-enable them when I re-enable this PK constraint?
Thank you,
C

Truncating table throws error although no child record exists

I have 2 tables
table_master (This is master table)
table_child (This is child table)
truncate table table_child ;
the above executes properly
BUT
truncate table table_master;
ERROR at line 1:
ORA-02266: unique/primary keys in table referenced by enabled foreign keys
Although there is no child record even though the above error is occuring.Please sove my problem.

Hi,
>>lthough there is no child record even though the above error is occuring.Please sove my problem.
In fact, doesn't matter if child table contain or not data.
LEGATTI> create table a (id number primary key);
Table created.
LEGATTI> create table b (id number constraint fk_b_a references a);
Table created.
LEGATTI> truncate table a;
truncate table a
ERROR at line 1:
ORA-02266: unique/primary keys in table referenced by enabled foreign keys
LEGATTI> alter table b disable constraint fk_b_a;
Table altered.
LEGATTI> truncate table a;
Table truncated.
-- In addition, in order to drop the parent table, just disable the constraint's child table is not sufficient.
LEGATTI> select constraint_name,status from user_constraints where table_name='B';
CONSTRAINT_NAME STATUS
FK_B_A DISABLED
LEGATTI> drop table a;
drop table a
ERROR at line 1:
ORA-02449: unique/primary keys in table referenced by foreign keys
LEGATTI> drop table a cascade constraints;
Table dropped.
LEGATTI> select * from user_constraints where table_name='B';
no rows selectedCheers
Legatti

ORA-02266

Hello All,
I am trying to truncate a table.
I am wondering following message.
ORA-02266: unique/primary keys in table referenced by enabled foreign keysAny help?
Thanks,
S!G

Sea!Gull,
TRUNCATE table operation does not enforce for foreign key constraint at data or row level. Even if there are no rows in any table (parent and child) truncate on parent will give this error a long as the FK constraint exists and is enabled.
You have to disable the FK constraints in the "child/detail" table(s), in order to truncate "parent/master" table.
Think about it, if TRUNCATE table enforced FK constraints at row/data level, it will not be any faster than DELETE statement. TRUNCATE bypasses lots of internal processes like FK checks, row level logging etc.
SQL> drop table d;
Table dropped.
SQL> drop table m;
Table dropped.
SQL> create table m (c int primary key);
Table created.
SQL> create table d (c1 int, constraint d_fk foreign key (c1) references m(c));
Table created.
SQL> select * from m;
no rows selected
SQL> select * from d;
no rows selected
SQL> truncate table m;
truncate table m
ERROR at line 1:
ORA-02266: unique/primary keys in table referenced by enabled foreign keys
SQL> alter table d disable constraint d_fk ;
Table altered.
SQL> truncate table m;
Table truncated.
SQL> alter table d enable constraint d_fk ;
Table altered.
SQL> truncate table m;
truncate table m
ERROR at line 1:
ORA-02266: unique/primary keys in table referenced by enabled foreign keys
SQL> Regards,
Sudhakar B.
Edited by: user517570 on Jan 6, 2010 9:57 AM (Added the code tag)

Truncate table and materialized view log

I user oracle 10 R2
I have a table and on that table a materialized view log.
I execute in a pl/sql procedure:
1) execute immediate('drop materialized view log on tab1');
then:
2) execute immediate('truncate table tab1');
3) Now I insert a lot of records in tab1
4) execute immediate('create materialized view log on tab1 WITH rowid INCLUDING NEW VALUES');
When I create the materialized view log I recieved this message:
ora32321: refresh fast on tab2 unsupported after detail table truncate
Why?

Refresh fast after truncate operation on container table is not supported, regardless the container table is or is not partitioned.
Perform a refresh complete.
ORA-32321 :
Cause:     A detail table has been truncated and no materialized view
     supports fast refersh after a detail table has been truncated
Action:     Use REFRESH COMPLETE. Note: you can determine why your
     materialized view does not support fast refresh after TRUNCATE
     using the DBMS_MVIEW.EXPLAIN_MV() API.

TRUNCATE TABLE does not work in PL/SQL - Why?

Hey there!
Is there any issue with truncate table not working inside an PL/SQL package?
For example this function:
PROCEDURE FLUSH_TABLE(vi_table_name VARCHAR2) IS
vn_table_name VARCHAR2(30);
BEGIN
vn_table_name := UPPER(LTRIM(RTRIM(vi_table_name)));
TRUNCATE TABLE vn_table_name;
END FLUSH_TABLE;
returns the following error msg:
Error: PLS-00103: Encountered the symbol "TABLE" when expecting one of the following:
:= . ( @ % ;
The symbol ":= was inserted before "TABLE" to continue.
Line: 5926
Text: TRUNCATE TABLE VN_TABLE_NAME;
Can somebody explain me the problem here? In my point of view, the error msg is not quite right ;)
Regards,
Thomas

> I just think the error msg is confusing
When you looked for TRUNCATE in the PL/SQL reference you might have noticed that the PL/SQL language has no TRUNCATE keyword. The error message indicates that syntactically the code appears to be some sort of variable assignment but has an extra keyword and no assignment operator. You would get the same message for any similar string of unrecognised keywords:
SQL> BEGIN
2      TRUNCATE TABLE emp;
3 END;
4 /
    TRUNCATE TABLE emp;
ERROR at line 2:
ORA-06550: line 2, column 14:
PLS-00103: Encountered the symbol "TABLE" when expecting one of the following:
:= . ( @ % ;
The symbol ":= was inserted before "TABLE" to continue.
SQL> BEGIN
2      TRANSMOGRIFY TABLE emp;
3 END;
4 /
    TRANSMOGRIFY TABLE emp;
ERROR at line 2:
ORA-06550: line 2, column 18:
PLS-00103: Encountered the symbol "TABLE" when expecting one of the following:
:= . ( @ % ;
The symbol ":= was inserted before "TABLE" to continue.
SQL> BEGIN
2      MORE TEA VICAR;
3 END;
4 /
    MORE TEA VICAR;
ERROR at line 2:
ORA-06550: line 2, column 10:
PLS-00103: Encountered the symbol "TEA" when expecting one of the following:
:= . ( @ % ;

ORA-02266: unique/primary keys - error while using Exchange Partition

Hi All,
While using EXCHANGE PARTITION statement as given below,
ALTER TABLE SOURCE_TABLE EXCHANGE PARTITION PRT_EXCG_PRTN WITH TABLE TARGET_TABLE
we are getting this error,
ORA-02266: unique/primary keys in table referenced by enabled foreign keys
However, there are no tables have foreign keys referring this TARGET_TABLE, we checked this by referring
USER_CONSTRAINTS table, it has only primary key and NOT NULL constraints.
SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME like 'TARGET_TABLE';
We are using the following version,
Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
PL/SQL Release 9.2.0.6.0 - Production
CORE 9.2.0.6.0 Production
TNS for IBM/AIX RISC System/6000: Version 9.2.0.6.0 - Production
NLSRTL Version 9.2.0.6.0 - Production
Is it due to any error in our end or it could be a bug in Oracle and should we go for any patch updation ?
Please guide us to resolve this error as soon as possible, thank you.
Regards,
Deva

*** Duplicate Post ***
Please Ignore.

Error when trying to truncate table from within PL/SQL

Hello.....
Does anyone know why I get an error when trying to execute the following command from within PL/SQL?
truncate table event;
The error is as follows:
ORA-06550: line 20, column 14:
PLS-00103: Encountered the symbol "TABLE" when expecting one of the following:
:= . ( @ % ;
The symbol ":= was inserted before "TABLE" to continue.

And as a DDL, it does a COMMIT just before it runs. Whether you want a COMMIT or not.
And with all the locking and serialization issues associated with a DDL.

Flashback and truncate table in 11gR2

Hi,
From what I can gather, flashback database is the only flashback operation that can undo a table truncate. A truncate table operation cannot be rolled back, because it does not produce the undo data necessary for undo based flashback operations like Flashback query, version, transaction/backup and table.
Is this assessment correct?
Thanks.

Pal wrote:
Thanks for reply. I hope it's ok to add a couple more related questions:
SQL> select current_scn from v$database;
1088080
SQL> connect hr/hr
SQL> truncate table test_data;
SQL> select * from test_data as of SCN 1088080;
ORA-01466: unable to read data - table definition has changedYes, that's correct Pal. The reason is that with any DDL , the structure/definition of the table would be changed and Flashback Query won't be allowed on such table.
I cannot use Flashback Query, however, just reading http://ocpdba.wordpress.com/2009/10/19/reversing-the-effect-of-a-truncate-table-in-oracle-11gr2 which demonstrates how to use Flashback Data Archive and Flashback Query to reverse a table truncate operation.
Why does Flashback Data Archive allow me to use Flashback Query past DDL operations?Please see,
http://download.oracle.com/docs/cd/E11882_01/appdev.112/e17125/adfns_flashback.htm#BJFJHDAG
Actually, even with the Flasback data archive too, you can't do anything if the table structure is modified by a command whose effect it can't tolerate. In 11.2, what is given is that you can dissociate your table from the Flashback DAta archive using the package DBMS_FLASHBACK_ARCHIVE.DISASSOCIATE_FBA , do the changes on both target and archive table and then reassociate . Oracle does makes a note in this operation that assume no aboslute guarantee in the data's accuracy if you would do this procedure.
If I do not have Flashback Data Archive enabled on a table, how can I determine the SCN to undo a truncate table using Flashback database or TSPITR?You would need to mine the logfile using the logminer .
HTH
Aman....

ORA-00604 error occured at recursive level1,ORA-20123 Insufficient privileges: you cannot drop table cls_lrn_tab_unique TABLE,ORA-06512

Dear All,
I created one table like
create table cls_lrn_tab_unique (F_no number unique UK_F_NO );
after performing some operations I want to delete the same.
At that time i got following error. Please help me and tell what is the reason for the error.
ORA-00604 error occured at recursive level1
ORA-20123 Insufficient privileges: you cannot drop table cls_lrn_tab_unique TABLE,
ORA-06512 at line no 2
Thanks and Regards
Prasad

26bffcad-f9a2-4dcf-afa0-e1e33d0281bf wrote:
Dear All,
I created one table like
create table cls_lrn_tab_unique (F_no number unique UK_F_NO );
after performing some operations I want to delete the same.
At that time i got following error. Please help me and tell what is the reason for the error.
ORA-00604 error occured at recursive level1
ORA-20123 Insufficient privileges: you cannot drop table cls_lrn_tab_unique TABLE,
ORA-06512 at line no 2
Thanks and Regards
Prasad
ORA-20123 is a localized/customized error code & message; therefore any solution depends upon what is unique inside your DB now.
I suspect that some sort of TRIGGER exists, which throws posted error, but this is just idle speculation on my part.
How do I ask a question on the forums?
https://forums.oracle.com/message/9362002#9362002

Truncate table ORA-02266

Similar Messages

Maybe you are looking for