Document 658930.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

Copyright (c) 2024, Oracle. All rights reserved. Oracle Confidential.

E1: DB: How To Find and Rebuild Missing Indices For EnterpriseOne Tables (Doc ID
658930.1)

In this Document

Goal
Solution
References

APPLIES TO:

JD Edwards EnterpriseOne Tools - Version SP24 and later

Information in this document applies to any platform.

GOAL

You have performance issues on your system and have noticed that there are missing indexes for standard tables. You
would like to know if there is a report to obtain a list of all missing indexes for each environment in EnterpriseOne?

SOLUTION

Use the following UBEs:

• R9698711 -- List tables that differ from EnterpriseOne Specs

• R9698713 -- Index Recreation

Additional information:

• R9698711 identifies all tables that have differences in columns and indexes between the physical database
and the EnterpriseOne specs. It gives a list of tables that would require generating an index for. GCS
recommends running R9698713 in proof mode to view discrepancies.

• R9698713 will regenerate all indexes in a datasource. This report has no mechanism to validate whether the
indexes are corrupt, etc. It will just recreate indexes in the specified datasource. The Primary Keys get created
as well provided they are available in the table specification when view via Table Design Aid.

Oracle Support recommends running both reports; first R9698711 then R9698713 to do a bulk regeneration of indexes
of the tables in the datasource you select.

1 de 2 15/01/2024, 03:55 p. m.
Document 658930.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

NOTES:

• The primary key does NOT get rebuilt as part of rebuilding an index (if they are not available in table
specification) . If you are missing Primary Keys (PKs), you will need to create it at the DB level, or recreate
the table using OMW.
• If the customer uses OMW, then all the data will get wiped out, so they should export the table and / or back
it up first, then recreate the table via OMW, then import that data back into the newly created table.
• Please note that these UBEs need to be submitted locally.

• Did you find this document helpful? If so, please provide your feedback and comments on this document in
MOS. Your feedback helps us help you.
• To discuss this information further with Oracle experts and industry peers, we encourage you to review, join
or start a discussion in the Install, Upgrades & Change Mgmt - JDE1 Community.
• To look at upcoming or archived Advisor Webcasts, please see Advisor Webcast Details Document
1450327.1. If your topic is not currently scheduled, please suggest it.

Didn't find what you are looking for?

2 de 2 15/01/2024, 03:55 p. m.