Clarity

  • 1.  BO Report performance poor compared to old actuate reports

    Posted Feb 12, 2013 01:51 PM
    We are in the process of moving from Actuate 9 to Business Objects
    We are running Clarity 12.1 on Websphere(Linux) with Oracle DB
    Our production environment is still running Actuate.
    Our QA environment is running BO CABI v3.
    Our Prod and QA environments are exactly the same expect for the BO server vs the Actuate server
    The BO server should be plenty robust we tried to scale for 100 users running reports all at the same time.

    W have 5 custom reports written for us by CA.
    The reports on our Prod environment with Actuate run in seconds
    The converted reports in QA take several minutes.
    Oracle optimizer gives no hints to the SQL in the newer BO reports.

    But just running 1 report takes over 4 mins where Actuate version takes 10 seconds.

    Has anyone experience a large shift in performance time when they went to Business Objects?

    The report seems like it is spending it's time in the database but the database doesn't seem overloaded. Cpu usage stays low memory usage stays low.

    I would love to hear about anyones experience.


    aditional item.
    The install process for BO/CABI give inconsistant results. We are unable to get through the entire installation process without an error. But usually not the same error. Any similar experience?


  • 2.  RE: BO Report performance poor compared to old actuate reports

    Posted Feb 12, 2013 02:12 PM
    One explanation I've seen in the posts is using timeslices. With BO it seems to take much longer than just bare SQL.

    Martti K.


  • 3.  RE: BO Report performance poor compared to old actuate reports

    Posted Feb 14, 2013 06:39 AM

    tnestor wrote:

    We are in the process of moving from Actuate 9 to Business Objects
    We are running Clarity 12.1 on Websphere(Linux) with Oracle DB

    I would love to hear about anyones experience.
    We have developed number of BO WEBI Report for 12.1 , Tomcat with Oracle Database.

    Personally i feel WEBI Reports are bit slow than Actuate but time difference is like few secs. 4 mins to run one report is too long if it runs in 10 sec in Actuate.

    But we have created new Universes according to our requirements. If you have access to Infoview then find the queries from reports and run on SQL Developer to find out whether the Queries are taking long time or not.


    aditional item.
    The install process for BO/CABI give inconsistant results. We are unable to get through the entire installation process without an error. But usually not the same error. Any similar experience?
    I have installed BO/ CABI number of times but without any error.


    -Gurjeet


  • 4.  RE: BO Report performance poor compared to old actuate reports

    Posted May 22, 2013 03:12 PM
    Does Infoview come packaged with BO?
    Is that something I can see through the CMC?

    -Tom


  • 5.  RE: BO Report performance poor compared to old actuate reports

    Posted Feb 26, 2013 09:47 AM
    Hi,

    In Crystal Report using Oracle DB - Are you calling an SP.If so it will be executed twice.That will also cause performance pbm.
    You need to address it.

    Have an look at the below post.

    18407830

    Note:- Every thing should be carefully tested before implementing in pdn.

    BO Reporting Parameters Tuning:-


    We increased the number of connections without affecting performance by adding one more Web Intelligence Processing. We have 8 CPU server
    so we opted for 2 Web Intelligence processing servers which can handle total of 300 connections.


    Increased the No of service engines.These settings will help to handle multitasking.


    Some Clarity KB Articles:-

    Title: How to Increase Concurrent Job Limit in Cabi 3.2
    Description:
    Please follow the steps below to increase the limit of jobs that can run concurrently in Cabi 3.2. These changes will not take affect until the BO services are restarted or the machine rebooted.
    Please set these values with caution as it may adversely affect the performance of the reporting server. Ensure that you have enough physical resources on the server before changing the values from the default.
    Solution:
    1.
    Launch 'Business Objects Central Management Console'
    2.
    Login as the 'Administrator' of BO.
    3.
    In the CMC home select 'Servers'
    4.
    Right Click on 'Crystal ReportsJobServer' it will be prefaced by the actual server name that BO is installed on.
    5.
    Select 'Properties' and scroll down to the bottom.
    6.
    In the filed titled 'Maximum Concurrent Jobs' change this value from the default of 5 and enter the value you wish.
    7.
    Click 'Save'
    8.
    Repeat steps 5-7 for the ''AdaptiveJobServer' it will be prefaced by the actual server name that BO is installed on.


    Clarity: Viewed Business Objects report times-out to Login Prompt
    Description:
    Viewing a report from Clarity is timing out and then displays a login prompt.
    Solution:
    The web server used by Business Objects (BO) is timing out. The following solution will extend the timeout for tomcat web server used for BO by default.
    1.
    Navigate to the following location on your Business Objects Server:

    <BO Install Dir>\Business Objects\Tomcat55\webapps\InfoViewApp\WEB-INF
    2.
    Edit the web.xml in notepad
    3.
    Search for the below lines:

    <session-config>
    <session-timeout>20</session-timeout> <!-- 20 minutes for session objects -->
    </session-config>
    4.
    Increase the Session-Timeout parameter from 20 to 120 minutes in web.xml
    5.
    Repeat the same for the web.xml file in the InfoViewAppActions folder in:

    <BO Install Dir>\Business Objects\Tomcat55\webapps\InfoViewAppActions\WEB-INF
    6.
    Save the files
    7.
    Increase WebIntelligenceProcessingServer Idle Connection Timeout to 120 minutes
    8.
    Restart tomcat instance serving BO
    9.
    Restart BO



    cheers,
    sundar


  • 6.  RE: BO Report performance poor compared to old actuate reports

    Posted Mar 13, 2013 01:42 PM
    Thanks for the info!


  • 7.  RE: BO Report performance poor compared to old actuate reports

    Posted Mar 06, 2013 02:20 PM
    Additionally to what Sundar already documented. It sounds like you are planning to heavily use Crystal Reports. As such, you should think about distributing the BOBJ infrastructure to have one server processing only Crystal Report requests.

    Also, I've noticed that the processing time in Crystal normally has to do with the number of pages that are being rendered on the report therefore, tweaking the parameters of the report to enforce a more limited result set, is also a good idea.


  • 8.  RE: BO Report performance poor compared to old actuate reports
    Best Answer

    Posted Apr 09, 2013 01:47 PM
    One of the things that was discovered was that there is a known bug with Oracle 11g with the ALL_SYNONYMS view.
    3 of our reports where hitting that view.
    Oracle had a fix by recreating the view.
    The 3 reports that hit that view work great now.
    Oracle document ID 1242844.1