SQE Indexes Advised

[Former Member]

Hi Friends,

In my installation of ECC 6.0 with sap basis 17 and kernel 7.0 patch level 186, in transaction dbacockpit we have a lot of "SQE Indexes Advised" and if we order them by "Times Advised" in 15 of the 20 first positions we found tables DD*.

is it correctly?

In the instance profile the parameter dbs/db4/nqe_optimize_method is not active. should be it active?

The database access is slow but the sap process response quickly.

What can we analize?

Thanks in advanced.

[Former Member]

Hi Francisco,

first of all the parameter dbs/db4/nqe_optimize_method should never be active !

Then, the "index advised" overview is very risky to - just - create indexes. Each SQL, that is the root cause for the advisory should be investigated and then perhaps this index or a different one should be created.

Unfortunately, this needs a bit experience ...

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

[Former Member]

Hi Volker,

I don't understand why there are tables of the dictionary in the list because this index are standard and use in standard programs.

If the database was ms sql or oracle I am sure that the problem was in the database statistics or parameters but in as400 db2 I don't knwon that can be....

Thanks in advanced.

Paco.

[Former Member]

Hi Paco,

tja, that are the differences on the different platforms ...

DB2/400 advises a lot of indexes - evenb when they are not useful - it is more "a just try" and get more statistics - even when it turns out to be noot useful. So, it is always risky, to just blind to create the indexes ...

You can expect, that in the DD area are missing no indexes. Even when in the System catalog area one index seems to miss ...

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

[Former Member]

Hi Volker,

The database seem that is use bad path to access data. By example in VA01 there are a lot of high time to access tables o view like V_CF_MCHB , V_CF_MKOL , INOB, KSSK, etc,etc...

I see in dbacockpit in system catalog view in systables for this tables INOB, KSSK that the last change data is "2008-11-10" and I update my kernel in April 2009.

Is it possible I need to regerate sql packages?

I see that the database is slow when access to the table by the fields of the primary key in ABAP dictionary.

Thanks for your help...

Paco.