• Article Type: General
• Product: Aleph
• Product Version: 19.01

Description:
I see the following for Z30 table in the v19 util a/17/14 z30_id12 and z30_id13:
...
IND z30_id12 4M 0K TSX_ONE
IND z30_id13 4M 0K TSX_ONE
__________________________________________________________


Exist in the Database:

INDEX_NAME STATUS INDEX_TYPE UNIQUENESS COLUMN_NAME
--------------- ------- ---------- ----------- --------------------
...
Z30_ID12 VALID NORMAL NONUNIQUE Z30_SUB_LIBRARY
Z30_ID12 VALID NORMAL NONUNIQUE Z30_EXPECTED_ARRIVAL
_DATE

Z30_ID13 VALID FUNCTION-B NONUNIQUE Z30_ARRIVAL_DATE
ASED NORMA
L

Z30_ID13 VALID FUNCTION-B NONUNIQUE SYS_NC00064$
ASED NORMA
L

Z30_ID13 VALID FUNCTION-B NONUNIQUE Z30_ITEM_PROCESS_STA
ASED NORMA

Resolution:
I see the same in util a/17/14 for the usm50 z30 on our server, so I think that it is normal.

That is what you see when the index is defined on multiple fields:

CREATE INDEX &1.Z30_ID12 ON &1.Z30 (Z30_EXPECTED_ARRIVAL_DATE,Z30_SUB_LIBRARY ASC)
CREATE INDEX &1.Z30_ID13 ON &1.Z30 (Z30_ITEM_PROCESS_STATUS,Z30_ARRIVAL_DATE,SUBSTR(Z30_REC_KEY_2,1,9) ASC)

This behavior is described in KB 16384-4002.

• Article last edited: 10/8/2013