The GENERATED column is derived from the OBJ$ table, so it's an attribute
of the object, not the index and we have to look elsewhere for rules about
why an object might be generated. (It might also explain why any "rule" we
discover might display inconsistencies.)
When I create a CONTEXT index on a column Oracle generates a handful of
heap tables, a couple of IOT, and a couple of LOBs.
Checking the GENERATED column of user_objects I can see that the LOBs, the
LOB indexes, and the IOT_TOP indexes of the IOTs are flagged as system
generated, the other objects making up the context index are not.
Checking basic lobs, when I create (and populate) a table with a LOB column
the LOB index is flagged as system generated
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com/all-postings
Author: Oracle Core (Apress 2011)
http://www.apress.com/9781430239543
----- Original Message -----
From: "Norman Dunbar" <oracle@xxxxxxxxxxxxxxx>
To: <oracle-l@xxxxxxxxxxxxx>
Sent: Friday, August 12, 2016 9:08 PM
Subject: Silly question about GENERATED column of DBA_INDEXES
Try as I might, I cannot get the "generated" column on user/all/dba _
indexes to take on any value other than 'N'.
I thought it was set to 'Y' if the index was system created, and indeed,
that's what the docs state. However, I have run a few tests creating pk and
unique constraints, without pre creating the supporting index, and the
value remains stubbornly set to 'N'.
Ditto when the creation of an MVIEW crews a new primary key, the underlying
index still flags as not system generated.
I admit to being puzzled! Can someone please enlighten me? Thanks.
Cheers,
Norm.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2016.0.7690 / Virus Database: 4633/12768 - Release Date: 08/07/16
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2016.0.7690 / Virus Database: 4633/12768 - Release Date: 08/07/16
--
//www.freelists.org/webpage/oracle-l
