Reoccuring missing secondary indexes in BI systems

Hi Gurus,
I'm been experiencing the problem of missing secondary indexes for some time, and I would like to get to the bottom of this problem.
These are a few of the missing indexes (from DB02):-
/BIC/F100294-900
/BIC/F100365-900
/BIC/F100366-900
/BIC/F100368-900
/BIC/F100369-900
/BIC/F100386-900
/BIC/FZCFIGRLP-900
/BIC/FZCGLECRD-900
/BIC/FZCGLECRD2-900
/BIC/FZCGLECRD3-900
TSP03-1
TSP03L-A
Any idea what could be causing this???
And how do I solve this problem??? And how can I prevent these from reoccuring again???
Thanks.
Cheers,
KeatSeong

I see missing indexes on DB02 as well and ran SAP_INFOCUBE_INDEXES_REPAIR and I just have a couple more questions that I think is relevant to this chain:
1) It repaired some fact indexes like /BIC/F* and dimension indexes like /BIC/D* but in the report showed as follows for those cubes:
0 ZPP_C008 : 0 secondary indexes repaired.
2) I had some other dimension indexes like /BIC/D* that did not get repaired and I'm wondering why. See 4) below for how I repaired those.
3) I ran RSRV and these missing indexes like /BIC/D* do not show up as being an issue
4) When I run RSDU_INFOCUBE_INDEXES_REPAIR on that missing index like /BIC/D* I get E_REPAIRED = 0 and system error: RSDU_INFOCUBE_INDEXES_REPA_ORA but when I refresh DB02 the index is gone. When I go to RSDU_INFOCUBE_INDEXES_REPA_ORA and run it I got e_reparied - 11
Thanks for all your help.
Mike
Edited by: Michael Hill on May 26, 2010 6:49 PM

Similar Messages

Missing secondary indexes

Hello Gurus,
Hope you are doing good ! I have few missing secondary indexes. I have corrected them in rsrv with the correct error option but still most of them seem to be back in DB02. Warnings have occured for few cubes being : Oracle:Index/BI0/SDOC_NUMBER~0 has possible degenareted.
I checked in the process chains but the indexes are successfully built. Any sugestions pls let me know.
Kind Regards,
Sunitha

Hi Sunitha,
Try checking these indices from cube/DSO Performance tab and try with the repair option available there.
Sometimes, it might be possible to the tablespace problem to build the indices. Check those too also from DB02.
Regards,
Srinivas.

Missing secondary index after TDMS data deletion

We have done a TDTIM transfer to a single client system. The deletion technique used by TDMS is Drop-insert technique.
During our initial analysis, we found that many of the secondary indices are not re-created by TDMS at database level. For many few tables the secondary indices are re-created at the database level.
Will TDMS delete and re-create the secondary index for re-created (droped & created) tables during data deletion in receiver system ?
Why did TDMS re-create secondary indices for few tables and why it didnot re-create secondary indices for few other tables?
Thanks
Praven

Indexes are deleted from the receiver only in cases when they were not present at the DB level in the receiver system
prior to TDMS run. This is to avoid any kind of error/exceptions when records are inserted into the table.
You need to create these indexes manually.
In order to do so, you can follow the steps below:
1. Execute transaction DB02.
2. Select the button "missing indexes". A list of 1091 is shown
3. Place the cursor on the line "secondary indexes" and hit F9
4. Now hit "create on DB".
5. A popup will ask if you want to do a mass select. Press "Yes"
6. A further Popup will then ask for background processing. Say "Yes".
Best Regards,
Rupam

DBACOCKPIT reports missing secondary indexes even though they exist .

Hi all,
On our BI system (7.0) on DBACOCKPIT, system reports some secondary indexes missing even though they already exist.
Any suggestions for the cause of the problem or what to investigate?
regards,
K

Hi,
When was statistics updated last time. Update the statistics and chk if the problem is still shown.

Missing secondary indexes ~P

Hi, when i check the Tx DB02 i have an alert with somw missing indexes like that
/BI0/E0BPM_C01~P
/BI0/E0BPM_c02~P
/BI0/E0COPA_C02~P
/BI0/E0COPA_C04~P
But i don't have option to create this index, so?
how can i create this indexes?

hi,
You should have the authorization for maintenance for creating the missing indexes.
Please check if you have the authorization for object S_RZL_ADM , if not then ask some BASIS person to do it,
regards,
Arvind.

Error when recreate secondary indexes

hi all
in db02 i have two missing secondary indexes.
when i try recreate :
in db02 select missing index -> choose processing type: direct processing -> create
i have error :
Internal error 1 in module DD_LONGNPROT_NAME_GET occurred
Diagnosis
An unexpected SQL error occurred in the ABAP/4 Dictionary interface.
System response
A system log entry has been written. This gives more precise information about where the termination occurred and the reason for the termination. The current transaction has been cancelled.
Procedure
Please check the system log and eliminate the cause of the SQL error.
in sm21 no errors
in db alert log no errors
how can resolve this problem?
thanks

Hi Andrey,
Please try to active the secondary indexes in transaction SE14. Please gothrough the note 1248769 as how to active the
indexes.
Many thanks.
Mohammed Hussain.

Transaction DB02 = Missing Tables and Indexes shows under Secondary indexes from package $tmp

Hi SAP Gurus,
I noticed on our SAP business warehouse (BW) system (NetWeaver 7.0 based on AIX/Oracle 11g) in transaction DB02 => Diagnostics => Missing Tables and Indexes under Secondary indexes, 26 indexes, in package $tmp:
The indexes are defined, but they don't have been created on the database.
When I try to create them via the database tool, I am getting the warning:
Does the warning raise up, because they where defined in the $tmp package?
I was looking in SAP notes for a solution for this "warning" concerning the /BIC/F-Indexes but I didn't found yet anything helpful ...
Thanks for your help and ideas ...
Best regards
Carlos

Hi Carlos,
These are secondary indexes created during process chains in BI to improvise performance.
You may refer below SCN blogs on creation of these indices in BI.
Secondary Index - Improving DSO insert/read performance
How to Create Secondary Index on DSO in SAP BW
Hope this helps.
Regards,
Deepak Kori

The fact table of InfoCube 0OPA_C11 is missing 2 secondary indexes

Hello experts,
in RSRV i got the above mentioned message for my InfoCube 0OPA_C11. Before I tried to delete, repair and build up my indices in performance tab of the InfoCube.
I followed SAP Note '401242 - Problems with InfoCube or aggregate indexes'.
-> SAP_INFOCUBE_INDEXES_REPAIR repaired indexes and show no further problem, but problem still exists, in performance tab light is red and RSRV brings same message.
Does someone have any idea what further I can do?
Best regards,
Peter

Peter, refer to note 928037, it's FAQ about MaxDB indexes. I gave it a quick reading and I believe the answer to this issue lies beneath this doc! There are ways to check consistency of individual index, bad indexes and ways of eliminating them.
Also, refer to the below blog. Check the status of the secondary index in this case. I suspect they are bad or missing. There are ways to recreate them. Keep your basis guys in the loop.
http://wiki.sdn.sap.com/wiki/display/MaxDB/MaxDBIndex%28Secondary+Key%29
Hope this helps.
Edited by: Mann Krishna on Sep 10, 2010 3:50 PM

How do you open a Numbers file sent from another Mac user with same operating system, i get a pop up that says I'm missing an index.hml file??? HELP PLEASE

how do you open a Numbers file sent from another Mac user with same operating system, i get a pop up that says I'm missing an index.hml file??? HELP PLEASE

The operating system may be the same but the Numbers applications are likely different. You need to get the apps in sync. Unfortunately, the Numbers (and Pages as well) saga is pretty confusing (and frustrating). Here's some info from the iWork resident version expert (PeterBreis0807):
Pages '09/'08 can not open Pages 5 files and you will get the warning that you need a newer version.
Pages 5.2 can open Pages '09 files but may damage/alter them. It can not open Pages '08 files at all.
Older versions of Pages 5 can not open files from later versions of Pages 5.
Once opened and saved in Pages 5 the Pages '09 files can not be opened in Pages '09.
Anything that is saved to iCloud and opened in a newer version of Pages is also converted to Pages 5 files.
All Pages files no matter what version and incompatibility have the same extension .pages.
Pages 5 files are now only compatible with themselves on a very restricted set of hardware, software and Operating Systems and will not transfer correctly on any other server software than iCloud.
Apple has removed almost 100 features from Pages 5 and added many bugs.

Is it worth creating secondary index on BKPF table ?

Hello,
One of my clients is using ECC version 5.0. I have a requirement wherein I need to fetch the data from BKPF table based on AWKEY, BUKRS and GJAHR. There is no standard secondary index available.
I have decided to create a secondary index on these fields in the following order:
1) MANDT
2) AWKEY
3) BUKRS
4) GJAHR
I know that creating secondary indexes does improve performance during data retrieval. But when I checked the total number of entries in BKPF table in production system, there are more than 20 lac 2 million records.
I am worried that creation of secondary index will create another table of such a large size in production that has data sorted on the above fields. Also, the RAM of production system is 6 GB.
Please suggest if creation of secondary index is a good measure OR should I recommend the client to increase the system RAM?
Regards,
Danish.
Edited by: Thomas Zloch on Oct 3, 2011 3:01 PM

Hi,
Secondary Index on BKPF-AWKEY has been successfully created in production. The report which used to timeout in foreground as well as in background is now executing in less than 10 seconds !!
Client is very much satisfied with this. But, there is one problem that we are facing now is that when the user is changing an existing billing document via VF02, on SAVE, system takes a very long time to save the changes done.
We monitored the processes via SM50 and found that there was a sequential read on BKPF table.
Before transporting the index in production, system approximately took not more than 5 seconds to save the Billing Document. But now system takes more than 20 minutes just to save the billing document via VF02.
I really don't know what has gone wrong. I can't figure out if I have missed any step while creating the index.
I did the following,
1) Created a Secondary index on BKPF, saved it in the transport request and activated it. Since the index was not existing in database ORACLE, I activated and adjusted the table via SE14. Now, index exists on database as well. Working perfectly in development.
2) Imported the transport request to Production. Checked in SE11. Index was existing and active. Also, index existed in database ORACLE.
Have I missed anything ? Is it required to activate and adjust the database via SE14 in production too ?
Regards,
Danish.

Creation of secondary indexes due to heavy flow of messages in ecc smq2

Hi gurus,
So we are facing smq2 issues from last 15 days in Ecc system due to some Time Limit Exceed and some times Object is Locked by the user xxxx
So finally we decided to go for creating seconday indexes in Ecc side , So here my question is there any thing required from Pi side while creating
Secondary indexes why i am asking this question is there is no issues From PI end after reaching to target(ECC) system only messages got stucking
in smq2 and facing issues .Below is the interface details.
ECC-FSCM
SAP ECC 6.0
FSCM
CreditCommitment_In and CreditCommitment_Out
CC_ProxySender_FSCM
CC_ProxyReceiver_FSCM
Plz reply back .
Regards
Madhu

If you had gone through the replies in your previous post, Iñaki Vilaand myself already provided the report name which needs to be scheduled to clear the messages in queues.
Plz provide the permanent fix for this issue

Regarding secondary index

how and when we create secondary indexes and what are the advantages and disadvantages of secondary indexes?

Hi
Index: Technical key of a database table.
Primary index: The primary index contains the key fields of the table and a pointer to the non-key fields of the table. The primary index is created automatically when the table is created in the database.
Secondary index: Additional indexes could be created considering the most frequently accessed dimensions of the table.
Structure of an Index
An index can be used to speed up the selection of data records from a table.
An index can be considered to be a copy of a database table reduced to certain fields. The data is stored in sorted form in this copy. This sorting permits fast access to the records of the table (for example using a binary search). Not all of the fields of the table are contained in the index. The index also contains a pointer from the index entry to the corresponding table entry to permit all the field contents to be read.
When creating indexes, please note that:
An index can only be used up to the last specified field in the selection! The fields which are specified in the WHERE clause for a large number of selections should be in the first position.
Only those fields whose values significantly restrict the amount of data are meaningful in an index.
When you change a data record of a table, you must adjust the index sorting. Tables whose contents are frequently changed therefore should not have too many indexes.
Make sure that the indexes on a table are as disjunctive as possible.
(That is they should contain as few fields in common as possible. If two indexes on a table have a large number of common fields, this could make it more difficult for the optimizer to choose the most selective index.)
Accessing tables using Indexes
The database optimizer decides which index on the table should be used by the database to access data records.
You must distinguish between the primary index and secondary indexes of a table. The primary index contains the key fields of the table. The primary index is automatically created in the database when the table is activated. If a large table is frequently accessed such that it is not possible to apply primary index sorting, you should create secondary indexes for the table.
The indexes on a table have a three-character index ID. '0' is reserved for the primary index. Customers can create their own indexes on SAP tables; their IDs must begin with Y or Z.
If the index fields have key function, i.e. they already uniquely identify each record of the table, an index can be called a unique index. This ensures that there are no duplicate index fields in the database.
When you define a secondary index in the ABAP Dictionary, you can specify whether it should be created on the database when it is activated. Some indexes only result in a gain in performance for certain database systems. You can therefore specify a list of database systems when you define an index. The index is then only created on the specified database systems when activated
Regards

What is the "No database index" means when you Creating Secondary Indexes?

HI,
   I'm Creating Secondary Indexes in the maintenance screen of the table(se11)
   There are three options under "Non-unique Index":
   1.Index on all database systems
   2.For selected database systems
   3.No database index
My questions is :
What do u mean by "No Database Index" and when is it used.
Can anybody plz tell me what's the difference of this three options ?
Here is what i found in the help:
   No database index: The index is not created in the database. If you
   choose this option for an index that already exists in the database,
   it is deleted when you activate this option.

Hi,
It is clear from the help documentation,
Here see what the help document says:
Create the index in the database (selection)
Whether an index improves or worsens performance often depends on the database system. You can therefore set whether an index defined in the ABAP Dictionary should be created in the database.
This makes it easier to install a platform-specific customer system.
You can set this option as follows:
1. Index in all database systems: The index is always created in the database.
2. In selected database systems: The index is created depending on the database system used. In this option, you must specify the databases in which the indexes are to be created. You can do this either on an inclusive (list of systems on which it should be created) or an exclusinve (list of systems on which it should not be created) basis. In either case, you can list up to four different database systems.
3. No database index:: The index is not created in the database. If you set this option for an index that already exists in the database, it is deleted when you activate the table in the ABAP Dictionary.
Note: Unique indexes have an extra function, and must therefore always be created in the database. The database system prevents entries or index fields being duplicated. Since programs may rely on this database function, you cannot delete unique indexes from the database.
Hope it helps you,
Regards,
Abhijit G. Borkar

Secondary Index vs Secondary Indices

Hi All,
In the earlier version already we have the primary index,secondary indexes,But now iam going through the enhancements in NW 7.0 In this they mentioned Secondary indices as the new enhancement with NW 7.0,I know how to create the Secondary indices ,But i am getting the conffusion between secondary indexes (already we have) and the new Secondary Indices,So please could any one elobarate this or atleast URL'S which are relavant to this topic,It would be very help full to me.
Thank you..
Srihasa

new index are just different at workbench level, but are the same at database level. You may assign them to a Y or Z package (instead of the sap package, it was seen as a modification of the standard). They also have a dedicated object directory entry (R3TR XINX). http://help.sap.com/saphelp_erp2005vp/helpdata/EN/85/685a41cdbf8047e10000000a1550b0/frameset.htm
[Note 1257033 - Cookbook: Modification/enhancement for standard SAP system|http://service.sap.com/sap/support/notes/1257033]

Database tableAUFM hitting is taking much time even secondary index created

Hi Friends,
   There is report for Goods movement rel. to Service orders + Acc.indicator.
   We have two testing Systems(EBQ for developer and PEQ from client side).
   EBQ system contains replica of PEQ every month.
   This report is not taking much time in EBQ.But it is taking much time in PEQ.For the selection criteria I have given,both systems have same data(Getting same output).
The report has the follwoing fields on the selection criteria:
A_MJAHR     Material Doc. Year (Mandatory)
S_BLDAT     Document Date(Optional)
S_BUDAT     Posting Date(Optional)
S_LGORT     Storage Location(Optional)
S_MATNR     Material(Optional)
S_MBLNR     Material Documen(Optional)t
S_WERKS     Plant(Optional)
Client not agrrying to make Material Documen as Mandatory.
The main (first) table hit is on AUFM table .As there are non-key fileds as well in where condition,We have cretaed a secondary index as well for AUFM table on the following fields:
BLDAT
BUDAT
MATNR
WERKS
LGORT
Even then also ,in PEQ sytem the report is taking very long time ,Some times not even getting the ALV output.
What can be done to get teh report executed very fast.
<removed by moderator>
The part of report Soure code is as below:
<long code part removed by moderator>
Thanks and Regards,
Rama chary.P
Moderator message: please stay within the 2500 character limit to preserve formatting, only post relevant portions of the code, also please read the following sticky thread before posting.
Please Read before Posting in the Performance and Tuning Forum
locked by: Thomas Zloch on Sep 15, 2010 11:40 AM

Hi Friends,
   There is report for Goods movement rel. to Service orders + Acc.indicator.
   We have two testing Systems(EBQ for developer and PEQ from client side).
   EBQ system contains replica of PEQ every month.
   This report is not taking much time in EBQ.But it is taking much time in PEQ.For the selection criteria I have given,both systems have same data(Getting same output).
The report has the follwoing fields on the selection criteria:
A_MJAHR     Material Doc. Year (Mandatory)
S_BLDAT     Document Date(Optional)
S_BUDAT     Posting Date(Optional)
S_LGORT     Storage Location(Optional)
S_MATNR     Material(Optional)
S_MBLNR     Material Documen(Optional)t
S_WERKS     Plant(Optional)
Client not agrrying to make Material Documen as Mandatory.
The main (first) table hit is on AUFM table .As there are non-key fileds as well in where condition,We have cretaed a secondary index as well for AUFM table on the following fields:
BLDAT
BUDAT
MATNR
WERKS
LGORT
Even then also ,in PEQ sytem the report is taking very long time ,Some times not even getting the ALV output.
What can be done to get teh report executed very fast.
<removed by moderator>
The part of report Soure code is as below:
<long code part removed by moderator>
Thanks and Regards,
Rama chary.P
Moderator message: please stay within the 2500 character limit to preserve formatting, only post relevant portions of the code, also please read the following sticky thread before posting.
Please Read before Posting in the Performance and Tuning Forum
locked by: Thomas Zloch on Sep 15, 2010 11:40 AM

Reoccuring missing secondary indexes in BI systems

Similar Messages

Maybe you are looking for