BR0970W Database administration alert - level: ERROR, type: MISSING_INDEX,

[Former Member]

Hi

I've noticed in the results of the DBCHECK job in DB13 that we have a number of warnings for missing indexes.

SAPNPIDB.BC_CMSRTS

SAPNPIDB.BC_SCCOMPAT

SAPNPIDB.BC_SCCOVERAGE

SAPNPIDB.BC_SCREQUIRED

SAPNPIDB.BC_SCVERSION

SAPNPIDB.BC_WA_SCH_LOG

SAPNPIDB.BC_WA_SYS_TO_GROUP

SAPNPIDB.SP_RESULTS

The strange thing is that no missing indexes are picked up be DB02. In SE11 these tables cannot be found. Checked at Oracle level and the tables exist but the indexes do not.

Does anyone know if these tables should have indexes?

If so what would be the best way to create these?

Regards,

Nic

[former_member195313]

Go to DB13 and check the output of "Check DB" if still there are some MISSING_INDEX entries then you should REBUILD them with following command ;

alter index <SCHEMA.INDEX_NAME> rebuild tablespace TABLESPACE_NAME;

Repeat the DB13 "Check DB" should be everything is green.

DB13 Warning CHECKDB Missing Index Situation | SAPBASISINFO

[Former Member]

First check the table in se14 and it should be in active state

You can create the missing_indexes in se11 just give the tablename --> select the indexes button and then click yes to create the index.

[former_member146451]

Dear CSCADMIN,

That would be true for ABAP tables, but those are Java stack tables, so SE14 there has nothing to do.

Regards.

[Former Member]

Hi

We are getting frequently the below error

BR0970W Database administration alert - level: ERROR, type: MISSING_INDEX, object: (table) SAPSR3./BIC/QUERYINPUT

BR0970W Database administration alert - level: ERROR, type: MISSING_INDEX, object: (table) SAPSR3./BIC/QUERYOUTPUT

but I tried to solve for the below process

se38 -> Program name:RSAR_PSA_PARTITION_CHECK-> Execute -> Repair(select option)->Execute.

but it is not solving permentaly.

could you please suggest any one to resolve ?

[fjhernanz]

Hi,

What is the result from SE14 for these indexes? In case these do not exist at DB level you can try to create them directly.

Another possibility is to add them to the DBDIFF table, and will be excluded from the check (See SAP note 33814 about this)

Br,

Javier