Error In SQL Statement

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • scorpion53061
    #1

    Error In SQL Statement

    My Visual Studio 2005 Query Window reports the following error when
    this query runs. Any idea what might be causing it? Thanks for any
    help. I have tried subsitituing for the parameter a fixed number and
    same error. I also have established it does connect and close properly
    with my connection string.

    [DB2/LINUX] SQL0952N Processing was cancelled due to an interrupt.
    SQLSTATE=57014


    SELECT F4211.SDITWT as grs_wgt, F5549110.BLDOCO as order_no,
    F5549110.BLSRTX as prod_code,
    F5549110.BLLOT1 as run_num, F5549110.BLLOTN as skid_num,
    F5549110.BLZ55B SWT as bs_wgt,
    F564108.IOZ55US R08 as id_barcode, F564108.IOZ55US R01 as width,
    F564108.IOZ55US R03 as length,
    F564108.IOZ55US R09 as desc1, F4211.SDVR01, F4211.SDVR02,
    F5549110.BLSQOR , F5549110.BLITM, F5549110.BLUOM
    FROM (PRODDTA.F55491 10 F5549110
    LEFT OUTER JOIN PRODDTA.F4211 F4211
    ON (F5549110.BLDOC O=F4211.SDDOCO)
    AND (F5549110.BLLNI D=F4211.SDLNID) )
    LEFT OUTER JOIN PRODDTA.F564108 F564108
    ON ((F5549110.BLMC U=F564108.IOMCU )
    AND (F5549110.BLITM =F564108.IOITM) )
    AND (F5549110.BLLOT N=F564108.IOLOT N)
    WHERE F5549110.BLDOCO =?

    Tags: sqlcode
    • Brian Tkatch
      #2
      Re: Error In SQL Statement

      On 5 Mar 2007 08:45:44 -0800, "scorpion53 061"
      <kellyjmartens@ gmail.comwrote:
      >My Visual Studio 2005 Query Window reports the following error when
      >this query runs. Any idea what might be causing it? Thanks for any
      >help. I have tried subsitituing for the parameter a fixed number and
      >same error. I also have established it does connect and close properly
      >with my connection string.
      >
      >[DB2/LINUX] SQL0952N Processing was cancelled due to an interrupt.
      >SQLSTATE=570 14
      >
      >
      >SELECT F4211.SDITWT as grs_wgt, F5549110.BLDOCO as order_no,
      >F5549110.BLSRT X as prod_code,
      >F5549110.BLLOT 1 as run_num, F5549110.BLLOTN as skid_num,
      >F5549110.BLZ55 BSWT as bs_wgt,
      >F564108.IOZ55U SR08 as id_barcode, F564108.IOZ55US R01 as width,
      >F564108.IOZ55U SR03 as length,
      >F564108.IOZ55U SR09 as desc1, F4211.SDVR01, F4211.SDVR02,
      >F5549110.BLSQO R, F5549110.BLITM, F5549110.BLUOM
      >FROM (PRODDTA.F55491 10 F5549110
      >LEFT OUTER JOIN PRODDTA.F4211 F4211
      >ON (F5549110.BLDOC O=F4211.SDDOCO)
      >AND (F5549110.BLLNI D=F4211.SDLNID) )
      >LEFT OUTER JOIN PRODDTA.F564108 F564108
      >ON ((F5549110.BLMC U=F564108.IOMCU )
      >AND (F5549110.BLITM =F564108.IOITM) )
      >AND (F5549110.BLLOT N=F564108.IOLOT N)
      >WHERE F5549110.BLDOCO =?

      =============== =============== =============== =========
      db2 =? sql952


      SQL0952N Processing was cancelled due to an interrupt.

      Explanation:

      The user may have pressed the interrupt key sequence.

      The statement processing is terminated. Some changes may have
      been applied to the database, but not committed, before
      termination occurred.

      Federated system users: this situation can also be detected by
      the data source.

      User Response:

      Continue the application.

      If installing the sample database, drop it and install the
      sample database again.

      sqlcode : -952

      sqlstate : 57014
      =============== =============== =============== =========

      I'd guess a timeout. An outer join on an outer join may take a few
      minutes. If you can, run the query in the CLP first to verify it is
      running. If it takes a while, you may need to adjust the timeout value
      of you DB connection object.

      B.

        Comment

        • scorpion53061
          #3
          Re: Error In SQL Statement

          On Mar 5, 11:00 am, Brian Tkatch <N/Awrote:
          On 5 Mar 2007 08:45:44 -0800, "scorpion53 061"
          >
          >
          >
          >
          >
          <kellyjmart...@ gmail.comwrote:
          My Visual Studio 2005 Query Window reports the following error when
          this query runs. Any idea what might be causing it? Thanks for any
          help. I have tried subsitituing for the parameter a fixed number and
          same error. I also have established it does connect and close properly
          with my connection string.
          >
          [DB2/LINUX] SQL0952N Processing was cancelled due to an interrupt.
          SQLSTATE=57014
          >
          SELECT F4211.SDITWT as grs_wgt, F5549110.BLDOCO as order_no,
          F5549110.BLSRTX as prod_code,
          F5549110.BLLOT1 as run_num, F5549110.BLLOTN as skid_num,
          F5549110.BLZ55B SWT as bs_wgt,
          F564108.IOZ55US R08 as id_barcode, F564108.IOZ55US R01 as width,
          F564108.IOZ55US R03 as length,
          F564108.IOZ55US R09 as desc1, F4211.SDVR01, F4211.SDVR02,
          F5549110.BLSQOR , F5549110.BLITM, F5549110.BLUOM
          FROM (PRODDTA.F55491 10 F5549110
          LEFT OUTER JOIN PRODDTA.F4211 F4211
          ON (F5549110.BLDOC O=F4211.SDDOCO)
          AND (F5549110.BLLNI D=F4211.SDLNID) )
          LEFT OUTER JOIN PRODDTA.F564108 F564108
          ON ((F5549110.BLMC U=F564108.IOMCU )
          AND (F5549110.BLITM =F564108.IOITM) )
          AND (F5549110.BLLOT N=F564108.IOLOT N)
          WHERE F5549110.BLDOCO =?
          >
          =============== =============== =============== =========
          db2 =? sql952
          >
          SQL0952N Processing was cancelled due to an interrupt.
          >
          Explanation:
          >
          The user may have pressed the interrupt key sequence.
          >
          The statement processing is terminated. Some changes may have
          been applied to the database, but not committed, before
          termination occurred.
          >
          Federated system users: this situation can also be detected by
          the data source.
          >
          User Response:
          >
          Continue the application.
          >
          If installing the sample database, drop it and install the
          sample database again.
          >
          sqlcode : -952
          >
          sqlstate : 57014
          =============== =============== =============== =========
          >
          I'd guess a timeout. An outer join on an outer join may take a few
          minutes. If you can, run the query in the CLP first to verify it is
          running. If it takes a while, you may need to adjust the timeout value
          of you DB connection object.
          >
          B.- Hide quoted text -
          >
          - Show quoted text -
          Thank you for yoru help. I ran it with ConnectionTimeo ut set to 0 in
          connections string and same error returned.

            Comment

            • Tonkuma
              #4
              Re: Error In SQL Statement

              Althou, this last part doesn't violate syntax.
              .......
              ON ((F5549110.BLMC U=F564108.IOMCU )
              AND (F5549110.BLITM =F564108.IOITM) )
              AND (F5549110.BLLOT N=F564108.IOLOT N)
              WHERE F5549110.BLDOCO =?

              It might be worth to try to rewrite as following.
              .......
              ON ((F5549110.BLMC U=F564108.IOMCU )
              AND (F5549110.BLITM =F564108.IOITM)
              AND (F5549110.BLLOT N=F564108.IOLOT N))
              WHERE F5549110.BLDOCO =?



                Comment

                • Brian Tkatch
                  #5
                  Re: Error In SQL Statement

                  On 5 Mar 2007 09:19:23 -0800, "scorpion53 061"
                  <kellyjmartens@ gmail.comwrote:
                  >On Mar 5, 11:00 am, Brian Tkatch <N/Awrote:
                  >On 5 Mar 2007 08:45:44 -0800, "scorpion53 061"
                  >>
                  >>
                  >>
                  >>
                  >>
                  ><kellyjmart... @gmail.comwrote :
                  >My Visual Studio 2005 Query Window reports the following error when
                  >this query runs. Any idea what might be causing it? Thanks for any
                  >help. I have tried subsitituing for the parameter a fixed number and
                  >same error. I also have established it does connect and close properly
                  >with my connection string.
                  >>
                  >[DB2/LINUX] SQL0952N Processing was cancelled due to an interrupt.
                  >SQLSTATE=570 14
                  >>
                  >SELECT F4211.SDITWT as grs_wgt, F5549110.BLDOCO as order_no,
                  >F5549110.BLSRT X as prod_code,
                  >F5549110.BLLOT 1 as run_num, F5549110.BLLOTN as skid_num,
                  >F5549110.BLZ55 BSWT as bs_wgt,
                  >F564108.IOZ55U SR08 as id_barcode, F564108.IOZ55US R01 as width,
                  >F564108.IOZ55U SR03 as length,
                  >F564108.IOZ55U SR09 as desc1, F4211.SDVR01, F4211.SDVR02,
                  >F5549110.BLSQO R, F5549110.BLITM, F5549110.BLUOM
                  >FROM (PRODDTA.F55491 10 F5549110
                  >LEFT OUTER JOIN PRODDTA.F4211 F4211
                  >ON (F5549110.BLDOC O=F4211.SDDOCO)
                  >AND (F5549110.BLLNI D=F4211.SDLNID) )
                  >LEFT OUTER JOIN PRODDTA.F564108 F564108
                  >ON ((F5549110.BLMC U=F564108.IOMCU )
                  >AND (F5549110.BLITM =F564108.IOITM) )
                  >AND (F5549110.BLLOT N=F564108.IOLOT N)
                  >WHERE F5549110.BLDOCO =?
                  >>
                  >============== =============== =============== ==========
                  >db2 =? sql952
                  >>
                  >SQL0952N Processing was cancelled due to an interrupt.
                  >>
                  >Explanation:
                  >>
                  >The user may have pressed the interrupt key sequence.
                  >>
                  > The statement processing is terminated. Some changes may have
                  >been applied to the database, but not committed, before
                  >termination occurred.
                  >>
                  > Federated system users: this situation can also be detected by
                  >the data source.
                  >>
                  >User Response:
                  >>
                  >Continue the application.
                  >>
                  > If installing the sample database, drop it and install the
                  >sample database again.
                  >>
                  > sqlcode : -952
                  >>
                  > sqlstate : 57014
                  >============== =============== =============== ==========
                  >>
                  >I'd guess a timeout. An outer join on an outer join may take a few
                  >minutes. If you can, run the query in the CLP first to verify it is
                  >running. If it takes a while, you may need to adjust the timeout value
                  >of you DB connection object.
                  >>
                  >B.- Hide quoted text -
                  >>
                  >- Show quoted text -
                  >
                  >Thank you for yoru help. I ran it with ConnectionTimeo ut set to 0 in
                  >connections string and same error returned.
                  Is it returned at a specific time?

                  Visual Studio has its own timeout value. It is a property of the
                  database object. Specifically, set that one.

                  B.

                    Comment

                    Previous template Next
                    Working...