SQL time out error during ETL jobs

We have SCSM 2010 installed on seperate servers
Server1 : Service manager server and SQL database with two instance (ServiceManager and Datawarehouse)
Server2: Data warehouse server 
But during run of ETL jobs we found the error in data warehouse server as
Please suggest some solution for this.

Looks like there is communications problem between the servers. Are all services started and they can communicate between each other?
Cheers,
Thomas Strömberg
System Center Specialist
Blog:  
Twitter:   LinkedIn:
Please remember to 'Propose as answer' if you find a reply helpful

Similar Messages

  • Encore CS3 time out error during launch

    I installed CS3 Master Collection. All programs opens fine except Encore. When I launch it, loads all files and gives me timeout error at:
    stay at Blue ray and stop at flash. At this point the program stops and does not load any more.
    Anybody found the solution for this?
    Thanks,

    Since install support is free, have you called Adobe?

  • Facing TIME OUT error during data load extraction

    The program "SAPLSENA" has exceeded the maximum permitted runtime without
    interruption and has therefore been terminated.
    Can someone help me with the solution please?

    Hi Sai,
    IT looks like you are running the program in foreground and execution takes more time than the value specified under profile parameter rdisp/max_wprun_time.
    Check whether you can execute the same in background.
    If not then increase the value of parameter rdisp/max_wprun_time . Take SAP restart and test again.
    Hope this helps.
    Regards,
    Deepak Kori

  • Workflow install time-out error

    hi,
    i get a time-out error during wf configuration assistant. i believe that is has something to do with a database/workflow language conflict. the ca aborts just after setting and resetting env var 4(?) nls_lang/wf_nls_lang. any thoughts?
    thanks,
    kp

    Your question is overly terse. As this ain't Twitter, maybe you can use a few more characters to describe what you are asking for?
    Timeouts can occur in a couple of situations:
    1) On connections. By default, most client APIs give up if the connection has not completed within 15 seconds. This value is usually adjustable.
    2) When running commands. Many client APIs has a default timeout of 30 seconds, meaning that if SQL Server has not returned any data in this time frame, they give up and tell SQL Server to stop executing. If you experience this, you need to determine whether
    the timeout is the problem or the fact that it takes 30 seconds is the problem. The timeout is adjustable on the Command object. The default is a hole in the head in my opinion.
    3) Lock timeouts. This is a timeout that occurs inside SQL Server (in opposition to the other two) when a process has been waiting for a lock long enough. The default here is -1 which means "wait forever". But you can use the command SET LOCK_TIMEOUT
    to set an explicit lock timeout.
    4) When talking to linked servers. These timeouts are really the same as the first two, but they occur inside SQL Server, as here SQL Server is the client with regards to the remote data source. The default for queries is 10 minutes, a little more generous
    than the default in the client API.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Foreground job - Standard report - Time out error

    Hi,
    I have a standard SAP report which is executed from portal and the report is failing in the foreground with a time out error. As there is time set for foreground process and probably the volume of the report is big which is not good enough to execute in the foreground time frame.
    The customer wants to run it only in the foreground and does not want to schedule in the background and the reason being he wants to do some customization on the columns when the report is displayed back on the portal screen.
    Now my question is there any other option to get the requirement and increasing the foreground time is ruled out by Basis team.
    I was thinking if I can use a wrapper report on the standard report and include SAPGUI_PROGRESS_INDICATOR to keep the connection between the dialog and the presentation server going without dis-connecting. Is this a better option and I am not sure if it will work ?
    Please let me know if any one else has resolved such issues earlier.
    Regards
    Praneeth Kumar
    Edited by: gansprasan on Sep 20, 2011 2:07 PM

    Hi,
          Though it is not advisable to change max run time... if need you you consult with your basis and you can change run time dynamically in your program and reset to original. I agree even CL_gui_timer class wont help.
    you can check below link.. handle it carefully..
    [http://help.sap.com/bp_bw370/documentation/How_To_Change_the_Maximum_Dialog_Runtime_of_a_Process_in_NW2004s.pdf]
    data: old_value(100).
    CONSTANTS: parameter LIKE tpfet-parname
    VALUE 'rdisp/max_wprun_time'.
    CALL 'C_SAPGPARAM' ID 'NAME' FIELD parameter
    ID 'VALUE' FIELD old_value. " old_value will have value set by basis.
    IF sy-subrc <> 0.
      RAISE not_found.
      ENDIF.
    use FM TH_CHANGE_PARAMETER to change value. Again reset the value with old value..
    Regards,
    Ravi.

  • Time out error on deploying to SAP-J2EE engine.

    I got a problem while deploying to SAP-J2EE engine using ant. It takes a lot of time and then throws a time out error.
    The problem is with the web.xml file pointing to a DTD in the internet, I have pasted some part of the web.xml below,
    <?xml version="1.0" encoding="UTF-8" ?>
    <!DOCTYPE web-app
      PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
      "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
    <web-app>
        <display-name>MyPay</display-name>
        <description>MyPay</description>
    Once I write down the DTD description in the web.xml itself, it works fine.
    I have pasted the error trace below,
    j2eedeploy:
         [echo] Deploying to Local environment...
         [echo] C:\Java\Projects/MyPay/dist/MyPay.ear
    BUILD FAILED
    C:\Java\Projects\MyPay\build.xml:445: java.lang.RuntimeException: ERROR: ID90507:  Error occured during getting EARDescriptor : Failed to load resource from the context classloader of the current thread! Loading from classloader was caused by: java.net.ConnectException: Connection timed out: connect
    Exception is :
    java.io.IOException: Failed to load resource from the context classloader of the current thread! Loading from classloader was caused by: java.net.ConnectException: Connection timed out: connect
         at com.sap.engine.lib.xml.parser.URLLoaderBase.resolveEntity(URLLoaderBase.java:148)
         at com.sap.engine.lib.xml.parser.XMLParser.scanDTD(XMLParser.java:1271)
         at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2795)
         at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
         at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
         at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
         at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
         at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
         at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
         at com.inqmy.lib.xml.StandardDOMParser.parse(StandardDOMParser.java:127)
         at com.inqmy.lib.xml.StandardDOMParser.parse(StandardDOMParser.java:120)
         at com.inqmy.services.servlets_jsp.descriptor.jar.WebWar.getWebDescriptor(WebWar.java:98)
         at com.inqmy.deploy.tool.deployer.ExtendedEarReader.loadDescriptorFromFile(ExtendedEarReader.java:175)
         at com.inqmy.deploy.tool.deployer.ExtendedEarReader.getFullEarDescriptor(ExtendedEarReader.java:104)
         at com.inqmy.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:355)
         at com.inqmy.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:325)
         at com.pg.sap.deploy620.SAPDeploy620Manager.process(SAPDeploy620Manager.java:84)
         at com.pg.ant.tasks.j2ee620.J2ee620EngineDeployTask.execute(J2ee620EngineDeployTask.java:40)
         at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
         at org.apache.tools.ant.Task.perform(Task.java:364)
         at org.apache.tools.ant.Target.execute(Target.java:341)
         at org.apache.tools.ant.Target.performTasks(Target.java:369)
         at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
         at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
         at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
         at org.eclipse.ant.internal.ui.antsupport.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32)
         at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
         at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:423)
         at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:137)

    Thanks for your reply Kalyan,
    The problem seems to be with my system, because I had run the same ant script in another system and it deployed successfully.
    The problem does not seem to be with the dtd, whereas it seems that the SAP-J2EE engine is not able to open the link to the dtd giving a time out error.
    Is it possible to switch off the validation process of the SAP-J2EE engine of an xml with the dtd?

  • Time out error in report - Urgent

    Hi Gurus,
       Am developing the report for GL Account summary from tables bkpf, bseg. Due to lot of records in production server it is coming time out error. Please help me regarding this here am attaching my code.
    REPORT ZFBLREPORT.
    *TABLES : zgltax.
    TYPE-POOLS : SLIS.
    TYPES : BEGIN OF TY_ZGLTAX,
            ZGL TYPE BSEG-HKONT,
            ZTAX1 TYPE P DECIMALS 2,
            ZTAX2 TYPE P DECIMALS 2,
            CAMOUNT TYPE RF42B-SALDO,
            PAMOUNT TYPE RF42B-SALDO,
            TCAMOUNT TYPE RF42B-SALDO,
            TPAMOUNT TYPE RF42B-SALDO,
            END OF TY_ZGLTAX.
    TYPES : BEGIN OF TY_BKPF,
            BELNR TYPE BKPF-BELNR,
            BUDAT TYPE BKPF-BUDAT,
            END OF TY_BKPF.
    TYPES : BEGIN OF TY_BSEG,
            BELNR TYPE BSIS-BELNR,
            DMBTR TYPE BSIS-DMBTR,
            SHKZG TYPE BSIS-SHKZG,
            HKONT TYPE BSIS-HKONT,
            BUDAT TYPE BSIS-BUDAT,
            BUZEI TYPE BSIS-BUZEI,
            END OF TY_BSEG.
    DATA : IT_FINAL TYPE STANDARD TABLE OF TY_ZGLTAX,
           WA_FINAL TYPE TY_ZGLTAX.
    DATA : IT_BKPF TYPE STANDARD TABLE OF TY_BKPF,
           WA_BKPF TYPE TY_BKPF.
    DATA : IT_BSEG TYPE STANDARD TABLE OF TY_BSEG,
           WA_BSEG TYPE TY_BSEG.
    DATA: CAMOUNT TYPE RF42B-SALDO,
          PAMOUNT TYPE RF42B-SALDO.
    DATA : INDEX TYPE SY-INDEX.
    DATA : ID TYPE SY-TABIX.
    DATA : START_DATE TYPE SY-DATUM.
    DATA : END_DATE TYPE SY-DATUM.
    DATA : START_QUATER TYPE SY-DATUM.
    DATA : YEAR1(4) TYPE C.
    DATA       : T_FIELDALV     TYPE SLIS_T_FIELDCAT_ALV.
    DATA       : IMPORT_VARIANT LIKE DISVARIANT.
    DATA       : XREPID         LIKE SY-REPID.
    DATA       : LAYOUT         TYPE SLIS_LAYOUT_ALV.
    SELECTION-SCREEN BEGIN OF BLOCK BK1 WITH FRAME TITLE TEXT-001.
    PARAMETER : P_PERIOD(1) TYPE C OBLIGATORY,
                P_YEAR(4) TYPE C OBLIGATORY.
    SELECTION-SCREEN END OF BLOCK BK1.
    AT SELECTION-SCREEN ON P_PERIOD.
      IF P_PERIOD > '4' OR P_PERIOD < '1'.
        P_PERIOD = ''.
        MESSAGE 'Enter Correct Quater Period' TYPE 'E'.
      ENDIF.
    START-OF-SELECTION.
      PERFORM CALC_DATE.
      PERFORM BUILD_LOGIC.
      PERFORM INITIAL_ALV_FIELDCAT CHANGING T_FIELDALV[].
      PERFORM LAYOUT.
      CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
        EXPORTING
          I_CALLBACK_PROGRAM     = SY-REPID
          I_GRID_TITLE           = 'FBT Report'
         i_callback_top_of_page = 'FORM_TOP_PAGE'
         it_sort                = p_sort
          IS_LAYOUT              = LAYOUT
          IT_FIELDCAT            = T_FIELDALV[]
          I_SAVE                 = 'A'
        TABLES
          T_OUTTAB               = IT_FINAL.
    *&      Form  calc_date
          text
    -->  p1        text
    <--  p2        text
    FORM CALC_DATE .
      IF P_PERIOD = '1'.
        CONCATENATE P_YEAR '04' '01' INTO START_DATE.
        CONCATENATE P_YEAR '04' '01' INTO START_QUATER.
        CONCATENATE P_YEAR '06' '30' INTO END_DATE.
      ELSEIF P_PERIOD = '2'.
        CONCATENATE P_YEAR '04' '01' INTO START_DATE.
        CONCATENATE P_YEAR '07' '01' INTO START_QUATER.
        CONCATENATE P_YEAR '09' '30' INTO END_DATE.
      ELSEIF P_PERIOD = '3'.
        CONCATENATE P_YEAR '04' '01' INTO START_DATE.
        CONCATENATE P_YEAR '10' '01' INTO START_QUATER.
        CONCATENATE P_YEAR '12' '31' INTO END_DATE.
      ELSEIF P_PERIOD = '4'.
        CONCATENATE P_YEAR '04' '01' INTO START_DATE.
        YEAR1 = P_YEAR + 1.
        CONCATENATE YEAR1 '01' '01' INTO START_QUATER.
        CONCATENATE YEAR1 '03' '31' INTO END_DATE.
      ENDIF.
    ENDFORM.                    " calc_date
    *&      Form  build_logic
          text
    -->  p1        text
    <--  p2        text
    FORM BUILD_LOGIC .
      SELECT * FROM ZGLTAX INTO CORRESPONDING FIELDS OF TABLE IT_FINAL.
      IF IT_FINAL[] IS NOT INITIAL.
        LOOP AT IT_FINAL INTO WA_FINAL.
          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
            EXPORTING
              INPUT  = WA_FINAL-ZGL
            IMPORTING
              OUTPUT = WA_FINAL-ZGL.
          INDEX = SY-TABIX.
           SELECT belnr dmbtr shkzg hkont budat buzei
          SELECT *
          FROM BSIS
          INTO CORRESPONDING FIELDS OF TABLE IT_BSEG
          WHERE
          BUKRS = '3599' AND
             HKONT = WA_FINAL-ZGL
            AND GJAHR = P_YEAR.
    Uses primary index (4.7)
          SELECT *
          FROM BSAS
          APPENDING CORRESPONDING FIELDS OF TABLE IT_BSEG
          WHERE
          BUKRS = '3599' AND
            HKONT = WA_FINAL-ZGL
            AND GJAHR = P_YEAR.
          LOOP AT IT_BSEG INTO WA_BSEG .
            IF WA_BSEG-BUDAT >= START_DATE AND WA_BSEG-BUDAT <= END_DATE.
              IF WA_BSEG-SHKZG = 'S'.
                CAMOUNT = CAMOUNT - WA_BSEG-DMBTR.
              ELSEIF WA_BSEG-SHKZG = 'H'.
                CAMOUNT = CAMOUNT + WA_BSEG-DMBTR.
              ENDIF.
            ENDIF.
            IF WA_BSEG-BUDAT >= START_QUATER AND WA_BSEG-BUDAT <= END_DATE.
              IF WA_BSEG-SHKZG = 'S'.
                PAMOUNT = PAMOUNT - WA_BSEG-DMBTR.
              ELSEIF WA_BSEG-SHKZG = 'H'.
                PAMOUNT = PAMOUNT + WA_BSEG-DMBTR.
              ENDIF.
            ENDIF.
          ENDLOOP.
          WA_FINAL-CAMOUNT = CAMOUNT.
          WA_FINAL-PAMOUNT = PAMOUNT.
          WA_FINAL-TCAMOUNT = CAMOUNT * WA_FINAL-ZTAX1 * WA_FINAL-ZTAX2 / (
    100 * 100 ).
          WA_FINAL-TPAMOUNT = PAMOUNT * WA_FINAL-ZTAX1 * WA_FINAL-ZTAX2 / (
    100 * 100 ).
          MODIFY IT_FINAL FROM WA_FINAL INDEX INDEX.
          REFRESH IT_BSEG.
        ENDLOOP.
      ENDIF.
    ENDFORM.                    " build_logic
    *&      Form  layout
          text
    FORM LAYOUT .
      LAYOUT-NO_SUBTOTALS = ' '.
    ENDFORM.                    " LAYOUT
    *&      Form  initial_alv_fieldcat
          text
         -->FIELDCAT   text
    FORM INITIAL_ALV_FIELDCAT  CHANGING FIELDCAT TYPE SLIS_T_FIELDCAT_ALV.
      DATA  : LS_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
      DATA  : CNTR TYPE I VALUE 1.
      CLEAR LS_FIELDCAT.
      CNTR = CNTR + 1.
      LS_FIELDCAT-COL_POS = CNTR.
      LS_FIELDCAT-FIELDNAME = 'ZGL'.
      LS_FIELDCAT-SELTEXT_L = 'GL A/C NO'.
      LS_FIELDCAT-OUTPUTLEN = 15.
      APPEND LS_FIELDCAT TO FIELDCAT.
      CLEAR LS_FIELDCAT.
      CNTR = CNTR + 1.
      LS_FIELDCAT-COL_POS = CNTR.
      LS_FIELDCAT-FIELDNAME = 'ZTAX1'.
      LS_FIELDCAT-SELTEXT_L = 'BASE TAX  PERCENTAGE'.
      LS_FIELDCAT-OUTPUTLEN = 15.
      APPEND LS_FIELDCAT TO FIELDCAT.
      CLEAR LS_FIELDCAT.
      CNTR = CNTR + 1.
      LS_FIELDCAT-COL_POS = CNTR.
      LS_FIELDCAT-FIELDNAME = 'ZTAX2'.
      LS_FIELDCAT-SELTEXT_L = 'TAX PERCENTAGE'.
      LS_FIELDCAT-OUTPUTLEN = 15.
      APPEND LS_FIELDCAT TO FIELDCAT.
      CLEAR LS_FIELDCAT.
      CNTR = CNTR + 1.
      LS_FIELDCAT-COL_POS = CNTR.
      LS_FIELDCAT-FIELDNAME = 'CAMOUNT'.
      LS_FIELDCAT-SELTEXT_L = 'CUMULATIVE AMOUNT'.
      LS_FIELDCAT-OUTPUTLEN = 20.
      APPEND LS_FIELDCAT TO FIELDCAT.
      CLEAR LS_FIELDCAT.
      CNTR = CNTR + 1.
      LS_FIELDCAT-COL_POS = CNTR.
      LS_FIELDCAT-FIELDNAME = 'TCAMOUNT'.
      LS_FIELDCAT-SELTEXT_L = 'Cumulative Tax % Amount'.
      LS_FIELDCAT-OUTPUTLEN = 20.
      APPEND LS_FIELDCAT TO FIELDCAT.
      CLEAR LS_FIELDCAT.
      CNTR = CNTR + 1.
      LS_FIELDCAT-COL_POS = CNTR.
      LS_FIELDCAT-FIELDNAME = 'PAMOUNT'.
      LS_FIELDCAT-SELTEXT_L = 'AMOUNT FOR PERIOD'.
      LS_FIELDCAT-OUTPUTLEN = 20.
      APPEND LS_FIELDCAT TO FIELDCAT.
      CLEAR LS_FIELDCAT.
      CNTR = CNTR + 1.
      LS_FIELDCAT-COL_POS = CNTR.
      LS_FIELDCAT-FIELDNAME = 'TPAMOUNT'.
      LS_FIELDCAT-SELTEXT_L = 'Tax AMOUNT FOR PERIOD'.
      LS_FIELDCAT-OUTPUTLEN = 20.
      APPEND LS_FIELDCAT TO FIELDCAT.
    ENDFORM.                    "initial_alv_fieldcat
    Points will be awarded
    Regards
    Ravi

    Hi Ravi kanth,
    You are using select * statement which is very time consuming and low performance. Dont use select * instead use select field1 field2.... into table itab  where field1 = s_field.  Use corresponding field names in the select statement.
    Follow the below rules.
    1) Dont use nested select statements
    2) If possible use for all entries in addition
    3) In the where addition make sure you give all the primary key
    4) Use Index for the selection criteria.
    5) You can also use inner joins
    6) You can try to put the data from the first select statement into an Itab and then in order to select the data from the second table use for all entries in.
    7) Use the runtime analysis SE30 and SQL Trace (ST05) to identify the performance and also to identify where the load is heavy, so that you can change the code accordingly
    <b>reward if useful</b>.
    Regards,
    sunil kairam.

  • Time Out ERROR CC Risk Analysis RFC

    Hi Friends,
    I am getting time out error when I am testing the CC risk analysis RFC. One thiing I monitor here is that when I am changing the parameters to 'YES' in tcode '/virsa/zrtcnfg',this RFC time out is occuring,when I am changing it back to 'NO' it is working fine.
    I beleive there is some system perfomance issue or any bottleneck is happenning.
    Please check error details of the Rfc below
    Logon     Connection Error
    Error Details     Error when opening an RFC connection
    Error Details     ERROR: program GRCRTTOCC5X not registered
    Error Details     LOCATION: SAP-Gateway on host hostname / sapgw00
    Error Details     DETAIL: TP GRCRTTOCC5X not registered
    Error Details     COMPONENT: SAP-Gateway
    Error Details     COUNTER: 65055
    Error Details     MODULE: gwr3cpic.c
    Error Details     LINE: 1960
    Error Details     RETURN CODE: 679
    Error Details     SUBRC: 0
    Error Details     RELEASE: 700
    Error Details     TIME: Thu Mar 11 09:21:35 2010
    Error Details     VERSION: 2
    and also some time I am getting below error
    Logon     Connection Error
    Error Details     Error when opening an RFC connection
    Error Details     ERROR: timeout during allocate of registered program
    Error Details     LOCATION: SAP-Gateway on host hostname / sapgw00
    Error Details     DETAIL: TP GRCRTTOCC5X init/busy for more than 60 sec
    Error Details     COMPONENT: SAP-Gateway
    Error Details     COUNTER: 65068
    Error Details     MODULE: gwr3cpic.c
    Error Details     LINE: 1937
    Error Details     RETURN CODE: 677
    Error Details     SUBRC: 0
    Error Details     RELEASE: 700
    Error Details     TIME: Thu Mar 11 09:29:56 2010
    Error Details     VERSION: 2
    Any suggestion please..
    Thanks & Regards,
    Satyabrat
    Edited by: Satyabrat Mohanty on Mar 11, 2010 11:54 AM
    Edited by: Satyabrat Mohanty on Mar 11, 2010 12:00 PM

    Hi,
    for further information  the latest log is
    2010-04-28 07:01:47,706 [SAPEngine_Application_Thread[impl:3]_18] ERROR  User :   not found to get full name
    2010-04-28 07:02:21,066 [SAPEngine_Application_Thread[impl:3]_11] ERROR
    java.lang.Throwable: java.lang.NullPointerException
         at com.virsa.re.workflow.client.WorkflowRequestClient.getRoleProcessContextDtos(WorkflowRequestClient.java:284)
         at com.virsa.re.workflow.client.WorkflowRequestClient.execSubmitRoleApprovalWF(WorkflowRequestClient.java:83)
         at com.virsa.re.workflow.actions.WorkflowRequestAction.submitApprovalRequest(WorkflowRequestAction.java:95)
         at com.virsa.re.workflow.actions.WorkflowRequestAction.execute(WorkflowRequestAction.java:54)
         at com.virsa.framework.NavigationEngine.execute(NavigationEngine.java:273)
         at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:230)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
         at com.virsa.comp.history.filter.HistoryFilter.doFilter(HistoryFilter.java:43)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    FYI
    I have already checked all the webservices urls and password everything is fine.am I missing something.
    Regards,
    Satyabrat

  • Xmlviewservice.executeSQLQuery  TIME OUT ERROR

    Hello OBIEE Experts,
    I got stucked with the command line xmlviewservice.executeSQLQuery(...) method of OBIEE as operation time out. Actuall i am writing dot net source code to retrive the xml result by passing the query created in Oracle BI Answer page. This method runs fine when running a very simple query returning only two rows. However when i set to use a query that takes around 10 min running in OBIEE answer section, the above method fails. It returns an error Operation Time out. I have even try setting sawservice & xmlviewservice timeout but no use.
    Is there any way to handle sql execution time using OBIEE SAW web service functionality ? Please find below code that i have used.
    Imports saw = Obiee_Services.web_Reference
    Dim sawservice As New saw.SAWSessionService
    Dim sessionid = sawservice.logon("xxx", "xxx")
    sawservice.Timeout = 60000
    'Dim curUser As String = sawservice.getCurUser(sessionid)
    'Dim repref As New saw.ReportRef()
    Dim xmlviewservice As New saw.XmlViewService
    Dim xmlQueryExecutionOption As New saw.XMLQueryExecutionOptions
    xmlQueryExecutionOption.maxRowsPerPage = 10
    xmlQueryExecutionOption.refresh = True
    Dim repid As String = "Report1"
    Dim repParams As New saw.ReportParams
    Dim repHtmlOP As New saw.ReportHTMLOptions
    Dim QueryResult As New saw.QueryResults
    xmlviewservice.Timeout = 60000
    QueryResult = xmlviewservice.executeSQLQuery(qry, Obiee_Services.web_Reference.XMLQueryOutputFormat.SAWRowsetData, xmlQueryExecutionOption, sessionid)
    Dim rstring As String = QueryResult.rowset
    Dim i = WriteToFile("text.xml", rstring)
    Regards,
    Rajen Singh

    Thank you for the reply.
    I do agree that i have omitted logging out command line and WriteToFile() definition. The below executesqlquery command is a syncronous call. I do not think it will be a problem with the next two or three lines. Below mentioned command line will not be released by the compiler until and unless it is completed. MOreover i am sure that the two mentioned command line does not have to do much on the issue becouse the error message is associated with below line and also works fine on simple query.
    QueryResult = xmlviewservice.executeSQLQuery(qry, Obiee_Services.web_Reference.XMLQueryOutputFormat.SAWRowsetData, xmlQueryExecutionOption, sessionid)
    I have tested other work around to resolve the current error i.e "Operation Time Out" error atleast(applying other configuration setup and increasing timeout properties). Having resolved sucessfully the next issue is on the below line. Blank rowset is returned each time. I can get an ID on QueryResult.QueryId and QueryResult.Finished=false.
    Dim rstring As String = QueryResult.rowset
    Finally, in OBI Presentation Services, the query runs fine in a specific time.

  • RSTXSCRP - Time out error

    Hello ,
    I am using the RSTXSCRP program to download and upload script.
    I am able to download(EXPORT).
    But during upload(IMPORT) to another system its giving a TIME OUT error.
    Do we need tot create the script in the upload syatem before using the RSTXSCRP program for upload!

    Hi,
    Create the Script and try to upload it will work fine. Even I was in the same situation . So I have created the script in SE71 and I have uploaded it . It came all those codes and windows.

  • BPC Optimization Server Time Out error message

    We’re using BPC 7.5 MS and on patch level 111.02
    There’s two front-end servers and one back-end.
    When completing a full optimization with compression on an application we immediately get the optimization popup screen with no processing information only a “Server Time Out” error message.
    Optimization was taking a long to time run and sometimes timed out.  To try and resolve this issue we have just updated indexes and statistics and during our test in production we now receive the “Server Time Out” error message immediately. However, the records from tbl.Factwb and tbl.Fac2 did move to the tbl.Fact.
    Our development environment test ran fine.
    Any suggestions?
    Thanks.

    Hi Michael,
    please look in the logs maybe you will found more informations regarding the timeout and eventually share it.
    There are several notes about a timeout in 10 version,
    1394533 - 'Server Time Out' error when performing Modify Application, Full Process of a dimension, or Full Optimize this is related with NLB
    but it could be also related with the web.config 1628908 - How to fix Optimize with compress time-out failure
    or if you reach the max number of connection
    1635749 - Error Message: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool
    Regards
         Roberto

  • SoA Couldnt start- Time Out Error

    Hi,
    My oracle SOA version is 10.1.3.1. I have created a application ( say sampleApplication) in jdeveloper (webservice from wsdl). When deploying the application to the application server it takes a long time to complete (approx 30 mins) but it gets deployed without error. I got a perm gen error and I stopped the SOA. When started it again after incresing the perm gen size, the SOA couldnt start. Got the following error
    <ERROR> <collaxa> <ProcessJob::execute> Attempt (1/15) ... failed to connect ... retrying in 5 seconds ...
    <2009-09-11 17:55:13,130> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://myURl....
    Maximum attempt of 15 was reached and the SOA failed to restart.
    After playing around with the server.xml (trying to remove all application entries and adding it one by one) found that when i removed the sampleApplication's entry from server.xml and tried starting SOA , it worked and it Started fine.
    Can any one point what might be the problem in my case.?
    Thanks in advance..
    (P.S: The other application deployed are developed in the same way as that of sampleApplication. So couldnt see any thing wrong with the sampleApplication. Other application entries in server.xml do not create this problem.)
    Edited by: user8655700 on Sep 11, 2009 7:03 AM

    Hi James,
    Thank You for your suggestion. I have some doubts.
    1) You suggested to revert back to old parameter and restart jDEV. What is the parameter i need to revert? I have only changed the max,min and perm size in opmn.xml because I keep getting perm gen error quite often. Did you mean those parameters ?
    2)Restarting jDev will solve the issue of longer deployment time for applications. But when I restart the SOA itself, it fails to start.I get the Time out error. On removing the application which took longer time to deploy from server.xml, SOA starts without error. No other changes have been made. So the question is why is the application which is successfully deployed from jdeveloper like many other applications stopping the SOA to start.?
    3)Or is the load during SOA startup is high, which results in it failing to start? If so how can I overcome this issue.
    Thanks,
    Ananth
    Edited by: user8655700 on Sep 14, 2009 10:25 PM

  • Select count(*) cause time out error

    I invoke the following statement:
    select count(*) as total from table1
    where table1 is large(30000 rows), total size of the database is more than 20GB.
    The above statement will cause time out error. How to solve the problem?

    Hallo chcw,
    a timeout in a table with 30.000 records is very unusual (for a simple SELECT COUNT). From my point of view Dan is on the right way and you will have a typical blocking scenario.
    1. if you have LOBs they won't be part of a SELECT COUNT (either its a heap of a clustered index)
    2. Microosft SQL Server will ALWAYS use the smallest index for such a simple SELECT
    3. if it is a heap you will run into a blocking scenario if someone is updating records and transaction has not committed.
    4. Check the isolation level of the transactions - but I expect the standard which is "read committed".
    Just a demonstration of "SELECT COUNT" will work whether it is a clustered index or a heap. The next script will create a heap with a LOB and additional attributes:
    CREATE TABLE dbo.foo
    Id INT NOT NULL IDENTITY(1,1),
    n1 INT NOT NULL,
    n2 SMALLINT NULL,
    c1 CHAR(250) NOT NULL,
    c2 CHAR(250) NULL,
    c3 VARCHAR(MAX) NOT NULL DEFAULT (REPLICATE('A', 15000))
    GO
    Now we enter 30,000 records into the table
    SET NOCOUNT ON;
    DECLARE @i INT = 1;
    WHILE @i <= 30000
    BEGIN
    INSERT INTO dbo.foo (n1, c1) VALUES (@i, 'Just a filler');
    SET @i += 1;
    END
    GO
    Keep in mind that we have a HEAP and NO indexes! To check the IO i use the following command befor any of the following examples:
    SET STATISTICS IO ON;
    GO
    Let's start with a first try and you will check as a result the produced IO depending on the affected table partitions:
    -- USE SELECT in a HEAP
    SELECT COUNT(*) FROM dbo.foo;
    GO
    Output:
    Table 'foo'. Scan count 1, logical reads 2508, ..., lob logical reads 0,
    As you can see from the result the LOB-data won't be attached only the "in-row-data" are affected (which are stored in 2508 pages. The reason is a quite simple one: Microsoft SQL Server uses different allocation units for in-row-data and LOB
    SELECT p.object_id, p.index_id, p.rows, au.total_pages
    FROM sys.partitions AS P INNER JOIN sys.allocation_units AS AU
    ON(p.partition_id = au.container_id)
    WHERE object_id = OBJECT_ID('dbo.foo');
    Now I create a simple index on the column n1 which is an INT-datatype
    SELECT p.object_id, p.index_id, p.rows, au.total_pages
    FROM sys.partitions AS P INNER JOIN sys.allocation_units AS AU
    ON(p.partition_id = au.container_id)
    WHERE object_id = OBJECT_ID('dbo.foo');
    and run the SELECT COUNT again with the following IO-output:
    Table 'foo'. Scan count 1, logical reads 69, ...
    WOW - only 69 pages have to be read. The explanation is a quite simple one - now we have an index which is quite small. Microsoft SQL Server WILL use the smallest index of a table to scan the number of records. Let's try it again with n2 which is a smallint
    (2 bytes)
    CREATE NONCLUSTERED INDEX ix_foo_n2 ON dbo.foo (n2);
    GO
    The IO will be 62 (or less) because MORE index records a fitting to one data page!
    Conclusion is that either you have small record size or long record size - The query optimizer will always use the smallest index for the execution (that's maybe why Visahk has asked for the execution plan).
    I don't believe it is because of the "huge amount of data" but - as Dan has pointed out - it HAS TO BE a blocking scenario which can have multiple reasons. For demonstration of a blocking scenario open SSMS and start in the query windows with the following
    command(s):
    BEGIN TRANSACTION
    UPDATE dbo.foo
    SET c1 = 'This is my name'
    WHERE Id = 10000;
    -- What locks do we have now in the database
    SELECT resource_description,
    resource_associated_entity_id,
    request_mode,
    request_type
    FROM sys.dm_tran_locks AS DTL
    WHERE resource_database_id = DB_ID() AND
    resource_type != 'DATABASE';
    Your result should look like that (with differences in the entity_id and resource descriptions :)
    The above pic demonstrates the "locking chain". As you can see the slot 7 on PAGE 82400 has an exclusive lock. This means that NO OTHER request can currently obtain another lock to it!
    Now open a second query window and run a SELECT COUNT... - it will not finish!
    The reason is that the second requests has to wait for the release of the locked resources by the first transaction! Leave the statement and change back to the first transaction and finish the transaction by cancellation of the query. In the moment the locks
    have been released the second query will finish immediate.
    So - from my point of view - Dan has given the correct answer. Against wide spreaded statements a heap won't block the whole table exclusivly but - as in a cluster, too - only the row itself (see the 7 which is the slot where the record exists).
    MCM - SQL Server 2008
    MCSE - SQL Server 2012
    db Berater GmbH
    SQL Server Blog (german only)

  • HT4623 The "Software Update" feature is not available in my Ipod 2nd Generation unit while the upgrade option in iTunes keeps on hanging while downloading the upgrade iOS (time out error). So, please tell me how I can upgrade the iOS.

    The "Software Update" feature is not available in my Ipod 2nd Generation unit while the upgrade option in iTunes keeps on hanging while downloading the upgrade iOS (time out error). So, please tell me how I can upgrade the iOS.

    The Settings>General>Software Update comes with iOS 5. The 2G can only go to iOS 4.2.1
    Try disabling the computer's security software during the download and update.

  • Time Out error : Its urgent

    Hi ,
    The scenario is that I am running a Process chain in which there is a loading process . In that process if data loading takes more than 1 hour it gives time out error . in ST22  , but in Sm37 it is active. Moreover in scheduler , the time is set to 2 hrs.
    What is happening ? can any one please explain . what should I do to get rid of time out error ? can we set time in update rule as in scheduler ?
    Please help me ...

    Hi Rajib,
    In your case even if you set the time out time in scheduler it takes the default work process settings.  Which you can see in the Parameter rdisp/max_wprun_time
    at RZ10 transaction and select Instance profile.  Even if the job is in active in sm37 it doesn't progress further when there is a timeout recorded.  Try to get intouch with you BASIS guys and get the parameter settings to 2 hours.  which may require server reboot.
    Hope it helps.
    Regards,
    Srikanth.

Maybe you are looking for