I like the way people having fun with upgrades and issues, because experience is what it matters at the end of the day. If you cant learn from your experience , at least learn from some one else's.
I came across a interesting thing because of my friend who just did a upgrade from 10.1.3.4 to 11.1.1.6 , other than the general issues like aggregation failures and formatting changes he came across an issue with some of the reports.
No Results even though its available in DB and the 10g version is getting things done just fine.
We have investigated and found its a BUG 14084943
Bug 14084943 - REQUEST FOR HELP : REPORTS SHOW NO RESULTS AFTER UPGRADE
However there is workaround provided by Oracle for temporarily fixing the issue. The cause of this BUG is due to a feature called "Grouping Sets" that has been bought in with 11g to increase performance.
To fix the issue modify the database features in Repository (RPD) physical layer to remove the feature GROUP_BY_GROUPING_SETS_SUPPORTED.
After disabling this feature, the SQL generated in 11g should be almost the same than the one from 10g. This is a temporary workaround and the bug has been logged to identify the root cause and provide a fix
I came across a interesting thing because of my friend who just did a upgrade from 10.1.3.4 to 11.1.1.6 , other than the general issues like aggregation failures and formatting changes he came across an issue with some of the reports.
No Results even though its available in DB and the 10g version is getting things done just fine.
We have investigated and found its a BUG 14084943
Bug 14084943 - REQUEST FOR HELP : REPORTS SHOW NO RESULTS AFTER UPGRADE
However there is workaround provided by Oracle for temporarily fixing the issue. The cause of this BUG is due to a feature called "Grouping Sets" that has been bought in with 11g to increase performance.
To fix the issue modify the database features in Repository (RPD) physical layer to remove the feature GROUP_BY_GROUPING_SETS_SUPPORTED.
After disabling this feature, the SQL generated in 11g should be almost the same than the one from 10g. This is a temporary workaround and the bug has been logged to identify the root cause and provide a fix
No comments:
Post a Comment