Re: ANALYZE - Currupting Index

From: Ms. D.H. Harvey <qq45_at_liverpool.ac.uk>
Date: 1996/10/08
Message-ID: <DyyGKI.3oy_at_liverpool.ac.uk>#1/1


Jay (jaynet_at_concntric.net) wrote:
: Environment: VAX VMS - Oracle 7.1 Visual Basic Front end.
: Problem:
 

: Some one's argument is whenever an "ANALYZE table Validate Structure" is
: run it is validating without any error messages but currupting the
: index.
 

: The basis for arguement is:
:
: When the "ANALYZE table Validate Structure" is not run the response time
: is very fast and as soon as the person runs the "ANALYZE table Validate
: Structure" the response time becomes terribly slow.
 

: But "ANALYZE" is supposed to analyze the table and show if the index is
: corrupted. Instead in this case it is corrupting the index.
 

: Could this true? Did any one faced this type of problem in the past? If
: so what could be the reason and what is the solution?

We experienced a similar problem when first migrated from 6.0.37 to 7.1.4. None of our objects ANALYZEd all ran OK. Then, some payroll tables ANALYZEd and payroll ground to a halt. Problem due to not setting optimizer_mode in the init file. Default is CHOOSE. Prior to any ANALYZE chose RULE, after ANALYZE chose COST. Solved by placing optimizer_mode = RULE in init file.

Hope this of help Helen Received on Tue Oct 08 1996 - 00:00:00 CEST

Original text of this message