INDEX Inconsistence on ORACLE DB

[Former Member]

Hello all!

I have a strange problem in our system (NW 7.0 on Oracle 10.0.2)

Phase CHECK_REQUIREMENTS: Open ABAP Dictionary Conversions

-

---

Some open conversion requests still exist in the ABAP Dictionary for the

following ABAP Dictionary objects. To avoid inconsistencies and loss of

data, you must process these conversions first.

Object Type Object Name

Table Index EDIDC ~ 4

I try to adjust index EDIDC ~ 4 of the table EDIDC with SE14 transaction, but this index is not in the Dictionary.

If I check the consistence of the Table, I obtain

Database object for EDIDC is inconsistent: (Secondary indexes)
ABAP Dictionary Database 
Index does not exist Index EDIDC~4
  MANDT 
  STATUS 
  MESTYP 

I try to check from DB levels, the set of the index of the table and I obtain that the index EDIDC~4 exist into DB:

SQL> select INDEX_NAME, TABLE_NAME from dba_indexes where TABLE_NAME = 'EDIDC';
INDEX_NAME                     TABLE_NAME
-
 -
EDIDC~Z04                      EDIDC
EDIDC~4                        EDIDC
EDIDC~Z01                      EDIDC
EDIDC~Z05                      EDIDC
EDIDC~1                        EDIDC
EDIDC~0                        EDIDC
EDIDC~2                        EDIDC
EDIDC~3                        EDIDC
8 rows selected.

The index is into DB but not into ABAP dictionary.

Is there anyone that tell me what kind of activity I have to do to solve the issue?

Thank you very much

Davide BRUNO

[markus_doehr2 · Accepted solution]

> Some open conversion requests still exist in the ABAP Dictionary for the

> following ABAP Dictionary objects. To avoid inconsistencies and loss of

> data, you must process these conversions first.

> I try to adjust index EDIDC ~ 4 of the table EDIDC with SE14 transaction, but this index is not in the Dictionary.

That index is listed either in the 'mass processing" queue in SE14 or in the 'created with import' queue. To find out use SE14 and use the menue point 'DB Requests'.

Markus

[Former Member · Accepted solution]

Thank you very much Markus,

The index was listed in the 'created with import' queue. I delete it from the list, and now the problem is solved.

Thank you very much for the help

Davide BRUNO

[markus_doehr2 · Accepted solution]

> The index was listed in the 'created with import' queue. I delete it from the list, and now the problem is solved.

I would have created that index rather than to delete it from the list

Markus

[volker_borowski2]

Hi,

Simply refer to the upgrade guide how to solve this.

There is a description how to resolve all complains the the PREPARE phase might throw up.

It looks like a previous upgrade or a support package has left some unprocessed conversions.

Guessing from the description, it could be the deletition of this index.

But you should check in SE14 for the open conversion / conversion steps,

what was the intended conversion (ie. DROP or DROP and create diffrent...)

Volker