Modifying existing profiles

You must take certain actions to apply changes to profiles.

To modify existing profiles and apply the changes:

1. Insert, update, or delete from the profile tables to define the changes.
   Important: To avoid disabling existing profiles, always use existing PROFILEID values for any new DSN_PROFILE_ATTRIBUTES rows that require the same filtering criteria as existing DSN_PROFILE_TABLE rows. If multiple DSN_PROFILE_TABLE rows contain exactly matching filtering criteria, only the newest duplicate row is accepted when you start the profiles, and the others are rejected and disabled.
2. For changes to profiles for optimization parameters, production system modeling, or query acceleration thresholds, invalidate the statements in the statement cache to apply the access path changes.
   For information about completing this action, see Invalidating statements in the dynamic statement cache.
3. Load or reload the profile tables into memory by issuing a START PROFILE command. (For best results, do not issue a STOP PROFILE command when you add or modify existing profiles. Use the STOP PROFILE command only if you intend to disable all existing profiles.) For more information, see Starting and stopping profiles.
4. Check the status of all newly added profiles in the STATUS columns of the DSN_PROFILE_HISTORY and DSN_PROFILE ATTRIBUTES_HISTORY tables.
   Successful completion of the START PROFILE command does not imply that all profiles started successfully. If the STATUS column of either history table contains a value that does not start with 'ACCEPTED', further action is required to enable the profile or the keyword action.