dbTalk Databases Forums  

[Info-Ingres] Orphaned System Generated Indexes

comp.databases.ingres comp.databases.ingres


Discuss [Info-Ingres] Orphaned System Generated Indexes in the comp.databases.ingres forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Martin Bowes
 
Posts: n/a

Default [Info-Ingres] Orphaned System Generated Indexes - 04-08-2010 , 08:46 AM






Hi All,



I have a table which has 5 system generated indexes. AFAIK only
constraints which do not specify an index can have a system generated
index created. But there are only two constraints on the table, and the
catalogs indicate that two of the secondary indexes are tied to these
constraints.



That leaves three seemingly orphaned indexes on the table.



Are there any other things which can create system generated indexes? If
so how do I determine which index is associated with the object?



My suspicion is that these indexes have been created by constraints (FK
and Unique) and have somehow stayed around after the constraint was
dropped. But I cannot replicate this on the current version of Ingres on
this installation. (II 9.1.2 (a64.lnx/100)NPTL + 13390).



Has there been a version of Ingres in which the system generated indexes
persisted after the drop of the associated constraint?



Martin Bowes

Reply With Quote
  #2  
Old   
David Stephens
 
Posts: n/a

Default Re: [Info-Ingres] Orphaned System Generated Indexes - 04-08-2010 , 09:26 AM






Hi,

I've not seen that but on the flip side if a constraint uses a user defined index and is then dropped, the index is dropped with it! Annoying.

Dave Stephens

-----Original Message-----
From: info-ingres-bounces (AT) kettleriver...ting (DOT) com [mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com]On Behalf Of Martin Bowes
Sent: 08 April 2010 14:46
To: Ingres and related product discussion forum
Subject: [Info-Ingres] Orphaned System Generated Indexes



Hi All,



I have a table which has 5 system generated indexes. AFAIK only constraints which do not specify an index can have a system generated index created.But there are only two constraints on the table, and the catalogs indicate that two of the secondary indexes are tied to these constraints.



That leaves three seemingly orphaned indexes on the table.



Are there any other things which can create system generated indexes? If so how do I determine which index is associated with the object?



My suspicion is that these indexes have been created by constraints (FK and Unique) and have somehow stayed around after the constraint was dropped.But I cannot replicate this on the current version of Ingres on this installation. (II 9.1.2 (a64.lnx/100)NPTL + 13390).



Has there been a version of Ingres in which the system generated indexes persisted after the drop of the associated constraint?



Martin Bowes


__________________________________________________ ____________
This message has been scanned for all viruses by BTnet VirusScreen.
The service is delivered in partnership with MessageLabs.

This service does not scan any password protected or encrypted
attachments.



__________________________________________________ ____________

This message has been checked for all viruses by BTnet VirusScreen.
The service is delivered in partnership with MessageLabs and does not scanany password protected or encrypted attachments.

Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of the company. The contents of this email are confidential to the addressee and may also be privileged. If you are not the addressee of this email, you mustnot copy, forward, disclose or otherwise use it, or any part of it, for any purpose, nor disclose its contents to any other person. If you have received this email in error please notify the sender. Please be aware that any email sent to, or received from, this address may be monitored for quality control, staff training or security purposes. Although the company scans all outgoing email and attachments for viruses, neither the sender northe company accepts any responsibility for viruses and it remains the responsibility of the recipient to scan email and attachments (if any) for viruses.

Reply With Quote
  #3  
Old   
Martin Bowes
 
Posts: n/a

Default Re: [Info-Ingres] Orphaned System Generated Indexes - 04-08-2010 , 09:45 AM



Hi David,



I've seen that bug too. Its bug 109682. That's a very old bug, what
version/patch are you running?



And pardon my paranoia but it's a bug I bother to retest on every patch
I receive!



Marty



From: David Stephens [mailto:dave (AT) chancellors (DOT) co.uk]
Sent: 08 April 2010 15:26
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] Orphaned System Generated Indexes



Hi,



I've not seen that but on the flip side if a constraint uses a user
defined index and is then dropped, the index is dropped with it!
Annoying.



Dave Stephens

-----Original Message-----
From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com]On Behalf Of
Martin Bowes
Sent: 08 April 2010 14:46
To: Ingres and related product discussion forum
Subject: [Info-Ingres] Orphaned System Generated Indexes

Hi All,



I have a table which has 5 system generated indexes. AFAIK only
constraints which do not specify an index can have a system generated
index created. But there are only two constraints on the table, and the
catalogs indicate that two of the secondary indexes are tied to these
constraints.



That leaves three seemingly orphaned indexes on the table.



Are there any other things which can create system generated
indexes? If so how do I determine which index is associated with the
object?



My suspicion is that these indexes have been created by
constraints (FK and Unique) and have somehow stayed around after the
constraint was dropped. But I cannot replicate this on the current
version of Ingres on this installation. (II 9.1.2 (a64.lnx/100)NPTL +
13390).



Has there been a version of Ingres in which the system generated
indexes persisted after the drop of the associated constraint?



Martin Bowes


__________________________________________________ ____________
This message has been scanned for all viruses by BTnet
VirusScreen.
The service is delivered in partnership with MessageLabs.

This service does not scan any password protected or encrypted
attachments.


__________________________________________________ ____________

This message has been checked for all viruses by BTnet VirusScreen.
The service is delivered in partnership with MessageLabs and does not
scan any password protected or encrypted attachments.

Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of the
company. The contents of this email are confidential to the addressee
and may also be privileged. If you are not the addressee of this email,
you must not copy, forward, disclose or otherwise use it, or any part of
it, for any purpose, nor disclose its contents to any other person. If
you have received this email in error please notify the sender. Please
be aware that any email sent to, or received from, this address may be
monitored for quality control, staff training or security purposes.
Although the company scans all outgoing email and attachments for
viruses, neither the sender nor the company accepts any responsibility
for viruses and it remains the responsibility of the recipient to scan
email and attachments (if any) for viruses.

Reply With Quote
  #4  
Old   
Martin Bowes
 
Posts: n/a

Default Re: [Info-Ingres] Orphaned System Generated Indexes - 04-08-2010 , 10:05 AM



What patch are you running?



Try with: set trace point qe61



Marty



From: David Stephens [mailto:dave (AT) chancellors (DOT) co.uk]
Sent: 08 April 2010 15:59
To: Martin Bowes
Subject: RE: [Info-Ingres] Orphaned System Generated Indexes



Hi Marty,



it was around before we moved up to 9.2 from 2006. I see it was fixed in

Patch 11500 for Ingres 2.6 on Tru64. Maybe it has crept back in!



Dave.

-----Original Message-----
From: Martin Bowes [mailto:martin.bowes (AT) ctsu (DOT) ox.ac.uk]
Sent: 08 April 2010 15:46
To: Ingres and related product discussion forum
Cc: David Stephens
Subject: RE: [Info-Ingres] Orphaned System Generated Indexes

Hi David,



I've seen that bug too. Its bug 109682. That's a very old bug,
what version/patch are you running?



And pardon my paranoia but it's a bug I bother to retest on
every patch I receive!



Marty



From: David Stephens [mailto:dave (AT) chancellors (DOT) co.uk]
Sent: 08 April 2010 15:26
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] Orphaned System Generated Indexes



Hi,



I've not seen that but on the flip side if a constraint uses a
user defined index and is then dropped, the index is dropped with it!
Annoying.



Dave Stephens

-----Original Message-----
From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com]On Behalf Of
Martin Bowes
Sent: 08 April 2010 14:46
To: Ingres and related product discussion forum
Subject: [Info-Ingres] Orphaned System Generated Indexes

Hi All,



I have a table which has 5 system generated indexes.
AFAIK only constraints which do not specify an index can have a system
generated index created. But there are only two constraints on the
table, and the catalogs indicate that two of the secondary indexes are
tied to these constraints.



That leaves three seemingly orphaned indexes on the
table.



Are there any other things which can create system
generated indexes? If so how do I determine which index is associated
with the object?



My suspicion is that these indexes have been created by
constraints (FK and Unique) and have somehow stayed around after the
constraint was dropped. But I cannot replicate this on the current
version of Ingres on this installation. (II 9.1.2 (a64.lnx/100)NPTL +
13390).



Has there been a version of Ingres in which the system
generated indexes persisted after the drop of the associated constraint?



Martin Bowes



__________________________________________________ ____________
This message has been scanned for all viruses by BTnet
VirusScreen.
The service is delivered in partnership with
MessageLabs.

This service does not scan any password protected or
encrypted
attachments.


__________________________________________________ ____________

This message has been checked for all viruses by BTnet
VirusScreen.
The service is delivered in partnership with MessageLabs and
does not scan any password protected or encrypted attachments.

Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be the views
of the company. The contents of this email are confidential to the
addressee and may also be privileged. If you are not the addressee of
this email, you must not copy, forward, disclose or otherwise use it, or
any part of it, for any purpose, nor disclose its contents to any other
person. If you have received this email in error please notify the
sender. Please be aware that any email sent to, or received from, this
address may be monitored for quality control, staff training or security
purposes. Although the company scans all outgoing email and attachments
for viruses, neither the sender nor the company accepts any
responsibility for viruses and it remains the responsibility of the
recipient to scan email and attachments (if any) for viruses.


__________________________________________________ ____________
This message has been scanned for all viruses by BTnet
VirusScreen.
The service is delivered in partnership with MessageLabs.

This service does not scan any password protected or encrypted
attachments.


__________________________________________________ ____________

This message has been checked for all viruses by BTnet VirusScreen.
The service is delivered in partnership with MessageLabs and does not
scan any password protected or encrypted attachments.

Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of the
company. The contents of this email are confidential to the addressee
and may also be privileged. If you are not the addressee of this email,
you must not copy, forward, disclose or otherwise use it, or any part of
it, for any purpose, nor disclose its contents to any other person. If
you have received this email in error please notify the sender. Please
be aware that any email sent to, or received from, this address may be
monitored for quality control, staff training or security purposes.
Although the company scans all outgoing email and attachments for
viruses, neither the sender nor the company accepts any responsibility
for viruses and it remains the responsibility of the recipient to scan
email and attachments (if any) for viruses.

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.