apparently optimizer stats for these indexes were updated after you ran SQL tuning advisor -- a background job could have done it.
No that is not the case as initially i also though it to be the same but then i checked the stats first which were latest updated and then run the sql tunining advisor again the same result stale stats.
Can any body show some pointers over this issue as its making me to doubt on the sql tuning advisor...
Can you first try doing as the SQL Advisor has recommended? Then re-run the SQL Advisor and check what it suggests again.
You wouldn't be using the old analyze command to get the statistics?
I had tried to gather the stats and again immediately run the advison then also its shows the same collect stats for these objects. I there any advisor setting which need to altered.
I am using dbms_stats.gather_index_stats as recommende by advisor to gather the stats.