After Creating Index ???

We creating a New Custom Index on MSEG and transported to production?
What are the followup activites to make the usage of created index immediately ??
Rdgs
PR

Hi,
Oracle use index after it have been created based on table statistics (CBO)
I suggest you create statistics for this index and update the statistics for the table MSEG.
Use the report RSANAORA, or the transaction DB20.
Best Regards,
Itamar Marioto

Similar Messages

Compute Statistics after creating indexes

Hi, I have to create some indexes in a production database.
I have a doubt.
Do I need to Compute Statistics after creating indexes?
Or when I create they automatically are computed?
Thanks for any help.
Edited by: Petri BR on May 14, 2013 3:39 PM

Petri BR wrote:
Hi, I have to create some indexes in a production database.
I have a doubt.
Do I need to Compute Statistics after creating indexes?answer is version dependeent.
Or when I create they automatically are computed?answer depends upon which version of Oracle.
How do I ask a question on the forums?
SQL and PL/SQL FAQ
you should ALWAYS provide Oracle version to FOUR decimal places.
below is even better
SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
PL/SQL Release 11.2.0.2.0 - Production
CORE    11.2.0.2.0      Production
TNS for Linux: Version 11.2.0.2.0 - Production
NLSRTL Version 11.2.0.2.0 - ProductionHandle:     Petri BR
Status Level:     Newbie
Registered:     Dec 10, 2007
Total Posts:     119
Total Questions:     29 (18 unresolved)
I extend to you my condolences; since you rarely get your questions answered here.

After creating index query is taking more

Hello all,
I am trying the following..and not getting why the query is taking more time after creating the index
SQL> SELECT distinct version_no
2 FROM iefloa_data_anal
3 WHERE datetime_inserted > to_date('17-02-2004','dd-mm-yyyy');
VERSION_NO
999
Elapsed: 00:00:22.16
Execution Plan
0 SELECT STATEMENT Optimizer=CHOOSE (Cost=15 Card=1 Bytes=22)
1 0 SORT (UNIQUE) (Cost=15 Card=1 Bytes=22)
2 1 TABLE ACCESS (FULL) OF 'IEFLOA_DATA_ANAL' (Cost=2 Card=1
Bytes=22)
/*******************Here I am creating the Index************/
SQL> create index t_ind_date on iefloa_data_anal(datetime_inserted);
Index created.
Elapsed: 00:07:427.38
SQL> SELECT distinct version_no
2 FROM iefloa_data_anal
3 WHERE datetime_inserted > to_date('17-02-2004','dd-mm-yyyy');
VERSION_NO
999
Elapsed: 00:00:40.10
Execution Plan
0 SELECT STATEMENT Optimizer=CHOOSE (Cost=14 Card=1 Bytes=22)
1 0 SORT (UNIQUE) (Cost=14 Card=1 Bytes=22)
2 1 TABLE ACCESS (BY INDEX ROWID) OF 'IEFLOA_DATA_ANAL' (Cos
t=1 Card=1 Bytes=22)
3 2 INDEX (RANGE SCAN) OF 'T_IND_DATE' (NON-UNIQUE) (Cost=
1 Card=1)
can anybody explains whats the reason...
the table is having around 1.5 crore records
regards

The execution plan clearly shows that Oracle thinks only one row is going to match that condition on the index ("Card=1"). Is that a true statement? If not, you should make sure your stats are accurate. If the data is highly skewed, you may need to put a histogram on that column.
Another possibility is that the index is on much slower disks than the table. Although, I can't imagine any range scan on an index that has only one matching value taking that long. How about doing a full trace (SET AUTOTRACE ON) and posting the logical and physical i/o information?

Unable to search documents after creating Index

hi all,
i've created index and assigned datasources to that index.but when i try to search that documents it is showing tht "No matches have been found "
where as in applicaiton log it is displauing follwing message
Error 11/29/05 6:30:03 PM XCrawlerService Failed to create crawler task SubscriptionCrawler - com.sapportals.wcm.service.xcrawler.XCrawlerException: The SQL statement "SELECT "XCRW_TASK_INDEX" FROM "KMC_XCRW_TASKS" WHERE "XCRW_TASK_ID" = ?" contains the semantics error[s]: type check error: the e
so, can any body help me to solve above problem
regards
gnana

Hi Gnana,
You may try searching on http://service.sap.com/patches
You will have to search for ur requrired patches. You would also find pdfs, giving details on the same.
All the best.
Awaiting Reply.
Warm Regards,
Ritu R Hunjan
Message was edited by: Ritu Hunjan

Compute Statistics after create a index

Good night, I tryed it before and got no help.
So I'll try it again, because I didn't find it yet.
I have to create some indexes in a production database.
I have a doubt.
Do I need to Compute Statistics after creating indexes?
Or when I create they automatically are computed?
Thanks for any help.
The version I'm using is:
Oracle Database 10g Release 10.2.0.5.0 - 64bit Production
PL/SQL Release 10.2.0.5.0 - Production
CORE 10.2.0.5.0 Production
TNS for 64-bit Windows: Version 10.2.0.5.0 - Production
NLSRTL Version 10.2.0.5.0 - Production

Petri BR wrote:
Good night, I tryed it before and got no help.
So I'll try it again, because I didn't find it yet.
I have to create some indexes in a production database.
I have a doubt.
Do I need to Compute Statistics after creating indexes?after CREATE INDEX what are the values for the index statistics?
Or when I create they automatically are computed?Just look at the statistics values after issuing CREATE INDEX & answer the question yourself!

I can not create index

Hello,
I am using 8.1.7
I'd like to create index on clob column, but after:
create index news_ctx_ind on news(news_description) indextype is CTXSYS.CONTEXT parameters ('DATASTORE CTXSYS.DEFAULT_DATASTORE')
i get:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-20000: interMedia Text error:
DRG-11422: linguistic initialization failed
DRG-00100: internal error, arguments : [52100],[drxs.c],[553],[gxtopen],[1]
DRG-11432: file error while accessing interMedia Text knowledge base
ORA-06512: at "CTXSYS.DRUE", line 126
ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 78
ORA-06512: at line 1
please help me.
null

<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Omar Alonso ([email protected]):
Do you have russian content in the documents?
What's the db version and character set?
You may try to disable the theme indexing:
begin
ctx_ddl.create_preference('mylex','BASIC_LEXER');
ctx_ddl.set_attribute('mylex','index_themes','NO');
ctx_ddl.set_attribute('mylex','index_text','YES');
end;
create index myindex on mytable(docs) indextype is ctxsys.context parameters('LEXER lmylex');<HR></BLOCKQUOTE>
Hi,
I am also facing the same problem. my character set is default and i am using oracle 8.1.6. I can create index if my database is dedicated but it will not work for mts for same table and data using intermedia.
Suppose i dont want to disable theme indexing and though i want to create index then what i have to do.
null

DSO activation problem after creating the secondary indexes

Hi,
I am facing the problem with DSO activation after creating the secondary indexes.
Compared with Info Cubes there is no functionality available which allows dropping and recreating a secondary index before/after the data activation.
As a workaround I can write a simple report which drops and creates the indexes on database level.
By using a process chain, we can simply insert the drop index report before data activation and the create index report after the data activation process.
Can any body help me step by step procedure or Material to write the programs for delete index and create index reports on DSO object?..
Thanks in advance for your help.
Thanks & Regards,
Bala

hi,
in BI if you are using the dso for reporting then you can simply chk the settings of dso for SID generation.
no need to create the indexes or delete it.
if the dso is not used for report then no need to use indexes.
Ramesh

Why should we create index on the table after inserting data ?

Please tell me the Reason, why should we create index on the table after inserting data .
while we can also create index on the table before insertion of the data.

The choice depends on a number of factors, the main being how many rows are going to be inserted in the table as a percentage of the existing rows, or the percentage growth.
Creating index after a table has been populated works better when the tables are large or the inserts are large for the following reasons
1. The sort and creation of index is more efficient when done in batch and written in bulk. So works faster.
2. When the index is being written blocks get acquired as more data gets written. So, when a large number of rows get inserted in a table that already has an index , the index data blocks start splitting / chaining. This increases the "depth" of the inverted b-tree makes and that makes the index less efficient on I/O. Creating index after data has been inserted allows Orale to create optical block distribution/ reduce splitting / chaining
3. If an index exists then it too is routed through the undo / redo processes. Thats an overhead which is avoided when you create index after populating the table.
Regards

What is the difference between creating index on cube and infopkg in PC

Hi All
I have process chain in which after executing infopkg(load data infopkg),creating index on cube i.e Object type is Cube ,for which execution time is 1 hour,then after (subsequent step ) again create index at this time object type is "infopkg"
execute infopkg for which time is 2 minnutes,what is the diffrence between these two,if i reome create index from cube i can save 1 hour time,I have to reveiew this
chain for performance,plese post me your thoughts,it's argent,your help will be heighly appreciatable.Thanks in advance.
regards
EA

By default once u use create index process type Object type has Infopackage - change it to Cube tech name.
If its Cube - Indexes will be deleted or created for all the date in the cube.
Message was edited by:
Jr Roberto

REBUILD INDEX vs DROP/CREATE INDEX

Hi there,
Does anyone has already got some performance degradation after REBUILD INDEXes ? Would it be better to perform DROP/CREATE INDEX instead ?
Thank you very much for anu reply.
Best regards,
Helena

Hi,
>>so is it then better to DROP/CREATE them ?
Well, In fact I learned that when you rebuild an index, Oracle creates a new index from the old index and does not perform sorting while building the new index, which results in performance enhancement. In this case, depending of the size of your data it's necessary sufficient space on a tablespace for storing the old as well as the new index (while creating the new index). Other advantage, is that Oracle can use the old index for answering queries while it builds the new index too using [alter index <index_name> rebuild online].
Cheers

H2 devide implicit and explicit created indexes by dictionary views?

For migrating amounts of data it is useful to drop and recreate indexes and referencing constaints. A implicit created index by defining a primary/unique key constraint will be dropped implicitly by dropping the before mentioned constraint. Creating such a constraint after creating an equivalent index with the constraint name will result in an other behaviour. The explicit created index will not be dropped by dropping the referencing primary/unique key constraint.
So far so good and well known. The question is: Which dictionary view columns will show me the difference between implicit and explict created indexes if I try to dynamically drop and recreate indexes and unique / primary key constraints?

Oracle Version is always helpful in answering questions, but for 9i you can find the system generated by:
dba_indexes.generated = 'Y'
or
'SYS_' naming convention for system generated indexes
or
dba_constraints.constraint_name = dba_constraints.index_name
Hope this helps - JTommaney

Performance issue with drop and re-create index

My database table has about 2 million records. The index in the table was not optmized, so we created a new index lets call it index2. So this table now was the original index (index1) and the index2. We then inserted data into this table from the other box. It was running for a few weeks.
Suddenly we noticed that a query which used to take a few seconds now took more than a minute. The execution plan was using the index2 which technically should be faster. We checked if the statistics were upto date and it was. So then we dropped the new index, re-ran the query and it completed in 10 sec's. It was usign the old index. This puzzled me since the point of the index2 was to make it better. So then we re-created index2 and genrated stats for the index. Re-ran the query and it completed in 5 sec's.
Everytime we timed to run the query, I shutdown and restarted the box to clear all cache's. So all the time I have specified are pure time's and not cached. The execution plan using index2 taking 1 min and 5 sec's are nearly the same, with very minior difference in cost and cardnitality. Any ideas why index2 took 1 min before and after drop and create again takes only 5 sec.
The reason I want to find the cause is to ensure that this doesn't happen again, since its impossible for me to re-create the index everytime I see this issue. Any thoughts would be helpful.

Firstly the indexes are different index1 is only on the time column, where as index2 is a composite index consisting of 3 columns.
Here are the details. The test that I did were last friday, 3/31. Yesterday and today when I executed the same query I get more increased times, yesterday it took 9 sec amd today 17 sec. The stats job kicked in on both days and is upto date. This table, nothing gets deleted. Only added.
3/31
Original
Elapsed: 00:01:02.17
Execution Plan
0 SELECT STATEMENT Optimizer=CHOOSE (Cost=6553 Card=9240 Bytes
=203280)
1 0 SORT (UNIQUE) (Cost=6553 Card=9240 Bytes=203280)
2 1 INDEX (FULL SCAN) OF 'EVENT_NA_TIME_ETYPE' (NON-UNIQ
UE) (Cost=15982 Card=2306303 Bytes=50738666)
drop index EVENT_NA_TIME_ETYPE
Elapsed: 00:00:11.91
Execution Plan
0 SELECT STATEMENT Optimizer=CHOOSE (Cost=7792 Card=9275 Bytes
=204050)
1 0 SORT (UNIQUE) (Cost=7792 Card=9275 Bytes=204050)
2 1 TABLE ACCESS (BY INDEX ROWID) OF 'EVENT' (Cost=2092
Card=2284254 Bytes=50253588)
3 2 INDEX (RANGE SCAN) OF 'EVENT_TIME_NDX' (NON-UNIQUE
) (Cost=6740 Card=2284254)
create index EVENT_NA_TIME_ETYPE ON EVENT(NET_ADDRESS,TIME,EVENT_TYPE);
BEGIN
SYS.DBMS_STATS.GENERATE_STATS('USER','EVENT_NA_TIME_ETYPE',0);
end;
Elapsed: 00:00:05.14
Execution Plan
0 SELECT STATEMENT Optimizer=CHOOSE (Cost=6345 Card=9275 Bytes
=204050)
1 0 SORT (UNIQUE) (Cost=6345 Card=9275 Bytes=204050)
2 1 INDEX (FULL SCAN) OF 'EVENT_NA_TIME_ETYPE' (NON-UNIQ
UE) (Cost=12878 Card=2284254 Bytes=50253588)
4/3
Elapsed: 00:00:09.70
Execution Plan
0 SELECT STATEMENT Optimizer=CHOOSE (Cost=6596 Card=9316 Bytes
=204952)
1 0 SORT (UNIQUE) (Cost=6596 Card=9316 Bytes=204952)
2 1 INDEX (FULL SCAN) OF 'EVENT_NA_TIME_ETYPE' (NON-UNIQ
UE) (Cost=11696 Card=2409400 Bytes=53006800)
Statistics
0 recursive calls
0 db block gets
11933 consistent gets
9676 physical reads
724 redo size
467 bytes sent via SQL*Net to client
503 bytes received via SQL*Net from client
2 SQL*Net roundtrips to/from client
1 sorts (memory)
0 sorts (disk)
3 rows processed
4/4
Elapsed: 00:00:17.99
Execution Plan
0 SELECT STATEMENT Optimizer=CHOOSE (Cost=6681 Card=9421 Bytes
=207262)
1 0 SORT (UNIQUE) (Cost=6681 Card=9421 Bytes=207262)
2 1 INDEX (FULL SCAN) OF 'EVENT_NA_TIME_ETYPE' (NON-UNIQ
UE) (Cost=12110 Card=2433800 Bytes=53543600)
Statistics
0 recursive calls
0 db block gets
12279 consistent gets
9423 physical reads
2608 redo size
467 bytes sent via SQL*Net to client
503 bytes received via SQL*Net from client
2 SQL*Net roundtrips to/from client
1 sorts (memory)
0 sorts (disk)
3 rows processed
SQL> select index_name,clustering_factor,blevel,leaf_blocks,distinct_keys from u ser_indexes where index_name like 'EVENT%';
INDEX_NAME CLUSTERING_FACTOR BLEVEL LEAF_BLOCKS DISTINCT_KEYS
EVENT_NA_TIME_ETYPE 2393170 2 12108 2395545
EVENT_PK 32640 2 5313 2286158
EVENT_TIME_NDX 35673 2 7075 2394055

IDES system copy ..error during IMPORT_ABAP..unable to create indexes

Hi all,
I am doing a IDES system copy. I ran the report SMIGR_CREATE_DLL , the export activities have been completed successfully as well on the source system. Now on the target system, during the import, I am getting the following error in the log file SAPDFACT.log.
(DB) ERROR: DDL statement failed
(CREATE INDEX "/BI0/E0RSTT_C06~P" ON "/BI0/E0RSTT_C06" ( "KEY_0RSTT_C06P" , "KEY_0RSTT_C06T" , "KEY_0RSTT_C06U" , "KEY_0RSTT_C061" , "KEY_0RSTT_C062" , "KEY_0RSTT_C063" , "KEY_0RSTT_C064" , "KEY_0RSTT_C065" , "KEY_0RSTT_C066" , "KEY_0RSTT_C067" , "KEY_0RSTT_C068" ) TABLESPACE PSAPSR3 STORAGE (INITIAL 65536 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )
DbSlExecute: rc = 99
(SQL error 1408)
error message returned by DbSl:
ORA-01408: such column list already indexed
(DB) INFO: disconnected from DB
The owner for this table is SAPSR3. Some oracle forums suggested to drop the index before recreating it. But when i do "drop index SAPSR3."/BI0/E0RSTT_C06~P..it says.."the specified index does not exist". But when I go to recreate this index, it doesn get created successfully. After that when I re-run the import, it again fails. Suprisingly..now if i go to check if this index is present thru a sql querry:
select owner, object_name, object_type from dba_objects where object_name='SAPSR3."/BI0/E0RSTT_C06~P"', it tells "no rows selected". This is happening everytime, I create an index, where it gets created successfully, and the import again fails with the same error in SAPDFACT.log.
I found an SAP note 885441 named..common errors during migration..although mine isnt a migration..my both source and destination are Red hat 64 bit platform.
The note 1st asks to download the latest R3load..which I did and extracted in the kernel directory of the source..then it also asked to edit the .TSK file..in my case..SAPDFACT.TSK..where the lines:
I /BIC/E<Cubename>~<index> C err
to I /BIC/E<Cubename>~<index> C ign..
I did that..this time..the import again fails..but in the SAPDFACT.log..it complains about some other index..n the same gets generated in the .TSK file as well..the earlier index error is not again generated.
I am not sure..what is going wrong..my export went through successfully.i have done the prep steps for export as well..before that i ran the SMIGR_CREATE_DLL report as well..
Any inputs are highly appreciated..
Thanks,
Akshay

Hi,
Check SAP Note 1166589 - Table converter: DB error when creating secondary indexes
Thanks
Sunny

Process Chain error while creating index on cube

Hi All,
I have two process chain P1 daily(except sunday) and P2 weekly(sunday), both have same process, i.e. cube C1 is loaded with same infopackage in both infopackage.
Now, on saturday after laoding the content index creating process on cube c1 is failed by process chain P1, but on sunday P2 have laoded C1 correctly and created indexes.
Now, my doubt is wheather i repeat process chain P1 from creating indexes or there is no need as indexes on cube are created by PC 2.
kindly suggest,
Regards,
Rajvinder

Hi Raj,
There is no need of running the process chain P1, the data has been bought by the process chain P2.
If there are any filters/data selection in infopackage level then you need to run the process chain P1.
Be make sure about the process chains and there infopackages/dtp's.
With Regards,
Ravi Kanth

Error while creating index on ep 6.0 9 sr1 (trex 6.1).

Hell o all,
I am getting following error while creating index on ep 6.0 9 sr1 (trex 6.1).
Index could not be created; creating index failed: general configuration error (Errorcode 2030)
can any on ehelp.
thanks and regards
Rajendra

Hi,
We are running TREX 6.1.09.00 on EP6.0.9.0.0 and KMC6.0.9.0.0.
We are experiencing the same problems, even after changing the value in the .ini file as specified in NOTE 766197.
After doing changes, I restarted the server after doing the changes.
Alessandro, have you got any ideas for fixing this?
Message was edited by: Bjorn Bjornstad

After Creating Index ???

Similar Messages

Maybe you are looking for