Deadlocks with ALTER TABLE DISABLE CONSTRAINT

Hello,
We're deleting millions of redundant rows from a particular table in our live 10g database. This is being done online because the downtime would be unacceptable. The table in question has 30 child tables, so for speed I am disabling the foreign keys using ALTER TABLE DISABLE CONSTRAINT before the deletion (we haven't had any constraint violations for ages). Without this, deletion takes about 1 second per row i.e. a very long time.
However, we're finding that ALTER TABLE DISABLE CONSTRAINT often reports ORA-00060: deadlock detected. This is causing problems with the live system. Can anyone think of the reason why a deadlock might occur in this situation and what we could do to prevent it happening? Note that any solution has to be doable without downtime unless it takes less than 30 minutes.
Thanks a lot
Ed
Edited by: edwiles on Feb 4, 2009 6:02 AM

look suggestions in the similar thread:
Re: Deadlock when deleting a not linked data record in a parent table

Similar Messages

ALTER TABLE ENABLE CONSTRAINT FK is very slow

Hello,
The following enable constraint command takes around (15min to be completed)
ALTER TABLE table_name ENABLE CONSTRAINT fk_constraint_name ;table_name: (~133 Millions rows)
Any idea why it takes long to be completed? and what could be done to improve the performance?
Thanks in advance

Enabling a foreign means the database has to check the existence of each value in the child table column against the key in the parent table. Now you say,
The following enable constraint command takes around (15min to be completed)
table_name: (~133 Millions rows)In other words, ithe database is validating about ten million rows a minute. That doesn't seem too shabby. So what would you consider to be a reasonable amount of time to accomplish this task?
Bear in mind the golden rule of tuning: ye cannae break the laws of physics. Acting on large volumes of data must necessarily take some time. You must be realistic.
Also, why is it a problem? This is the sort of task which ought to be undertaken only occasionally. If you're doing it often enough that fifteen nminutes is unacceptably long perhaps you should reconsider why you're disabling the constraint. See whether there's another way to achieve whatever it is you're doing. After all, the most effective way to reduce something's elapsed time is to avoid doing that thing at all.
Cheers, APC

Can't import DDL file that has alter table rename constraint

Hi:
Version 3.1.0.691 on Windows 7 Enterprise 64-bit SP1
I'm trying to import a DDL file with syntax similar to what's below. The <name> notes that I've replaced the actual names for obfuscation purposes.; the real names are in the script.
ALTER TABLE <name>
RENAME CONSTRAINT SYS_C0041150
TO <name2>_CK;
ALTER TABLE <name>
RENAME CONSTRAINT AVCON_1281559518_ACTIV_022
TO <name2>_CK;
I get the following error:
Oracle SQL Developer Data Modeler 3.1.0.691
Oracle SQL Developer Data Modeler Import Log
Date and Time: 2012-01-13 16:29:05 PST
Design Name: <name>
RDBMS : Oracle Database 11g
          All Statements:           819
          Imported Statements:      0
          Failed Statements:           0
          Not Recognized Statements:      819
<<<<< Not Recognized >>>>>
ALTER TABLE <name>
RENAME CONSTRAINT SYS_<name>
TO <name2>_CK
ALTER TABLE <name>
RENAME CONSTRAINT AVCON_1281559518_QVI_A_000
TO <name2>_CK
Thanks for any help you can provide.
Doc

Hi:
The file was indeed comprised of just alter statements. As a test, I trimmed the file down to just one alter statement:
ALTER TABLE <name> RENAME CONSTRAINT SYS_C0041413 TO <name2>_CK;
The output file contained exactly the following, where the <<BEGIN OF FILE>> and <<END OF FILE>> were simply added here for clarity. There was no section called
<<<<< ERRORS >>>>> and the ddl file contained no create table statements.
<<BEGIN OF FILE>>
Oracle SQL Developer Data Modeler 3.1.0.691
Oracle SQL Developer Data Modeler Import Log
Date and Time: 2012-01-16 10:16:42 PST
Design Name: <name>
RDBMS : Oracle Database 11g
          All Statements:           1
          Imported Statements:      0
          Failed Statements:           0
          Not Recognized Statements:      1
<<<<< Not Recognized >>>>>
ALTER TABLE <name> RENAME CONSTRAINT SYS_C0041413 TO <name2>_CK
<<END OF FILE>>
Other info.
When I do an model import, none of the existing check constraint names get captured. Also, if I add names afterwards to two separates models via DM and then compare them. The output DDL shows a drop of the target constraint referencing its name, but the recreation of the not null constraint doesnt reference the source constraint name set for it manually in DM. Here's the example I did and the output ddl.
ALTER TABLE <name>
DROP CONSTRAINT SYS_C0041413
ALTER TABLE <name>
MODIFY ( <column_name> NOT NULL )
That last line should have read as follows due to the constraint_name I added for it in DM.
ALTER TABLE <name>
MODIFY (<column_name> CONSTRAINT <name2>_CK NOT NULL);
In the example directly above, <name2>_CK is the name I explicity set via DM and would have expected the compare to have used to recreated the constraint since it referenced the target constraint name when it constructed the drop constraint syntax.
I believe at least one bug is involved here, most likely two.
The first bug is that model imports are not capturing not null check constraint names.
The second bug is that the source constraint name is not being used when generating the ddl necessary to change the not null constraint name in the target model.
All of this is assuming that I haven't just goofed and forgotten to check a box somewhere telling it to do what I've been talking about here. :-)
Doc

Problem with alter table in execute immediate

We have PL/SQL scripts which modify the data structure, add data etc to en existing database. These scripts basically ensure that the db is compatible with what the software expects.
The reason for doing it in PL/SQL rather than SQL script is A) The scripts are launched using GUI so that they are more user friendly. sqlplus is launched as a background process which executes these scripts. All the scripts have EXIT FAILURE WHENEVER SQLERROR as first line to ensure that the control does not hang in the sqlplus background process.
Going from one version to other, we have added a few tables to the database and also modified a few tables. since (i think) DDL is not allowed in PL/SQL block, we had to resort to putting them in EXECUTE IMMEDIATE enclosures.
Now for the real question,
If I create a table using EXECUTE IMMEDIATE clause, I can immediately have insert as a next statement to insert data in this table. but, if I alter the table and add a column to the existing table, I cannot immediately add data to that column, it throws an error saying 'invalid identifier'
At code level, the following is allowed :
EXECUTE IMMEDIATE 'CREATE TABLE SP_TEST_TABLE
                         ID     NUMBER,
                         NAME     Varchar2(40)
INSERT INTO SP_TEST_TABLE(ID, NAME) Values(1, 'SP');
but I get error for the following :
EXECUTE IMMEDIATE 'ALTER TABLE SP_TEST_TWO ADD
                    ANOTHER_COLUMN     number
UPDATE     SP_TEST_TWO SET          ANOTHER_COLUMN = 1;
In this case, it says ANOTHER_COLUMN invalid identifier
Does anybody know why?
any workaround will be greatly appreciated.
--SP

Friends,
Thanks to all of you for your help. The spelling mistakes might have occurred becuase i changed the actual script to something 'short and complete' to show the problem.
I could solve the problem by having more than one PL/SQL block within my file. something like :
BEGIN
--alter table statements here
END;
BEGIN
--insert the values in column here.
END;
I am still not sure why the error is presented only on alter table statement and not for create table statement. Probably somebody with the knowledge of oracle internals will be able to throw more light on it. I am trying to get the naswers, if I get the answer, I'll surely post it here.
Regards,
--Saurabh

Exception Typo: ORA-02297: cannot disable constraint (string.string)

ORA-02297: cannot disable constraint (string.string) - dependencies exist
Cause: an alter table disable constraint failed becuase the table has foriegn keys
that are dpendent on this constraint.
Action: Either disable the foreign key constraints or use disable cascade
Note the typo of the word BECAUSE from Version 11R2 back to at least 10R2.
Thanks.

Actually, please also correct the words "foriegn" and "dpendent" too!

ALTER TABLE privilege and CREATE/DROP/ENABLE/DISABLE constraint privilege

Hi,
I am looking for some detailed info regarding the below previleges
ALTER TABLE, CREATE CONSTRAINT, DROP CONSTRAINT, ENABLE CONSTRAINT AND DISABLE CONSTRAINT PRiVILEGES.
I have two schemas 'A' and 'B', I want to provide user 'A' with Alter table, create or drop constraint,Enable or Disable constraint on schema B.
Please let me know how to make this work.
Thank you

I got the answer for my second question, I have an option to grant 'Alter ANY table' privilege to the user.Yes, but you should not do that.
Regarding question one, Suppose I have two schemas A and B and I want Schema A to have alter table privilege on all tables of Schema B.
Can I do this in one command No
or I need to grant alter on each table saperately?Yes
If I am chosing the second option for each table saperately then whenever a table is added in schema B we need to grant privilege on that table as well.Yes. But nothing strange there. Designing and creating objects includes the privileges on them.
If user A is granted with alter table privilege on a table which user B owns then can user A drop/create/enable/disable constraints for that table?Yes, isn't that what all this about?
Again, letting one user alter the objects of another user is generally not such a good idea. Hope you see this from our discussion.
Alter table privilege includes adding and dropping columns. This is why I suggested writing a procedure that does exactly what you need. And then grant execute on that to A.
The best thing of course would be NOT TO disable the constraints, they are probably there for a reason.
I am currently handling an issue where one session doing this, deadlocks with another session doing only selects - From other tables, that is!
Regards
Peter

Altering Primary Key constraint on a table i Oracle 10G

Hi All,
Can anyone tell me how to alter a primary key constraint on any table. My concern is that, suppose i have a table called 'Employee' where only 'EmployeeName' is added as a primary ket constaint. Now i want to alter this P.K. constarint to add 'EmployeeName' and 'DateOfBirth' as a primary key. Can anyone suggest me how can i achieve that? Any help will be highly appreciated.

hi,
you need to drop the constraint and recreate it.
SQL> conn scott/tiger@alpspso
Connected.
SQL> create table test (id number constraint id_pk primary key,name varchar(30));
create table test (id number constraint id_pk primary key,name varchar(30))
ERROR at line 1:
ORA-00955: name is already used by an existing object
SQL> create table test_table (id number constraint id_pk primary key,name varchar(30))
Table created.
SQL> alter table test_table modify constraint id_pk primary key(id,name);
alter table test_table modify constraint id_pk primary key(id,name)
ERROR at line 1:
ORA-00933: SQL command not properly ended
SQL> alter table test_table modify constraint id_pk(id,name);
alter table test_table modify constraint id_pk(id,name)
ERROR at line 1:
ORA-00933: SQL command not properly ended
SQL> alter table test_table modify primary key(id,name);
alter table test_table modify primary key(id,name)
ERROR at line 1:
ORA-00933: SQL command not properly ended
SQL> alter table drop constraint id_pk;
alter table drop constraint id_pk
ERROR at line 1:
ORA-00903: invalid table name
SQL> alter table test_table drop constraint id_pk;
Table altered.
SQL> alter table test_table add constraint id_pk primary_key(id,name);
alter table test_table add constraint id_pk primary_key(id,name)
ERROR at line 1:
ORA-00902: invalid datatype
SQL> alter table test_table add constraint id_pk primary key(id,name);
Table altered.
Regards.
Navneet

Altering Primary Key Constraint

hi this may sound silly .
but is it possible to alter a primary key constraint and add another column to it ?
eg. >desc t1
c1 number(3) not null
c2 number(3)
here I have created primary key on column c1.
Now I want to alter this constraint and add second column also as part of primary key constraint (so that it will be composite primary key )
How do i do that ? Do the column needs to be empty ?
Thanks

You should use ALTER TABLE DROP CONSTRAINT / ADD CONSTRAINT option.
Do the column needs to be empty ?Because primary key constraint supposes NOT NULL constraints for columns
included into primary key, all columns havn't to have nulls values (NOT NULL constraint will be added to c2 column):
SQL> create table t1 (c1 number(3) not null, c2 number(3));
Table created.
SQL> alter table t1 add constraint t1_pk primary key(c1);
Table altered.
SQL> insert into t1 values(1,1);
1 row created.
SQL> insert into t1 values(2,null);
1 row created.
SQL> commit;
Commit complete.
SQL> alter table t1 drop constraint t1_pk;
Table altered.
SQL> alter table t1 add constraint t1_pk primary key (c1,c2);
alter table t1 add constraint t1_pk primary key (c1,c2)
ERROR at line 1:
ORA-01449: column contains NULL values; cannot alter to NOT NULL
SQL> update t1 set c2 = 3;
2 rows updated.
SQL> alter table t1 add constraint t1_pk primary key (c1,c2);
Table altered.
SQL> desc t1
Name                                      Null?    Type
C1                                        NOT NULL NUMBER(3)
C2                                        NOT NULL NUMBER(3)Rgds.

SQL Server 2012 Undetected Deadlock in a table with only one row

We have migrated our SQL 2000 Enterprise Database to SQL 2012 Enterprise few days ago.
This is our main database, so most of the applications access it.
The day after the migration, when users started to run tasks, the database access started to experiment a total failure.
That is, all processes in the SQL 2k12 database were in lock with each other. This is a commom case of deadlock, but the Database Engine was unable to detect it.
After some research, we found that the applications were trying to access a very simple table with only one row. This table has a number that is restarted every day and is used to number all the transactions made against the system. So, client
applications start a new transaction, get the current number, increment it by one and commit the transaction.
The only solution we found was to kill all user processes in SQL Server every time this situation occurs (no more than 5 minutes when all clients are accessing the database).
No client application was changed in this migration and this process was working very well for the last 10 years.
The problem is that SQL 2k12 is unable to handle this situation compared to SQL 2k.
It seems to occurs with other tables too, but as this is an "entry table" the problem occurs with it first.
I have searched internet and some suggest some workarounds like using table hints to completely lock the table at the begining of the transaction, but it can't be used to other tables.
Does anyone have heard this to be a problem with SQL 2k12? Is there any fixes to make SQL 2k12 as good as SQL 2k?

First off re: "Unfortunatelly, this can't be used in production environment as exclusive table lock would serialize the accesses to tables and there will be other tables that will suffer with this problem."
This is incorrect.
Using a table to generate sequence numbers like this is a bad idea exactly because the access must be serialized. Since you can't switch to a SEQUENCE object, which is the correct solution, the _entire goal_ of this exercise to find a way to properly
serialize access to this table. Using exclusive locking will not be necessary for all the tables; just for the single-row table used for generating sequence values with a cursor.
I converted the sample program to VB.NET:
Public Class Form1
Private mbCancel As Boolean = False
Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click
Dim soConn As ADODB.Connection
Dim soRst As ADODB.Recordset
Dim sdData As Date
Dim slValue As Long
Dim slDelay As Long
'create database vbtest
'go
' CREATE TABLE [dbo].[ControlNumTest](
' [UltData] [datetime] NOT NULL,
' [UltNum] [int] NOT NULL,
' CONSTRAINT [PK_CorreioNumTeste] PRIMARY KEY CLUSTERED
' [UltData] Asc
' )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 80) ON [PRIMARY]
' ) ON [PRIMARY]
mbCancel = False
Do
' Configure the Connection object
soConn = New ADODB.Connection
With soConn
.ConnectionString = "Provider=SQLNCLI11;Initial Catalog=vbtest;Data Source=localhost;trusted_connection=yes"
.IsolationLevel = ADODB.IsolationLevelEnum.adXactCursorStability
.Mode = ADODB.ConnectModeEnum.adModeReadWrite
.CursorLocation = ADODB.CursorLocationEnum.adUseServer
.Open()
End With
' Start a new transaction
Call soConn.BeginTrans()
' Configure the RecordSet object
soRst = New ADODB.Recordset
With soRst
.ActiveConnection = soConn
.CursorLocation = ADODB.CursorLocationEnum.adUseServer
.CursorType = ADODB.CursorTypeEnum.adOpenForwardOnly
.LockType = ADODB.LockTypeEnum.adLockPessimistic
.Open("SELECT * FROM dbo.ControlNumTest")
End With
With soRst
sdData = .Fields!UltData.Value ' Read the last Date (LOCK INFO 1: See comments bello
slValue = .Fields!UltNum.Value ' Read the last Number
If sdData <> Date.Now.Date Then ' Date has changed?
sdData = Date.Now.Date
slValue = 1 ' Restart number
End If
.Fields!UltData.Value = sdData ' Update data
.Fields!UltNum.Value = slValue + 1 ' Next number
End With
Call soRst.Update()
Call soRst.Close()
' Ends the transaction
Call soConn.CommitTrans()
Call soConn.Close()
soRst = Nothing
soConn = Nothing
txtUltNum.Text = slValue + 1 ' Display the last number
Application.DoEvents()
slDelay = Int(((Rnd * 250) + 100) / 100) * 100
System.Threading.Thread.Sleep(slDelay)
Loop While mbCancel = False
If mbCancel = True Then
Call MsgBox("The test was canceled")
End If
Exit Sub
End Sub
Private Sub Button2_Click(sender As Object, e As EventArgs) Handles Button2.Click
mbCancel = True
End Sub
End Class
And created the table
CREATE TABLE [dbo].[ControlNumTest](
[UltData] [datetime] NOT NULL,
[UltNum] [int] NOT NULL,
CONSTRAINT [PK_CorreioNumTeste] PRIMARY KEY CLUSTERED
[UltData] Asc
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = on, FILLFACTOR = 80) ON [PRIMARY]
) ON [PRIMARY]
go insert into ControlNumTest values (cast(getdate()as date),1)
Then ran 3 copies of the program and generated the deadlock:
<deadlock>
<victim-list>
<victimProcess id="processf27b1498" />
</victim-list>
<process-list>
<process id="processf27b1498" taskpriority="0" logused="0" waitresource="KEY: 35:72057594039042048 (a01df6b954ad)" waittime="1970" ownerId="3181" transactionname="implicit_transaction" lasttranstarted="2014-02-14T15:49:31.263" XDES="0xf04da3a8" lockMode="X" schedulerid="4" kpid="9700" status="suspended" spid="51" sbid="0" ecid="0" priority="0" trancount="2" lastbatchstarted="2014-02-14T15:49:31.267" lastbatchcompleted="2014-02-14T15:49:31.267" lastattention="1900-01-01T00:00:00.267" clientapp="vbt" hostname="DBROWNE2" hostpid="21152" loginname="NORTHAMERICA\dbrowne" isolationlevel="read committed (2)" xactid="3181" currentdb="35" lockTimeout="4294967295" clientoption1="671088672" clientoption2="128058">
<executionStack>
<frame procname="adhoc" line="1" stmtstart="80" sqlhandle="0x020000008376181f3ad0ea908fe9d8593f2e3ced9882f5c90000000000000000000000000000000000000000">
UPDATE [dbo].[ControlNumTest] SET [UltData]=@Param000004,[UltNum]=@Param000005 </frame>
<frame procname="unknown" line="1" sqlhandle="0x0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000">
unknown </frame>
</executionStack>
<inputbuf>
(@Param000004 datetime,@Param000005 int)UPDATE [dbo].[ControlNumTest] SET [UltData]=@Param000004,[UltNum]=@Param000005 </inputbuf>
</process>
<process id="processf6ac9498" taskpriority="0" logused="10000" waitresource="KEY: 35:72057594039042048 (a01df6b954ad)" waittime="1971" schedulerid="5" kpid="30516" status="suspended" spid="55" sbid="0" ecid="0" priority="0" trancount="1" lastbatchstarted="2014-02-14T15:49:31.267" lastbatchcompleted="2014-02-14T15:49:31.267" lastattention="1900-01-01T00:00:00.267" clientapp="vbt" hostname="DBROWNE2" hostpid="27852" loginname="NORTHAMERICA\dbrowne" isolationlevel="read committed (2)" xactid="3182" currentdb="35" lockTimeout="4294967295" clientoption1="671156256" clientoption2="128058">
<executionStack>
<frame procname="adhoc" line="1" sqlhandle="0x020000003c6309232ab0edbe0a7790a816a09c4c5ac6f43c0000000000000000000000000000000000000000">
FETCH API_CURSOR0000000000000001 </frame>
<frame procname="unknown" line="1" sqlhandle="0x0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000">
unknown </frame>
</executionStack>
<inputbuf>
FETCH API_CURSOR0000000000000001 </inputbuf>
</process>
</process-list>
<resource-list>
<keylock hobtid="72057594039042048" dbid="35" objectname="vbtest.dbo.ControlNumTest" indexname="PK_CorreioNumTeste" id="lockff6e6c80" mode="U" associatedObjectId="72057594039042048">
<owner-list>
<owner id="processf6ac9498" mode="S" />
<owner id="processf6ac9498" mode="U" requestType="wait" />
</owner-list>
<waiter-list>
<waiter id="processf27b1498" mode="X" requestType="convert" />
</waiter-list>
</keylock>
<keylock hobtid="72057594039042048" dbid="35" objectname="vbtest.dbo.ControlNumTest" indexname="PK_CorreioNumTeste" id="lockff6e6c80" mode="U" associatedObjectId="72057594039042048">
<owner-list>
<owner id="processf27b1498" mode="U" />
<owner id="processf27b1498" mode="U" />
<owner id="processf27b1498" mode="X" requestType="convert" />
</owner-list>
<waiter-list>
<waiter id="processf6ac9498" mode="U" requestType="wait" />
</waiter-list>
</keylock>
</resource-list>
</deadlock>
It's the S lock that comes from the cursor read that's the villian here. U locks are compatible with S locks, so one session gets a U lock and another gets an S lock. But then the session with an S needs a U, and the session with a U needs an
X. Deadlock.
I'm not sure what kind of locks were taken by this cursor code on SQL 2000, but on SQL 2012, this code is absolutely broken and should deadlock.
The right way to fix this code is to add (UPDLOCK,SERIALIZABLE) to the cursor
.Open("SELECT * FROM dbo.ControlNumTest with (updlock,serializable)")
So each session reads the table with a restrictive lock, and you don't mix S, U and X locks in this transaction. This resolves the deadlock, but requires a code change.
I tried several things that didn't require a code, which did not resolve the deadlock;
1) setting ALLOW_ROW_LOCKS=OFF ALLOW_PAGE_LOCKS=OFF
2) SERIALIZABLE isolation level
3) Switching OleDB providers from SQLOLEDB to SQLNCLI11
Then I replaced the table with a view containing a lock hint:
CREATE TABLE [dbo].[ControlNumTest_t](
[UltData] [datetime] NOT NULL,
[UltNum] [int] NOT NULL,
CONSTRAINT [PK_CorreioNumTeste] PRIMARY KEY CLUSTERED
[UltData] Asc
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = on, FILLFACTOR = 80) ON [PRIMARY]
) ON [PRIMARY]
go
create view ControlNumTest as
select * from ControlNumTest_t with (tablockx)
Which, at least in my limited testing, resovlved the deadlock without any client code change.
David
David http://blogs.msdn.com/b/dbrowne/

Deleting Datas from a table without disabling constraints.

Hi,
I am working in Oracle9i and solaris 5.8. In that i want to delete half of the datas in a table . the table contains one lakh rows but i need to delete only 50 thousand rows. But the table is constraints enabled.Please send me some queries how to delete the datas withput disabling the constraints.

What type of constraint do you have ?
In case of not null, unique, primary key constraint you can delete the rows without disabling the constraints.
In case of referential integrity constraint you can also delete the rows without disable the constraints but you have to specify on delete cascade constraints clause. By doing so, Oracle will delete the rows in the child table as well.
http://www.techonthenet.com/oracle/foreign_keys/foreign_delete.php

SQL error msg - The DELETE statement conflicted with the SAME TABLE REFERENCE constraint

Executed as user: ****. The DELETE statement
conflicted with the SAME TABLE REFERENCE constraint "FK_PARENT_TASK_REF".
The conflict occurred in database "****", table "****", column
'PARENT_TASK_ID'. [SQLSTATE 23000] (Error 547) The statement has been
terminated. [SQLSTATE 01000] (Error 3621). The step failed.
Does this error msg indicate the whole script failed to execute or was it just a single step/task that failed ?
What does error msg mean ?
Anyway to prevent this error msg and ensure script runs successfully

Hi mdavidh,
This error occurs because the record 'PARENT_TASK_ID' was referenced by 'FK_PARENT_TASK_REF'.
Please refer below codes:
CREATE TABLE MyTable (
ID INT, primary key(ID), -- primary key
ID_Parent INT foreign key(ID_Parent) references MyTable(ID), -- foreign key reference the same table
insert into MyTable(ID,ID_Parent)
values(0,0);
insert into MyTable(ID,ID_Parent)
values(1,0);
insert into MyTable(ID,ID_Parent)
values(2,0);
insert into MyTable(ID,ID_Parent)
values(3,1);
insert into MyTable(ID,ID_Parent)
values(4,3);
insert into MyTable(ID,ID_Parent)
values(5,4);
CREATE TRIGGER MyTrigger
on MyTable
instead of delete
as
set nocount on
update MyTable set ID_Parent = null where ID_Parent in (select ID from deleted)
delete from MyTable where ID in (select ID from deleted)
Now we could delete records.
delete from MyTable where ID_Parent=0
Thanks,
Candy Zhou

Generate Alter Table with ERWin

Hi all,
Is the a way to Generate Alter Table with ERWin.?
I need this to generate release of a database, thats contains only
the updated tables.
thanx

If you have a stored/saved model of the database or the original schema structures in a script file, you can use ERWin to compare that to the current database. You can have ERWin generate a script the contains the differences which in most cases would be alter statements.

ALTER TABLE command with owner does not work

I performed the following statement in a SQLplus script where the variables were filled some lines before:
alter table '&ownername||'.'||&tablename' move online tablespace '&tablespacename';
However this does not work. I am getting:
ERROR at line 1:
ORA-00903: invalid table name
The variables are replace correctly by SQLplus and everything owner, table, tablespace exist.
Can I (as SYSDBA) not alter the table of another user?
Peter

Solomon Yakobson wrote:
EdStevens wrote:
Ok, you removed the mis-placed quotes, but why the double "." ??
If you wish to append characters immediately after a substitution variable, use a <font color=red size=3>period</font> to separate the variable from the character.
SY.Ah, I had simply never done it that way nor seen it done that way.

Altering table degrade performance - Help needed?

Hi,
I have a table called test_case which has 60 million records.
I got a requirement to add new column with not null constraint and default value as 0.
When I try to add new column with the above said constraints the schema modification taking 40 minutes.
Alter table test_case add tax number(5) not null default 0
Is there any workaround to modiy the schema with less minutes?
I would appreciate if anybody help on this.
Regards
SP

You wanted a faster approach that’s why I suggested this approach. To my understanding there isn't any other method faster than CTAS method.
Something like this you need to do ( If you are in a position to apply the changes ) –
1.     Create a Tables using CTAS method I mentioned
CREATE TABLE New_Table ( col1,
                                        Col2,
                                         tax number(5) Not Null
As Select col1
                ,col2
                ,0
From Original_Table;
2.     Disable the constraints ( Original Table )
3.     Rename the Original_Table to Original_Table_Bak
4.     Rename the New_Table to the Original_Table
5.     Enable back the constraints
6.     Drop the Original_Table_Bak

Partition exchange error on table with nested table

On Oracle 11.2.0.1, I have a partitioned table with some partitions that need to be 'archived' (in terms of moving partitions to an 'archive' table).
I have a source table like:
CREATE TABLE IS_PODACI245
ID_OBJEKTA_IDENTIFIKACIJA NUMBER(10),
ID_OBJEKTA                 NUMBER(20),
DATUM                      TIMESTAMP(6)       NOT NULL,
TZ                         NUMBER(3),
DATA1                      NUMBER(10),
DATA2                      NUMBER(6),
DATA3                      NUMBER(10),
DATA4                      NUMBER,
DATA5                      T_NTCIP_CLIMATE_TABLE
NESTED TABLE DATA5 STORE AS IS_PODACI245_STORE_TABLE
TABLESPACE DATA
PARTITION BY RANGE (DATUM)
PARTITION P_201107 VALUES LESS THAN (TIMESTAMP' 2011-08-01 00:00:00')
    LOGGING
    NOCOMPRESS
    TABLESPACE DATA,
PARTITION P_MAXVALUE VALUES LESS THAN (MAXVALUE)
    LOGGING
    NOCOMPRESS
    TABLESPACE DATA
NOCOMPRESS
NOCACHE
NOPARALLEL
MONITORING;
CREATE INDEX IDX_IS_PODACI245_KOMPLEKS ON IS_PODACI245
(ID_OBJEKTA_IDENTIFIKACIJA, ID_OBJEKTA, DATUM)
TABLESPACE DATA
LOCAL (
PARTITION P_201107
    LOGGING
    NOCOMPRESS
    TABLESPACE DATA,
PARTITION P_MAXVALUE
    LOGGING
    NOCOMPRESS
    TABLESPACE DATA
NOPARALLEL;
CREATE OR REPLACE TYPE t_ntcip_climate_table as table of t_ntcip_climate_fmt;
CREATE OR REPLACE TYPE t_ntcip_climate_FMT as object
( dev_index number(6)
,   dev_description varchar2(512)
,   dev_type number(10)
,   dev_status number(10)
,   dev_mfr_status varchar2(512)
,   dev_active number(3)
,   dev_test_activation number(10)
/I would like to make exchange partition using stage table, and everything is going fine on all tables, but only on a few of them (listed source is one of them, and they're only tables with nested tables wihin), where I get an error.. but sometimes ;)
on a statement like:
ALTER TABLE IS_PODACI245_ARH EXCHANGE PARTITION P_201106 WITH TABLE IS_PODACI245_STAGE EXCLUDING INDEXES WITHOUT VALIDATION;I got an error:
ORA-00001: unique constraint (TXV.SYS_C0032911) violated
it's an unique index between parent and nested table.
what could cause that problem?

Dear,
I suppose that the unique constraint
ORA-00001: unique constraint (TXV.SYS_C0032911) violatedis the one you 've created on the nested table IS_PODACI245_STORE_TABLE
If so, why not disable that constraint and try again.
I have never exchanged such a kind of partitioned table having a nested table in it. But, I could imagine that the cloned non partitioned table IS_PODACI245_STAGE should at least be the exact image of the partitioned table IS_PODACI245_ARH (of course without the partition part) but with the nested table part and including all indexes
In addition, if you have a parent/child relationship between your partitioned tables, then there is a chronological order of exchange starting by the child and then finishing by the parent
see the following link for more information about this order of exchange (and comment 2 for an example also)
http://jonathanlewis.wordpress.com/2006/12/10/drop-parent-partition/#more-65
Hope this helps
Mohamed Houri

Deadlocks with ALTER TABLE DISABLE CONSTRAINT

Similar Messages

Maybe you are looking for