Results 1 to 7 of 7
  1. #1
    Join Date
    Feb 2005
    Posts
    1

    Unanswered: Error while running db2look

    I try to cron the data from DB2 8.2(AIX remote machine) to PC(windows 2000) with DB2 7.2 installed.

    When I ran the following command on PC, the error occurs.

    db2look -d node -i username -w password -a -e -x -o c:/tmp/db.out

    % Generate statistics for all creators
    % Creating DDL for table(s)
    % Output is sent to file: c:/dbdata/backup/penguinp.out
    The db2look utility could not generate table DDL rc = 131136
    The db2look utility is now terminating
    SQL0969N There is no message text corresponding to SQL error "-1198" in the
    message file on this workstation. The error was returned from module
    "SQLEDSSD" with original tokens "2".

    If I try to get data from AIX 7.2 to PC(windows 2000) with DB2 7.2 installed, it works.

    Anyone has any suggestion.

    Thanks.

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Quote Originally Posted by tsang
    I try to cron the data from DB2 8.2(AIX remote machine) to PC(windows 2000) with DB2 7.2 installed.
    Install client of the same version.

  3. #3
    Join Date
    Aug 2003
    Posts
    58
    I have 7.2 on my PC and it works fine to the same machines Tsang-bin is running to. His worked fine before he went on vacation. Some time in the
    last month or so, his PC stopped working. We have tried intalling multiple
    versions on his PC, but have not been able to duplicate how my PC works.
    What could have changed to cause this problem?

  4. #4
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    If you're interested in
    Quote Originally Posted by wayneb64
    What could have changed to cause this problem?
    then you're probably in a wrong forum. Try "alt.mysteries" or something like that.

    If you just need to solve the problem try installing a proper version of the client software.
    Code:
    >db2 ? sql1198
    
    
    SQL1198N This command is not supported in the current downlevel
              client-server configuration. Reason code =
              "<reason-code>".
    
    Explanation:
    
     The command you have entered is not supported in your current
    configuration involving either a pre-V8 client or server. The
    possible reason codes are as follows:
    
    
     1 Scrollable cursors are not supported from a pre-V8 client
    through a V8 or later gateway to a DB2 UDB server.
    
     2 Utility commands are not supported from a pre-V8 client
    through a V8 or later gateway to any DB2 server.
    
    ...
    
    User Response:
    
     The action is based on the reason code as follows:
    
    
     1 Do not use scrollable cursors from a downlevel client through
    a gateway.  Use a direct client-server connection or upgrade your
    client to a compatible release.
    
     2 Do not issue utility commands from a downlevel client through
    a gateway.  Use a direct client-server connection or upgrade your
    client to a compatible release.
    
    ...
    
     sqlcode :  -1198
    
     sqlstate :  42997

  5. #5
    Join Date
    Aug 2003
    Posts
    58
    well it turns out something has changed. Its NOT a level problem, I managed to dig into the system and find a bunch of error message in the db2dump
    complaining:

    RETCODE : ZRC=0x800D002B=-2146631637=SQLM_RC_EVFULL "monitor full of data"

    We have two 8.1 AIX installs and the other is working fine, in fact both where working fine until something filled up on one of them, so dont send
    us off to another forum.

    Here is the end of the db2dump:

    2005-02-02-17.07.36.292414-360 E382363505C976 LEVEL: Event
    PID : 307408 TID : 1 PROC : db2star2
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911
    MESSAGE : ADM7513W Database manager has started.
    START : DB2 DBM
    DATA #1 : Build Level, 124 bytes
    Instance "db2inst1" uses "32" bits and DB2 code release "SQL08020"
    with level identifier "03010106".
    Informational tokens are "DB2 v8.1.1.64", "s040812", "U498350", FixPak "7".
    DATA #2 : System Info, 184 bytes
    System: AIX penguin 2 5 00053D4C4C00
    CPU: total:8 online:2
    Physical Memory: total:12032 free:10767
    Virtual Memory: total:12544 free:11276
    Swap Memory: total:512 free:509
    Kernel Params: msgMaxMessageSize:4194304 msgMaxQueueSize:4194304
    shmMax:2147483648 shmMin:1 shmIDs:131072 shmSegments:16
    semIDs:131072 semNumPerID:65535 semOps:1024 semMaxVal:32767
    semAdjustOnExit:16384

    2005-02-02-17.08.18.636448-360 I382364482C369 LEVEL: Warning
    PID : 487674 TID : 1 PROC : db2agent (PENGLOCL) 0
    INSTANCE: db2inst1 NODE : 000 DB : PENGUIN
    APPHDL : 0-7 APPID: G9037916.O037.07DF42230817
    FUNCTION: DB2 UDB, base sys utilities, sqledint, probe:30
    MESSAGE : Crash Recovery is needed.

    2005-02-02-17.08.20.685466-360 I382364852C432 LEVEL: Warning
    PID : 487674 TID : 1 PROC : db2agent (PENGLOCL) 0
    INSTANCE: db2inst1 NODE : 000 DB : PENGUIN
    APPHDL : 0-7 APPID: G9037916.O037.07DF42230817
    FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:410
    MESSAGE : Crash recovery started. LowtranLSN 000004644CCD000C MinbuffLSN
    000004644CCD000C

    2005-02-02-17.08.20.787800-360 I382365285C411 LEVEL: Warning
    PID : 487674 TID : 1 PROC : db2agent (PENGLOCL) 0
    INSTANCE: db2inst1 NODE : 000 DB : PENGUIN
    APPHDL : 0-7 APPID: G9037916.O037.07DF42230817
    FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:2000
    MESSAGE : Using parallel recovery with 3 agents 4 QSets 12 queues and 6 chunks

    2005-02-02-17.08.21.481799-360 I382365697C442 LEVEL: Warning
    PID : 487674 TID : 1 PROC : db2agent (PENGLOCL) 0
    INSTANCE: db2inst1 NODE : 000 DB : PENGUIN
    APPHDL : 0-7 APPID: G9037916.O037.07DF42230817
    FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:4000
    MESSAGE : DIA2051W Forward phase of crash recovery has completed. Next LSN is
    "000004644CCD3CB8".

    2005-02-02-17.08.21.573656-360 I382366140C397 LEVEL: Warning
    PID : 487674 TID : 1 PROC : db2agent (PENGLOCL) 0
    INSTANCE: db2inst1 NODE : 000 DB : PENGUIN
    APPHDL : 0-7 APPID: G9037916.O037.07DF42230817
    FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:3170
    MESSAGE : Crash recovery completed. Next LSN is 000004644CCD3CB8

    2005-02-02-17.08.22.084973-360 I382366538C336 LEVEL: Warning
    PID : 307412 TID : 1 PROC : db2event (DB2DETAILDEADLOCK) 0
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, database monitor, sqm___sqlmeiot, probe:7
    MESSAGE : target type 0 failed to open DB2DETAILDEADLOCK with rc -2146631637

    2005-02-02-17.08.22.101193-360 I382366875C477 LEVEL: Severe
    PID : 487674 TID : 1 PROC : db2agent (PENGLOCL) 0
    INSTANCE: db2inst1 NODE : 000 DB : PENGUIN
    APPHDL : 0-7 APPID: G9037916.O037.07DF42230817
    FUNCTION: DB2 UDB, database monitor, sqm___start_evmon, probe:40
    RETCODE : ZRC=0x800D002B=-2146631637=SQLM_RC_EVFULL "monitor full of data"
    DIA8052C Event monitor has reached its file capacity.

    2005-02-02-17.08.22.120166-360 I382367353C461 LEVEL: Severe
    PID : 487674 TID : 1 PROC : db2agent (PENGLOCL) 0
    INSTANCE: db2inst1 NODE : 000 DB : PENGUIN
    APPHDL : 0-7 APPID: G9037916.O037.07DF42230817
    MESSAGE : event monitor name
    DATA #1 : Hexdump, 17 bytes
    0x2003A988 : 4442 3244 4554 4149 4C44 4541 444C 4F43 DB2DETAILDEADLOC
    0x2003A998 : 4B K

    2005-02-02-17.08.22.120440-360 I382367815C621 LEVEL: Severe
    PID : 487674 TID : 1 PROC : db2agent (PENGLOCL) 0
    INSTANCE: db2inst1 NODE : 000 DB : PENGUIN
    APPHDL : 0-7 APPID: G9037916.O037.07DF42230817
    MESSAGE : event monitor target
    DATA #1 : Hexdump, 61 bytes
    0x2003A9B0 : 2F64 6244 6174 612F 6462 3269 6E73 7431 /dbData/db2inst1
    0x2003A9C0 : 2F4E 4F44 4530 3030 302F 5351 4C30 3030 /NODE0000/SQL000
    0x2003A9D0 : 3031 2F64 6232 6576 656E 742F 6462 3264 01/db2event/db2d
    0x2003A9E0 : 6574 6169 6C64 6561 646C 6F63 6B etaildeadlock

    2005-02-02-17.08.29.025384-360 I382368437C336 LEVEL: Warning
    PID : 303314 TID : 1 PROC : db2event (DB2DETAILDEADLOCK) 0
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, database monitor, sqm___sqlmeiot, probe:7
    MESSAGE : target type 0 failed to open DB2DETAILDEADLOCK with rc -2146631637

    2005-02-02-17.08.29.026567-360 I382368774C477 LEVEL: Severe
    PID : 483578 TID : 1 PROC : db2agent (PENGLOCL) 0
    INSTANCE: db2inst1 NODE : 000 DB : PENGUIN
    APPHDL : 0-8 APPID: G9037916.O03A.07EF52230826
    FUNCTION: DB2 UDB, database monitor, sqm___start_evmon, probe:40
    RETCODE : ZRC=0x800D002B=-2146631637=SQLM_RC_EVFULL "monitor full of data"
    DIA8052C Event monitor has reached its file capacity.

    2005-02-02-17.08.29.027493-360 I382369252C461 LEVEL: Severe
    PID : 483578 TID : 1 PROC : db2agent (PENGLOCL) 0
    INSTANCE: db2inst1 NODE : 000 DB : PENGUIN
    APPHDL : 0-8 APPID: G9037916.O03A.07EF52230826
    MESSAGE : event monitor name
    DATA #1 : Hexdump, 17 bytes
    0x2003A988 : 4442 3244 4554 4149 4C44 4541 444C 4F43 DB2DETAILDEADLOC
    0x2003A998 : 4B K

    2005-02-02-17.08.29.027759-360 I382369714C621 LEVEL: Severe
    PID : 483578 TID : 1 PROC : db2agent (PENGLOCL) 0
    INSTANCE: db2inst1 NODE : 000 DB : PENGUIN
    APPHDL : 0-8 APPID: G9037916.O03A.07EF52230826
    MESSAGE : event monitor target
    DATA #1 : Hexdump, 61 bytes
    0x2003A9B0 : 2F64 6244 6174 612F 6462 3269 6E73 7431 /dbData/db2inst1
    0x2003A9C0 : 2F4E 4F44 4530 3030 302F 5351 4C30 3030 /NODE0000/SQL000
    0x2003A9D0 : 3031 2F64 6232 6576 656E 742F 6462 3264 01/db2event/db2d
    0x2003A9E0 : 6574 6169 6C64 6561 646C 6F63 6B etaildeadlock



    something clearly overflowed and blowed up, but no clue where to look
    on how to fix this.

  6. #6
    Join Date
    Nov 2003
    Location
    Netherlands
    Posts
    96
    Quote Originally Posted by wayneb64

    2005-02-02-17.08.29.025384-360 I382368437C336 LEVEL: Warning
    PID : 303314 TID : 1 PROC : db2event (DB2DETAILDEADLOCK) 0
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, database monitor, sqm___sqlmeiot, probe:7
    MESSAGE : target type 0 failed to open DB2DETAILDEADLOCK with rc -2146631637

    2005-02-02-17.08.29.026567-360 I382368774C477 LEVEL: Severe
    PID : 483578 TID : 1 PROC : db2agent (PENGLOCL) 0
    INSTANCE: db2inst1 NODE : 000 DB : PENGUIN
    APPHDL : 0-8 APPID: G9037916.O03A.07EF52230826
    FUNCTION: DB2 UDB, database monitor, sqm___start_evmon, probe:40
    RETCODE : ZRC=0x800D002B=-2146631637=SQLM_RC_EVFULL "monitor full of data"
    DIA8052C Event monitor has reached its file capacity.
    Could this be a 'filesystem full' problem?

  7. #7
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    I would be extremely surprised if the situation above had caused db2look to fail; however, you can try disabling the event monitor ("set event monitor DB2DETAILDEADLOC state 0") and cleaning its directory (the path to it is in the diagnostic record above).

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •