pazikas.com

Blog

  • OBIEE Performance Tuning Part 1

    This is part one of my OBIEE Tuning guide. In this post we will look at some of the parameters that should be set at NQSConfig.ini in order to achieve maximum performance  First things first to run a valid test I ran the same report each time, after I had applied changes rebooted all database and OBIEE services to find time of completion I used the manage sessions section on the Analytics Console (Administration > Manage Sessions). With regards to what is a good and bad result if its not 10 seconds or more faster then I would say the change hasn’t had an effect on performance.

    Note that all SQL should be tuned and it is said that OBIEE should be able to return a report within 1-10 seconds. My instance is not at this stage but you can still see a clear performance increase.

    With my performance testing cache has been turned off as this will give invalid results, when performace tweaking caching should only be turned in the final stage.

    Below changes were made to the NQSConfig.ini

    
MAX_SESSION_LIMIT = 5000
MAX_REQUEST_PER_SESSION_LIMIT = 5000
SERVER_THREAD_RANGE = 40-260
DB_GATEWAY_THREAD_RANGE = 40-520
INIT_BLOCK_CACHE_ENTRIES = 5000 # default is 20

    The settings were saved, database and all BI services restarted.

    The Report I was running contained 4 dashboards they will be listed as 1-4 below.

    Original Report Timings                                                  Changes to NQSConfig.ini Timings
    1.                  2m10s                                                                                                    1m54s
    2.                  3m5s                                                                                                      2m46s
    3.                  5m16s                                                                                                    5m13s
    4.                  2m41s                                                                                                    2m34s

    As you can see from the above there have been slight improvments in the report but one dashboard still runs in pretty much the same time.

    My next post will be on changes made to instanceconfig.xml then finally the changes I made to the database.

  • OBIEE Presentation Service

    I’ve known about this issue for some time now if using an older version of OBIEE then you may have trouble starting all of the opmn services in one go be it from the front or back-end.

    From the back-end if you run opmnctl startall the presentation service fails to come Alive.

    The reason for this is it is timing out before it can be brought up be it because you may have a large .rpd file.

    This is a know issue with OBIEE and the only work around is to bring the Presentation service online by itself by running;

    
opmnctl startproc ias-component=coreapplication_obips1

    you can try and edit opmn.xml to increase the time-out but Oracle notes that little success has been achieved by doing this and the only true fix is to upgrade OBIEE

  • Socket communication error

    I have came across a socket communication error. This error is very general and can be caused by a number of issues.

    In my case it related to a port conflict on the OBIEE server.

    The first thing I would suggest to try would be stopping all OBIEE and MW services then using ps -ef | grep to kill any outstanding processes. Hopefully all goes well for you and upon restarting all services everything comes back up and all is well.

    If you are still faced with issues I would try changing the port range that OBIEE uses this can be done through MW Enterprise Manager.

    Head to BI > Core Application > Capacity Management > Scalability

    Unlock & Edit settings and shorten the port range OBIEE is using, Apply the change and restart OPMN services.

  • Out of Memory error

    So I have been getting an out of memory issue when running reports in Analytics.

    At first I was at a loss with the issue as the log files didn’t point to any significant issue that would be the root cause.

    I started by doubling the Max Heap Size to hopefully resolve the issue but with no luck there I was stuck.

    A little research lead me to check the BIData\tmp location both BIServer and BIPresentation folders there were a number of tmp files that were very large in size.

    I have removed these tmp files and now hopefully the issue is resolved

    More to come…