Skip to Content
0
Former Member
Nov 27, 2012 at 11:06 AM

R3szchk gathers incorrect index names and cut's them off at 18 characters

38 Views

Hello,

we are in the process of a Unicode migration on our BW system (701 Kernel). During the import we noticed that nearly 50% of all our indexes

have been 'incorrectly' exported from the SAP dictionary while the STR-files got created by R3szchk.

We now have entries like this in the STR file:

/BIC/4EBCEBI08CG 1114701824

/BIC/4EBCEBI08CG~0 65536

/BIC/4EBCEBI08CG~0 65536

/BIC/4EBCEBI08CG~0 65536

/BIC/4EBCEBI08CG~0 65536

/BIC/4EBCEBI08CG~0 65536

/BIC/4EBCEBI08CG~0 65536

/BIC/4EBCEBI08CG~0 65536

/BIC/4EBCEBI08CG~0 65536

/BIC/4EBCEBI08CG~0 65536

/BIC/4EBCEBI08CG~0 65536

/BIC/4EBCEBI08CG~1 65536

/BIC/4EBCEBI08CG~1 65536

/BIC/4EBCEBI08CG~1 65536

/BIC/4EBCEBI08CG~1 65536

/BIC/4EBCEBI08CG~P 1772158976

While it should look like this (from DB Oracle 11.2.0.4):

SQL> select PARTITIONED, INDEX_NAME, INDEX_TYPE from dba_indexes where table_name = '/BIC/4EBCEBI08CG';

PAR INDEX_NAME INDEX_TYPE
--- ------------------------------ ---------------------------
YES /BIC/4EBCEBI08CG01 BITMAP
YES /BIC/4EBCEBI08CG~P NORMAL
YES /BIC/4EBCEBI08CG02 BITMAP
YES /BIC/4EBCEBI08CG03 BITMAP
YES /BIC/4EBCEBI08CG04 BITMAP
YES /BIC/4EBCEBI08CG05 BITMAP
YES /BIC/4EBCEBI08CG06 BITMAP
YES /BIC/4EBCEBI08CG07 BITMAP
YES /BIC/4EBCEBI08CG08 BITMAP
YES /BIC/4EBCEBI08CG09 BITMAP
YES /BIC/4EBCEBI08CG10 BITMAP
YES /BIC/4EBCEBI08CG11 BITMAP
YES /BIC/4EBCEBI08CG12 BITMAP
YES /BIC/4EBCEBI08CG13 BITMAP

14 rows selected.

Does anybody know where in the dictionary the information is gathered by R3szchk? I checked se11 and there the index name matches the index name on DB level. Also I checked table DD12L but the values in DBINDEX are either empty or do not match at all. My intention is to 'correct' our dictionary settings to match the index names on DB level so that R3szchk extracts the correct indexnames.

Btw. the DDL is gathered correctly it's just wrong in the STR files.

Kind Regards

Florian