What's new in Customer Journeys?

Connect and learn more! ×
Incident indexes exceeded — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Incident indexes exceeded

Received Response
edited Aug 11, 2021 12:14PM in General Technical Discussions 1 comment


Advice 15, effictive 30 max indexes


Hi all,

The current incident object allows (as of 21A) a total of 30 indexes. This was 23 in prior releases. Oracle support advice is to not exceed 15 (or 18):

The purpose of an index is to speed up record searches when searching by the indexed field. For example, if you have an incident custom field called language, and you frequently search your knowledge base for all incidents related to a specific language, you would want this custom field indexed to improve search performance. There are also drawbacks to having custom fields indexed. Specifying too many indexes on a specific table can degrade search performance rather than improve it. In general, it is best to have fewer than 15 total fields indexed in any given table. Please review the following Answer for

Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!