What is Oracle's policy for custom indexes on seeded EBS tables?
Some of the seeded tables are heavily used by our custom programs. At times we had found additional (custom) indexes could significantly improve performance for a custom program. Examples of such tables are AP_INVOICES_ALL, GL_JE_HEADERS, and GL_JE_LINES. Yet some of the custom indexes could have negative performance impact on some other seeded and/or custom programs. Some Oracle docs mentioned that custom indexes're not recommended but it didn't appear they're prohibited. What is Oracle's policy for custom indexes on seeded EBS tables? What kind of testing can be done to assess the impact of such indexes before production implementation?