Cube Re-Partitioning

[former_member205400]

I have this cube that did not have partitioning and so I did a complete re-partition on 0calmoth.

Upon the partitioning I have an FACT index error when I attempt to re-index it. The error is:

CREATE BITMAP INDEX

"SAPSR3"."/BIC/FZSM_C001~090" ON "/BIC/FZSM_C001"

( "KEY_ZSM_C0016" ) PCTFREE 5 INITRANS

2 MAXTRANS 255 STORAGE ( INITIAL 16 K NEXT

2560 K MINEXTENTS 1 MAXEXTENTS UNLIMITED

PCTINCREASE 0 FREELISTS 4 FREELIST GROUPS 1

BUFFER_POOL DEFAULT ) LOCAL PARALLEL TABLESPACE

"PSAPSR3I" NOLOGGING COMPUTE STATISTIC

SQL-END: 06/07/2011 09:55:07 00:00:00

SQL Error: ORA-01408: such column list already indexed

I attempted to drop the indexes, repair them, adjust them using se14.

I'm thinking I need to drop the cube data, then re-index, and re-load the cube.

Any way I can make this adjustment without dropping the data?

Mike

[former_member205400]

In my index check (RSDU_INFOCUBE_INDEXES_CHECK) i see this message:

TABNAME                        IND DBIDXNAME          FIELDNAME                      TYPE_EXPEC TYPE       T UNIQUE_EX UNIQUE    U P P P STATUS   S

/BIC/FZSM_C001                 090 /BIC/FZSM_C001~090 KEY_ZSM_C0016                  BITMAP                  NONUNIQUE             X     INVALID  R
/BIC/FZSM_C001                 100 /BIC/FZSM_C001~100 KEY_ZSM_C0017                  BITMAP                  NONUNIQUE             X     INVALID  R
/BIC/FZSM_C001                 110 /BIC/FZSM_C001~110 KEY_ZSM_C0018                  BITMAP                  NONUNIQUE             X     INVALID  R
/BIC/FZSM_C001                 120 /BIC/FZSM_C001~120 KEY_ZSM_C0019                  BITMAP                  NONUNIQUE             X     INVALID  R
/BIC/FZSM_C001                 900 /BIC/FZSM_C001~900 SID_0CALMONTH                  BITMAP                  NONUNIQUE             X     INVALID  R

Dims ZSM_C0016 and ZSM_C0017 are line item dimensions

Mike

[former_member205400]

and I'm seeing the message in se14

Index could not be created completely in the database

Message no. DI006

Diagnosis

It was not possible to create the index in the database.

This could be caused by the fact that an index with the same name exists in the database, but it is unknown to the ABAP/4 Dictionary. Activating the index in the ABAP/4 Dictionary is possible, but it is not possible to create it in the database.

Mike

[former_member205400]

So I had to drop the data, adjust the table using se14 (both E and F) and then it was all good.