Skip to Content
author's profile photo Former Member
Former Member

Appset offline while optimize occurs but not comeback online

Hi ,

An optimize occurs it takes appset offline but why it didn't come back online when it completed.When SSIS package that performs the part of optimzing applications.

In the morning time the first optimize in the SSIS pack would be running?If a user logs in during this process is it cause the problem or shall I look in different option.Please advice me .Thankyou.



Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Sep 24, 2010 at 09:12 PM

    Yaswanth - This is a bug that was fixed I believe in BPC 7.0 M SP 6 or SP 7. If you're using SQL Server 2008, I believe you can go into Services on your Server and find the Send Governor service and set it to restart on boot - which may or may not fully work.

    Instead, All you have to do is to add a custom task to your SSIS package that restarts the Send Governor service after the Optimize task is complete.


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 25, 2010 at 05:02 PM

    Hi Yashwant,

    If it is an SSIS package, do you have a SYSTEM AVAILABLE task at the end of the package to bring back the appset online?

    When an optimization (except Lite optimization) is running, the user will not be able to enter data. The users must wait till the package ends and brings the appset online.


    Edited by: Karthik AJ on Sep 27, 2010 1:15 PM

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Kaarthic Jayapaul

      This may not be relavant to you and others may not recommend this method.

      We had a similar problem whilst developing one of our appsets. Once of the development tasks is to schedule lite optimises and a full optimise at night - similiar to your situation.

      However there are scenarios that erroneous data is put into the FACT tables (i.e typically via bad script logic).

      In order to get the appset back online, we created an SSIS package that put the appset back online and scheduled this after the full optimise at night (just incase the appset was offline).

      Of course the major flaw is that you are masking possible database table errors - although this is less of a concern if you are proactive in checking logs.

      Hope this helps.


      Edited by: Hiren Amin on Oct 13, 2010 8:20 AM

      I just read some of the posts above and noted the service reset - Osoft Send Governer - this is not a bad idea.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.