Does Bi Beans allow dynamic aggragation capability?
Below is the use case and I would like to find out how I can implement this using Bi Beans.

We have a concept of analyzing the data by a "Group". A group is a set of 3 different dimensions. Say 'A','B' an
d 'C'. There may be 30000 members in Dimension A, 100K in B and 20 in C but for
a group X will have only 5 members from A, 10 from B and 4 from C.

So when user search by Group - X, I would like to perform an aggregation only on 5 memebers
from A, 10 from B and 4 from C and the Bi Beans crosstab should display aggrega
tion for only this group, also when I drill down on A I will n
eed to show only 5 member records and not 30000 members of A.

Thanks for your suggestions in advance.
.

Can you please help with documentation or a tutorial how we can implement this solution?
We tried to use supress NA rows option but it is impacting our application performance.

 out of  found this valuable. Do you find this valuable?    

• Post reply

Hello,

Is Oracle Discoverer supported in Oracle 11g (Desktop and web)?

Thanks

2  out of 2 found this valuable. Do you find this valuable? Do you?    

• Post reply

Show Last Reply

Please submit your proposals for BIWA Summit, visit http://OracleBIWA.org under summit 2008 tab.
Email us at conference@oracleBIWA.org if you have any questions.
Thanks
Shyam

3  out of 5 found this valuable. Do you find this valuable? Do you?    

• Post reply

DISCOVERER QUICK TIPS (covers 4.1.48, but may cover other levels) :

1) After cloning a DB and APPS code tree, the Discoverer part will not always work. Ensure that the pref.txt file has the correct IP address of the "new" server that runs the Discoverer code, and after the Discoverer services are started, create an "unregisterall.sh" script (like the "registerall.sh" script, but runs all 3 "unreg*" scripts one after the other). Run this, followed by a "registerall.sh", then "applypreferences.sh", and check the errors.txt file for zero length (no errors present). Run checkdiscoverer.sh, also to check all is OK.

2) switch off Query Prediction (QPPEnable – make his zero in the pref.txt), as it can help performance.

3) There are often several levels of heavy hash-joins going on in the PLAN that the CBO sets up for Discoverer report runs.
If not catered for, these overflow into the TEMP TS, and get slowed down ten-fold by excessive disk I/O in there. I would recommend if your DB server has , say 32GB memory, set your pga_aggregate_target to a quarter of this, to 8GB, but also override the AUTO settings, by adding hash_area_size = 200M or even 400M, and the sort_area_size to 100M, or 200M in the init<DB>.ora if still getting disk sorts.

4) Check for orphaned ws processes on the Discoverer server (or on your main DB server if running all under on code-tree),
and kill them regularly. These can occur after a “Memory Heap” error in the user stack. I have user session logging on, so I can detect this with a cron check of the user logs, then locate the process list, and kill them. This stops CPU hogging. I can provide the scripts I use for this if you need them.

5) When stopping Discoverer services each night (If you are not 24x7) for cleanup, ensue that all the following files are removed from /tmp, as they are sometimes missed: /tmp/orb*, /tmp/dc*, /tmp/opm*

2  out of 4 found this valuable. Do you find this valuable? Do you?    

• Post reply

Show Last Reply

Join the BI SIG for a web presentation and discussion on the importance of data modelling. http://bidwsig.org/node/8

Tuesday, March 11. Meeting details will be published no later than 5 March.

4  out of 6 found this valuable. Do you find this valuable? Do you?    

• Post reply