never-ending LOADs

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • J.Kubica

    never-ending LOADs

    Hello,

    We use DB2 8.2.4
    I have noticed that on one of our sun solaris machines LOAD command don't
    work. EXPORT and IMPORT commands works, but if I execute any LOAD - it never ends.
    The same LOAD statements takes on another machines less then second.
    On those server we have 3 instances and on every database it looks the same -
    it never stops.
    After I start LOAD command - in db2diag I've found only

    2008-07-08-08.54.04.243706 +120 I1252210C427 LEVEL: Warning
    PID : 26258 TID : 1 PROC : db2lrid 0
    INSTANCE: aut NODE : 000 DB : UNIT2
    APPHDL : 0-115 APPID: C0A8010A.J80A.0 2AD08075549
    FUNCTION: DB2 UDB, database utilities, DIAG_NOTE, probe:0
    DATA #1 : String, 81 bytes
    LOADID: 24182.2008-07-08-08.54.03.904228 .0 (10;110)
    Load CPU parallelism is: 7, 0

    2008-07-08-08.54.04.276194 +120 I1252638C491 LEVEL: Warning
    PID : 26250 TID : 1 PROC : db2lfrm0 0
    INSTANCE: aut NODE : 000 DB : UNIT2
    APPHDL : 0-115 APPID: C0A8010A.J80A.0 2AD08075549
    FUNCTION: DB2 UDB, database utilities, sqlulPrintPhase Msg, probe:0
    DATA #1 : String, 135 bytes
    LOADID: 24182.2008-07-08-08.54.03.904228 .0 (10;110)
    Starting LOAD phase at 07/08/2008 08:54:04.259599 . Table MYSCHEMA .MYTESTTABLE

    Did someone have similar problem?
    How to try find a reason?

    Thank you
    J.Kubica

  • Tomas

    #2
    Re: never-ending LOADs

    On Jul 8, 12:23 am, "J.Kubica" <j...@k.comwrot e:
    Hello,
    >
            We use DB2 8.2.4
    I have noticed that on one of our sun solaris machines LOAD command don't
    work. EXPORT and IMPORT commands works, but if I execute any LOAD - it never ends.
    The same LOAD statements takes on another machines less then second.
    On those server we have 3 instances and on every database it looks the same -
    it never stops.
    After I start LOAD command - in db2diag I've found only
    >
    2008-07-08-08.54.04.243706 +120 I1252210C427       LEVEL: Warning
    PID     : 26258                TID  : 1          PROC : db2lrid 0
    INSTANCE: aut                  NODE : 000         DB   : UNIT2
    APPHDL  : 0-115                APPID: C0A8010A.J80A.0 2AD08075549
    FUNCTION: DB2 UDB, database utilities, DIAG_NOTE, probe:0
    DATA #1 : String, 81 bytes
    LOADID: 24182.2008-07-08-08.54.03.904228 .0 (10;110)
    Load CPU parallelism is: 7, 0
    >
    2008-07-08-08.54.04.276194 +120 I1252638C491       LEVEL: Warning
    PID     : 26250                TID  : 1          PROC : db2lfrm0 0
    INSTANCE: aut                  NODE : 000         DB   : UNIT2
    APPHDL  : 0-115                APPID: C0A8010A.J80A.0 2AD08075549
    FUNCTION: DB2 UDB, database utilities, sqlulPrintPhase Msg, probe:0
    DATA #1 : String, 135 bytes
    LOADID: 24182.2008-07-08-08.54.03.904228 .0 (10;110)
    Starting LOAD phase at 07/08/2008 08:54:04.259599 . Table MYSCHEMA    ..MYTESTTABLE
    >
    Did someone have similar problem?
    How to try find a reason?
    >
    Thank you
            J.Kubica
    Hello,

    you're not saying which version of Solaris you're running. If you're
    on Solaris 10, and you're trying to load into a tablespace with
    multiple containers, you're most likely hitting this Solaris bug:



    Its impact on DB2 LOAD is described here:



    There is a Solaris patch available to take care of this problem, or
    you can specify DISK_PARALLELIS M 1 on your load command.

    /T

    Comment

    • J.Kubica

      #3
      Re: never-ending LOADs

      Tomas wrote:
      On Jul 8, 12:23 am, "J.Kubica" <j...@k.comwrot e:
      >Hello,
      >>
      > We use DB2 8.2.4
      >I have noticed that on one of our sun solaris machines LOAD command don't
      >work. EXPORT and IMPORT commands works, but if I execute any LOAD - it never ends.
      >The same LOAD statements takes on another machines less then second.
      >On those server we have 3 instances and on every database it looks the same -
      >it never stops.
      >After I start LOAD command - in db2diag I've found only
      >>
      >2008-07-08-08.54.04.243706 +120 I1252210C427 LEVEL: Warning
      >PID : 26258 TID : 1 PROC : db2lrid 0
      >INSTANCE: aut NODE : 000 DB : UNIT2
      >APPHDL : 0-115 APPID: C0A8010A.J80A.0 2AD08075549
      >FUNCTION: DB2 UDB, database utilities, DIAG_NOTE, probe:0
      >DATA #1 : String, 81 bytes
      >LOADID: 24182.2008-07-08-08.54.03.904228 .0 (10;110)
      >Load CPU parallelism is: 7, 0
      >>
      >2008-07-08-08.54.04.276194 +120 I1252638C491 LEVEL: Warning
      >PID : 26250 TID : 1 PROC : db2lfrm0 0
      >INSTANCE: aut NODE : 000 DB : UNIT2
      >APPHDL : 0-115 APPID: C0A8010A.J80A.0 2AD08075549
      >FUNCTION: DB2 UDB, database utilities, sqlulPrintPhase Msg, probe:0
      >DATA #1 : String, 135 bytes
      >LOADID: 24182.2008-07-08-08.54.03.904228 .0 (10;110)
      >Starting LOAD phase at 07/08/2008 08:54:04.259599 . Table MYSCHEMA .MYTESTTABLE
      >>
      >Did someone have similar problem?
      >How to try find a reason?
      >>
      >Thank you
      > J.Kubica
      >
      Hello,
      >
      you're not saying which version of Solaris you're running. If you're
      on Solaris 10, and you're trying to load into a tablespace with
      multiple containers, you're most likely hitting this Solaris bug:
      >

      >
      Its impact on DB2 LOAD is described here:
      >

      >
      There is a Solaris patch available to take care of this problem, or
      you can specify DISK_PARALLELIS M 1 on your load command.
      >
      /T
      LOAD with DISK_PARALLELIS M 1 works. It means it is probably solaris bug you
      mentioned. Thank you.

      J.Kubica

      Comment

      Working...