Home » SQL & PL/SQL » SQL & PL/SQL » Analyzing Index Problem (10g)
Analyzing Index Problem [message #393606] Mon, 23 March 2009 09:58 Go to next message
reachmexyz
Messages: 8
Registered: February 2009
Location: New Jersey
Junior Member

Hello All
Thanks for the previous responses on DROP BITMAP INDEXES post.
I a using oracle 10g installed on UNIX IBM-AIX system
Now i have a new issue like
After dropping the index, i am recreating the index.
After recreation i wish to gather index stats nd compute statistics. So i have execute the below query.

exec dbms_stats.gather_index_stats
(INDEX_NAME=>'IFACT_TUD01',
INDEX_TYPE=>'BITMAP');

It gave me a error
"wrong number or types of arguments in call to gather_index_stats.
Line 2, column 6 ignored"

But at the time of creation if i compute statistics, its working
"
CREATE BITMAP INDEX IFACT_TUD01 ON tablename
(
col1 ASC
COMPUTE STATISTICS
);"

Can you please tell me how can i compute statistics with exec_dbms package
Re: Analyzing Index Problem [message #393607 is a reply to message #393606] Mon, 23 March 2009 10:03 Go to previous messageGo to next message
BlackSwan
Messages: 25033
Registered: January 2009
Location: SoCal
Senior Member
post results from
SQL> DESC DBMS_STATS

You need to help us by following the Posting Guidelines as stated below.
http://www.orafaq.com/forum/t/88153/0/
Re: Analyzing Index Problem [message #393608 is a reply to message #393606] Mon, 23 March 2009 10:03 Go to previous message
pablolee
Messages: 2834
Registered: May 2007
Location: Scotland
Senior Member
The first thing that I would suggest that you do is read the syntax for the procedure that you are calling:
Quote:
DBMS_STATS.GATHER_INDEX_STATS (
ownname VARCHAR2,
indname VARCHAR2,
partname VARCHAR2 DEFAULT NULL,
estimate_percent NUMBER DEFAULT to_estimate_percent_type
(GET_PARAM('ESTIMATE_PERCENT')),
stattab VARCHAR2 DEFAULT NULL,
statid VARCHAR2 DEFAULT NULL,
statown VARCHAR2 DEFAULT NULL,
degree NUMBER DEFAULT to_degree_type(get_param('DEGREE')),
granularity VARCHAR2 DEFAULT GET_PARAM('GRANULARITY'),
no_invalidate BOOLEAN DEFAULT to_no_invalidate_type
(GET_PARAM('NO_INVALIDATE')),
force BOOLEAN DEFAULT FALSE);

Previous Topic: Help needed for SQL Query (merged)
Next Topic: best practice for mapping table composite key or Pk with unique constraint ?
Goto Forum:
  


Current Time: Fri Dec 02 16:37:22 CST 2016

Total time taken to generate the page: 0.14005 seconds