I have the agent Change Tracking set to the second choice: Retrieving plan from V$SQL_PLAN (run EXPLAIN PLAN if plan does not exist).
I have an execution plan that is the same, but it is reported as being different.
It looks like chaning from the default collection method to the V$SQL_PLAN (run EXPLAIN PLAN if plan does not exist) method adds the OBJECT_TYPE to the explain plan details; whereas the default method does not.
(ie OBJECT_TYPE contains the values 'TABLE' and 'INDEX (UNIQUE) using V$SQL_PLAN method)
Is there a way to have both explain plan methods display the same information so the execution plan is not reported as being different?
To solve the problem please run the following on PA REPOSITORY instance using PA username/password:
update quest_cm_def_attributes
set filter_enabled=1, filter_def='NVL(LAST.%s, ''ANALYZED'')<>NVL(PREV.%s, ''ANALYZED'')'
where type_key=18 and alias='OPTIMIZER';
commit;
After the above, restart PA Launcher service on Middleware and Change Tracking issue should be fixed.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center