Even I created properly Sec. Index, Why getting message, saying not ACTIVE?

[Former Member]

Hi Experts,

Y'day; IN dev SYSTEM, I created a Secondary index for SAP tbl, saved, activated too!

But, am getting the following message,

<b><i>Index does not exist in database system ORACLE</i></b>

Actually, previuosly also, I got the same message in another case, then I approached DBA, then they craeted and TRed, fine.

So, my curiousity is that, Why its happening like that? And How the DBA people r rectifying it?

ThanQ.<b></b>

Message was edited by:

Srikhar

[suresh_datti]

If you have access to the Tcode DB02, try it out to create the missing index in the database.. Usually it is a DBA's task.. nothing wrong in approaching the DBA again..

http://help.sap.com/saphelp_nwmobile71/helpdata/en/c4/3a7194505211d189550000e829fbbd/content.htm

~Suresh

[Former Member]

ThanQ Suersh,

Yes. I hv access DB02, so I navigated,

db02>Missing Indexes->Selecting/Highlighting my miseed Index--->Pressed the push button CREATE IN DB, so, they Its asking me to choose from the following 3 options,

1 - Direct processing,

2- Back Ground,

3- Enter for mass processing

In UR Link, note is,

<i>Choose the object and then choose Create in DB. You can now choose whether you want to create the object directly (online) or in the background (as a background job). (The latter option is only useful for indexes of large tables.)</i>

I wanna to create on BKPF, Is it a large table?

So, Which is my correct option, I mean Which one I hv to choose?

ThanQ.

Message was edited by:

Srikhar

Message was edited by:

Srikhar

[suresh_datti]

processing in background is always a safe bet..

~Suresh

[Former Member]

I'd be careful though creating indexes on tables such as BKPF which have some high volume use in transations. You need to make sure that the new index will not kill the standard SAP online processing performance...(Yes an additional index can do that by telling the online program to use the new and may be way less efficient index than the one SAP intended it to use...)

On the other hand the need to add an index to such a table usually comes from poorly understood or defined reporting requirements. A few more lines of ABAP could probably allow you to use one of the existing indexes and avoid a new index creation...

Enjoy

[Former Member]

follow these steps for creating secondary index.

1) In the maintenance screen of the table, choose Indexes.

If indexes already exist on the table, a list of these indexes is displayed. Choose CREATE.

2) In the next dialog box, enter the index ID and press ENTER.

The maintenance screen for indexes appears.

3) Enter an explanatory text in the field Short text.

You can then use the short text to find the index at a later time, for example with the R/3 Repository Information System.

4) Select the table fields to be included in the index using the input help for the Field name column.

The order of the fields in the index is very important. See What to Keep in Mind for Secondary Indexes.

5) If the values in the index fields already uniquely identify each record of the table, select Unique index.

A unique index is always created in the database at activation because it also has a functional meaning (prevents double entries of the index fields).

6) If it is not a unique index, leave Non-unique index selected.

In this case you can use the radio buttons to define whether the index should be created for all database systems, for selected database systems or not at all in the database.

7) Select for selected database systems if the index should only be created for selected database systems.

Click on the arrow behind the radio buttons. A dialog box appears in which you can define up to 4 database systems with the input help. Select Selection list if the index should only be created on the given database systems. Select Exclusion list if the index should not be created on the given database systems. Choose .

😎 Choose ACTIVE.

Check with below link and it may be useful

http://help.sap.com/saphelp_nw04/helpdata/en/cf/21f0f0446011d189700000e8322d00/content.htm

Thanks

Seshu

[Former Member]

ThanQ F.J.

I understand ur response. But, in one of my SELECT's WHERE clause, am using the STBLG(=filtering the BELNRs, which r NOT reversed), like

<b><i>SELECT BELNR WHERE STBLG = ' '.</i></b> (not exactly like this! actually, am using similarly to it, together with INNER JOIN with BSAD)

(I mean, I guess, we dont hv alternative for STBLG)

So, Do u hv any alternatives, to my above requirements?

Now, the report is taking 4 min. in DEV system & yielding 3 records! So, Do U mean that, Its better to NOT create the Index for BKPF, even though report wuld take 15 min. in PRODUCTION system?

thanq.

[Former Member]

ThanQ F.J.(/Sheshu)

I understand ur response. But, in one of my SELECT's WHERE clause, am using the STBLG(=filtering the BELNRs, which r NOT reversed), like

SELECT BELNR WHERE STBLG = ' '. (not exactly like this! actually, am using similarly to it, together with INNER JOIN with BSAD)

(I mean, I guess, we dont hv alternative for STBLG)

So, Do u hv any alternatives, to my above requirements?

Now, the report is taking 4 min. in DEV system & yielding 3 records! So, Do U mean that, Its better to NOT create the Index for BKPF, even though report wuld take 15 min. in PRODUCTION system?

thanq.

Message was edited by:

Srikhar

[Former Member]

Hi Srikhar,

It is very bad performance - 3 records getting in 4 minutes time,i don't think you can use secondary index ,it should be key problem,even you create secondary index.. ,most of the time we have performance problem for each development,some times as per customer req we need use non primary key in where clause ,so it will have bad performance.

I think you have to talk ur senior people regarding this i mean how should approach.

Thanks

Seshu