An additional unique index has been added to a table which already having the 19 indexes. CRDD for the same has been done succesfully. We have seen the same getting reflected in GTD as well as at informix level.

As we go to select the index in change keys in Maintain Session, the newly added index does not appear in list, even after doing the Create Runtime DD for the session.

Have you tried creating a new session, just to see if the new index shows up on the session? To me it still looks like a data dictionary issue.

Dear Mark,
Thank you for your response. On new session also the new index is not appearing it seems that BaanIVC4 only consider the index till 19 the 20th one does not appear in any case.
Regards.

I have not heard of that limitation and I am not sure we have any tables with 19 or 20 indexes. I will look when I get a chance.

According to the Infor LN 6.1 Programmers Guide:


Known limits

Reports
sorting doubles correct to 6 decimal places
maximum 255 fields on a report (including array elements)

Bshell
maximum string buffer size is 4K – be careful when concatenating strings with '&' sign
maximum function stack depth is 500

Bic
maximum 255 arguments per function
maximum 32K variables per compilation
maximum BRANCH of 32K (BRANCH refers to the amount of generated code per function, including macros etc.)

SQL
The nesting level of subqueries is limited to 10. The nesting level is defined as follows. The nesting level of the main query is 1. The nesting level of a sub query immediately contained in the main query is 2. The nesting level of a sub query immediately contained in another sub query is the nesting level of that sub query plus 1.
The number of index hints that can be given on a table is limited to 4.
The SQL processor has no limit on the length of string values. However, the databases may impose restrictions on the length of string values. It is advised to keep the length of string values (including string literals and string values resulting from concatenation) below 4K.

Tables
maximum record length is 3072 bytes (for multi-byte columns take a factor 2 into account. For example, a multi-byte string of 256 characters will be 512 bytes long in a multi-byte environment.)
maximum number of fields is 1024
maximum field length is 3072 bytes
maximum number of indices per table is 20:eek:

Indexes
maximum index length is 500 bytes
maximum number of fields is 24 (no combined fields)

I have never rechead any one of them, but i think this is reason for your problem.