Skip to main content

How to find constraints with same columns but different name between two databases.

How to find constraints with same columns but different name between two databases.

select
prodschema.cons prod_constraint, prodschema.tbl prod_table, prodschema.cols prod_cols, localschema.cons local_constraint, localschema.tbl local_table, localschema.cols local_cols,
'ALTER table '|| prodschema.tbl ||' rename constraint ' || prodschema.cons || ' TO ' || localschema.cons || ';' sqlchg
from
(select
constraint_name cons,
constraint_type cons_type,
table_name tbl,
ltrim(max(sys_connect_by_path(column_name, ','))
keep (dense_rank last order by curr), ',') as cols
from
(select
ucc.constraint_name,
uc.constraint_type,
ucc.table_name,
ucc.column_name,
row_number() over (partition by ucc.constraint_name, ucc.table_name order by ucc.position) as curr,
row_number() over (partition by ucc.constraint_name, ucc.table_name order by ucc.position) -1 as prev
from
user_cons_columns@build3 ucc, user_constraints@build3 uc
where ucc.constraint_name = uc.constraint_name
and uc.constraint_name not like 'SYS_%')
group by constraint_name,constraint_type, table_name
connect by prev = PRIOR curr and constraint_name = PRIOR constraint_name and table_name = PRIOR table_name
start with curr = 1
order by cons,tbl) localschema,
(select
constraint_name cons,
constraint_type cons_type,
table_name tbl,
ltrim(max(sys_connect_by_path(column_name, ','))
keep (dense_rank last order by curr), ',') as cols
from
(select
ucc.constraint_name,
uc.constraint_type,
ucc.table_name,
ucc.column_name,
row_number() over (partition by ucc.constraint_name, ucc.table_name order by ucc.position) as curr,
row_number() over (partition by ucc.constraint_name, ucc.table_name order by ucc.position) -1 as prev
from
user_cons_columns ucc, user_constraints uc
where ucc.constraint_name = uc.constraint_name
and uc.constraint_name not like 'SYS_%'
)
group by constraint_name,constraint_type, table_name
connect by prev = PRIOR curr and constraint_name = PRIOR constraint_name and table_name = PRIOR table_name
start with curr = 1
order by cons,tbl) prodschema
where
prodschema.tbl = localschema.tbl
and prodschema.cols = localschema.cols
and prodschema.cons_type = localschema.cons_type
and prodschema.cons != localschema.cons
and prodschema.tbl not like 'BIN%'
order by prodschema.cons, prodschema.tbl;

Comments

Popular posts from this blog

RabbitMQ java clients for beginners

Here is a sample of a consumer and producer example for RabbitMQ. The steps are Download Erlang Download Rabbit MQ Server Download Rabbit MQ Java client jars Compile and run the below two class and you are done. This sample create a Durable Exchange, Queue and a Message. You will have to start the consumer first before you start the for the first time. For more information on AMQP, Exchanges, Queues, read this excellent tutorial http://blogs.digitar.com/jjww/2009/01/rabbits-and-warrens/ +++++++++++++++++RabbitMQProducer.java+++++++++++++++++++++++++++ import com.rabbitmq.client.Connection; import com.rabbitmq.client.Channel; import com.rabbitmq.client.*; public class RabbitMQProducer { public static void main(String []args) throws Exception { ConnectionFactory factory = new ConnectionFactory(); factory.setUsername("guest"); factory.setPassword("guest"); factory.setVirtualHost("/"); factory.setHost("127.0.0.1"); factory.se...

Spring 3.2 quartz 2.1 Jobs added with no trigger must be durable.

I am trying to enable HA on nodes and in that process I found that in a two test node setup a job that has a frequency of 10 sec was running into deadlock. So I tried upgrading from Quartz 1.8 to 2.1 by following the migration guide but I ran into an exception that says "Jobs added with no trigger must be durable.". After looking into spring and Quartz code I figured out that now Quartz is more strict and earlier the scheduler.addJob had a replace parameter which if passed to true would skip the durable check, in latest quartz this is fixed but spring hasnt caught up to this. So what do you do, well I jsut inherited the factory and set durability to true and use that public class DurableJobDetailFactoryBean extends JobDetailFactoryBean {     public DurableJobDetailFactoryBean() {         setDurability(true);     } } and used this instead of JobDetailFactoryBean in the spring bean definition     <bean i...

Killing a particular Tomcat thread

Update: This JSP does not work on a thread that is inside some native code.  On many occasions I had a thread stuck in JNI code and it wont work. Also in some cases thread.stop can cause jvm to hang. According to javadocs " This method is inherently unsafe. Stopping a thread with Thread.stop causes it to unlock all of the monitors that it has locked". I have used it only in some rare occasions where I wanted to avoid a system shutdown and in some cases we ended up doing system shutdown as jvm was hung so I had a 70-80% success with it.   -------------------------------------------------------------------------------------------------------------------------- We had an interesting requirement. A tomcat thread that was spawned from an ExecutorService ThreadPool had gone Rogue and was causing lots of disk churning issues. We cant bring down the production server as that would involve downtime. Killing this thread was harmless but how to kill i...