RE: Naming standards -- that lead to implicit/explicit constraint and index creation.
- From: D'Hooge Freek <Freek.DHooge@xxxxxxxxx>
- To: "Joel.Patterson@xxxxxxxxxxx" <Joel.Patterson@xxxxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 17 Nov 2011 14:16:13 +0100
Hey
In attach you will find an example which shows an implicit unique index not
being recreated during import because the constraint is using an explicit index
instead.
Also note the failed import of some of the index_statistics, which can act as a
red flag to detect such a case.
Regards,
Freek D'Hooge
Uptime
Oracle Database Administrator
email: freek.dhooge@xxxxxxxxx
tel +32(0)3 451 23 82
http://www.uptime.be
disclaimer: www.uptime.be/disclaimer
---
From: Joel.Patterson@xxxxxxxxxxx [mailto:Joel.Patterson@xxxxxxxxxxx]
Sent: woensdag 16 november 2011 20:47
To: D'Hooge Freek; oracle-l@xxxxxxxxxxxxx
Subject: Naming standards -- that lead to implicit/explicit constraint and
index creation.
Oracle version 10.2.0.4
I would appreciate an example where an Index is created such that by creating
an implicit primary key or unique index on the table, would cause one of the
indexes not to be imported.
...
--
//www.freelists.org/webpage/oracle-l
Other related posts:
