Resolve Indexing Discrepancies - "Discrepancy 1: [Index Name] is not defined in metadata." / "Discrepancy 1: [Index Name]  is not defined in database."

Version 1

    Details

    After making metadata changes to an object, clicking Save brings the following message:



    Checking the Indexes, a discrepancy is shown: 



    What is the best course of action to take? 

     


    Resolution

    "Accept database indexes": 

    - Copies database schema indexes to the metadata if they are not in the metadata.
    - Removes metadata indexes from the metadata if they are not in the database schema.
    - Applies changes from the database schema indexes to the metadata indexes.

    "Accept metadata indexes": 
    - Copies metadata indexes to the database schema if they are not in the database schema.
    - Removes database schema indexes from the database schema if they are not in the metadata.
    - Applies changes from the metadata indexes to the database schema indexes.

    "Resolve later":
    - Does not change the indexes, allowing you to defer the decision until the next time the object is saved. 

    When the message "Discrepancy 1: [Index Name] is not defined in metadata." is displayed, choose 
    "Accept database indexes" to keep the database indexes and update the metadata 
    OR
    "Accept metadata indexes" to drop the database indexes that are not defined in metadata. 
    When the message "Discrepancy 1: [Index Name]  is not defined in database." is displayed, choose 
    "Accept database indexes" to drop the metadata indexes that are not defined in the database
    OR
    "Accept metadata indexes" to keep the metadata indexes and update the database.
     
    Online help reference: