Partition By Function creating problem in Disco 10g

Question

We have used "Partition By" analytical function in some of our reports. We were running it in Disco 4i without any problem. But when we tried to run those reports in disco 10g, all the calculation columns where "Partition By" function is used, showing empty. When I remove "partition by" clause it retrieves the data. Anybody knows why it is happening?
Update: When I tried to add following existing calculation in the report gives me a error "column ambiguously defined"
ROW_NUMBER() OVER(PARTITION BY Invoice Number,Invoice Line Number ORDER BY Invoice Line Number )
Thanks
Message was edited by:
DiscoverDiscoverer

Answer 1

Hi
You don't type the double quotes but if Discoverer puts them in leave them there.
My gut feeling is that the problem is caused by the names of the items in the folder, or at least inside the report. As you know, whenever Discoverer begins parsing a name it stops whenever the name can be satisfied or tied to an object. Look again at your code:
ROW_NUMBER() OVER(PARTITION BY Invoice Number,Invoice Line Number ORDER BY Invoice Line Number )
You have an item called Invoice Number right? You also have an item called Invoice Line Number. As Discoverer is parsing these do you happen to have another item in your system called Invoice? If so, Discoverer will think you are asking it to PARTITION BY that item. Does this make sense?
Let's try an experiment.
Create 2 calculations, one called INV_NUM and one called INV_LINE, pointing INV_NUM directly at INVOICE NUMBER and INV_LINE at INVOICE_LINE_NUMBER.
Having got these 2 calculations in use, remove the original items from the report
Now try adding this code:
ROW_NUMBER() OVER(PARTITION BY INV_NUM,INV_LINE ORDER BY INV_LINE)
Did this help at all?
May I finally give you a workd of warning and that is to take care when naming items in folders. While Discoverer will let you do it, try to avoid using Oracle reserved words in item names. The name Number is a reserved word.
Having these as item names can lead to terrible problems when using analytic functions. Imagine if you will that you have a column called INVOICE and another called INVOICE DESC, short for DESCRIPTION and you use this:
ROW_NUMBER() OVER(PARTITION BY INVOICE AMOUNT ORDER BY INVOICE DESC )
Discoverer will think you want the INVOICE sorted in descending order which is not what you want at all. In this case you won't get an error. You'll just get the wrong answer.
Michael