RE: Embarasing question ....
- From: "Richard J. Goulet" <rgoulet@xxxxxxxxxx>
- To: <norman.dunbar@xxxxxxxxxxxxxxxxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 11 May 2007 11:53:38 -0400
Norman,
There is a similar problem with Materialized views. I've had an
iTAR open for about a month now with no final resolution.
........................................................................
.............................................................
Kanbay
Dick Goulet, Senior Oracle DBA
45 Bartlett ST | Marlborough, MA 01752 USA
Tel: 508.573.1978 | Fax: 508.229.2019 | Cell: 508.742.5795
rgoulet@xxxxxxxxxx
........................................................................
.............................................................
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Norman Dunbar
Sent: Friday, May 11, 2007 9:00 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: Embarasing question ....
Afternoon all,
Sorry about the 'stupidity' of the following question, but I've just
been bitten by it, and I can't find a proper answer anywhere in the
Oracle DOCS, online or anywhere. If you know of a location for a Fine
Manual that I can read, please tell me. Thanks.
I have a database which calls out to an external software package via
an extproc listener. This started failing for no apparent reason with
'failed to verify indextype' errors.
DBA_INDEXTYPES has no STATUIS columns, but joining to DBA_OBJKECST gave
me 'VALID' for the STATUS column there.
Looking at all my indexes under DBA_INDEXES shows the STATUS to be
VALID there as well.
As far as I was concerned, the error was misleading - my indexes and
indextypes are ok. (First mistake !)
However, further investigation (after raisng a call with the vendor)
showed that under DBA_OBJECTS, for some of the indexes, the STATUS
column showed up as INVALID. This was the cause of my problem.
Q1. How is it possible for an INDEX to be VALID but the object to be
INVALID ?
Q2. Is it wrong of me to think that if the object is 'broken' that the
index should be too?
I've looked in the docs, the status column on XXX_INDEXES says that it
is for unpartitioned indexes and shows whether they are valid or
unusable. For the XXX_OBJECTS the status column simply says where 'the
object is valid or not'.
What am I missing ?
Cheers,
Norman.
Norman Dunbar.
Contract Oracle DBA.
Rivers House, Leeds.
Internal : 7 28 2051
External : 0113 231 2051
Information in this message may be confidential and may be legally
privileged. If you have received this message by mistake, please notify
the sender immediately, delete it and do not copy it to anyone else.
We have checked this email and its attachments for viruses. But you
should still check any attachment before opening it.
We may have to make this message and any reply to it public if asked to
under the Freedom of Information Act, Data Protection Act or for
litigation. Email messages and attachments sent to or from any
Environment Agency address may also be accessed by someone other than
the sender or recipient, for business purposes.
If we have sent you information and you wish to use it please read our
terms and conditions which you can get by calling us on 08708 506 506.
Find out more about the Environment Agency at
www.environment-agency.gov.uk
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
