In analysing explains - I noticed that the optimizer ( I am on 13.1x) is actually using table alias names that are referred to in view and we have to delve into each view definition to find out what those aliases mean. Is there a Diganostic statement that will prevent them using these aliases and instead just refer to the qualified table as DB.Table.
e.g. in replace view it will
we do all AMP scan from Aliasname in view xyz. Its a bit irate to go find out what that alias is in the views and def. not a comfortable task if your view # is > 30 or so in the first layer