visual explain

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

    visual explain

    Since upgrading to db2 8.2.1 I've been having odd problems with visual
    explain:

    1. tables appear to require schema prefixes:
    [IBM][CLI Driver][DB2/AIX64] SQL0204N "BUCK.DIM_SENSO R"
    is an undefined name. SQLSTATE=42704

    I had already set the schema to dw - where queries can find
    dw.dim_sensor

    Now, this isn't a killer - I can always modify the sql before
    explaining it - but it seems like an unnecessary further PITA.


    2. DBA3065E Snapshot cannot be processed due to a CLI error.
    Explanation:
    A CLI error has occurred during snapshot processing. An
    access plan cannot be displayed.

    DBA3037E The explain snapshot has been corrupted. Your request
    cannot be completed.
    Explanation: The explain snapshot that is requested has been
    corrupted in the explain tables.

    Ok, no idea how to handle this one. So, I guess I just won't be
    using this tool to get an explain on this query. And if this
    happens more than every now & then - I've got ZERO chance on
    getting the developers to use it.

    You know, there are quite a few different new bells & whistles being
    added to db2 these days. Some of them are really terrific. But why
    can't we make sure the basic components are nearly bulletproof before
    adding new gewgaws?

    And no, I'm really not interested in calling support unless absolutely
    necessary - I expect this kind of thing to work perfectly out of the
    box, and don't appreciate having to waste my time on the phone to
    fiddle with the product to get it to work. At a certain point support
    lines become crutches to allow vendors to release an inferior product,
    and get it fixed in the field.

    So, is there a simple fix? Do I have to ugrade to v8.2.2?

    buck

    Tags: None
    • Mark A
      #2
      Re: visual explain

      "Buck Nuggets" <bucknuggets@ya hoo.com> wrote in message
      news:1126390052 .791070.276370@ g14g2000cwa.goo glegroups.com.. .[color=blue]
      > Since upgrading to db2 8.2.1 I've been having odd problems with visual
      > explain:
      >
      > 1. tables appear to require schema prefixes:
      > [IBM][CLI Driver][DB2/AIX64] SQL0204N "BUCK.DIM_SENSO R"
      > is an undefined name. SQLSTATE=42704
      >
      > I had already set the schema to dw - where queries can find
      > dw.dim_sensor
      >
      > Now, this isn't a killer - I can always modify the sql before
      > explaining it - but it seems like an unnecessary further PITA.
      >
      >
      > 2. DBA3065E Snapshot cannot be processed due to a CLI error.
      > Explanation:
      > A CLI error has occurred during snapshot processing. An
      > access plan cannot be displayed.
      >
      > DBA3037E The explain snapshot has been corrupted. Your request
      > cannot be completed.
      > Explanation: The explain snapshot that is requested has been
      > corrupted in the explain tables.
      >
      > Ok, no idea how to handle this one. So, I guess I just won't be
      > using this tool to get an explain on this query. And if this
      > happens more than every now & then - I've got ZERO chance on
      > getting the developers to use it.
      >
      > You know, there are quite a few different new bells & whistles being
      > added to db2 these days. Some of them are really terrific. But why
      > can't we make sure the basic components are nearly bulletproof before
      > adding new gewgaws?
      >
      > And no, I'm really not interested in calling support unless absolutely
      > necessary - I expect this kind of thing to work perfectly out of the
      > box, and don't appreciate having to waste my time on the phone to
      > fiddle with the product to get it to work. At a certain point support
      > lines become crutches to allow vendors to release an inferior product,
      > and get it fixed in the field.
      >
      > So, is there a simple fix? Do I have to ugrade to v8.2.2?
      >
      > buck
      >[/color]
      You should upgrade to FP10 before you do anything else. Also, make sure you
      upgrade your databases with db2updv8 (see Command Reference) after applying
      the FP and upgrading the instances. This procedure is not included in the
      earlier FP readme installation instructions (erroniously), but is for FP10.


        Comment

        • Buck Nuggets
          #3
          Re: visual explain

          Mark A wrote:[color=blue]
          > You should upgrade to FP10 before you do anything else. Also, make sure you
          > upgrade your databases with db2updv8 (see Command Reference) after applying
          > the FP and upgrading the instances. This procedure is not included in the
          > earlier FP readme installation instructions (erroniously), but is for FP10.[/color]

          Thanks Mark.

          I just reviewed the apars for this fp and see that FP10 will fix the
          visual explain problem with merges and comments. I hadn't gotten to
          the problem with unions yet. But it doesn't list the problem with
          requiring schema prefixes.

          Still, it looks like a lot of code was cleaned up, so maybe they've got
          both of these problems fixed.

          Buck

            Comment

            Previous template Next
            Working...