Results 1 to 2 of 2
  1. #1
    Join Date
    Jul 2010
    Posts
    6

    Unanswered: SQL0901N error when accessing one table

    Hi,
    Recently i want to try to access one table in db2 9.7. It will come out the

    below error:

    com.ibm.db.DataException: A database manager error occurred.
    : [IBM][CLI Driver][DB2/NT64] SQL0901N The SQL statement failed
    because of a non-severe system error. Subsequent SQL statements can
    be processed. (Reason "Specified index not found for scan open".)
    SQLSTATE=58004



    And also refer to below error coming from db2diag.log when i access the table:

    2014-08-12-17.52.08.866000+480 I35784932F1196 LEVEL: Severe
    PID : 3380 TID : 2676 PROC : db2syscs.exe
    INSTANCE: DB2DV1 NODE : 000 DB : DV1
    APPHDL : 0-127 APPID: *LOCAL.DB2DV1.140812095207
    AUTHID : DB2DV1
    EDUID : 2676 EDUNAME: db2agent (DV1) 0
    FUNCTION: DB2 UDB, data management, sqldSetupIndexScan, probe:1873
    MESSAGE : ZRC=0x82040001=-2113667071=SQLD_NONSEVERE_PRGERR
    "non-severe dms programming error"
    DIA8532C An internal processing error has occurred.
    DATA #1 : String, 39 bytes
    Specified index not found for scan open
    DATA #2 : String, 12 bytes

    sqldScanOpen
    CALLSTCK:
    [0] 0x000000018010E989 pdLog + 0x353
    [1] 0x0000000003ABE3C2 sqlzSetAndLog901 + 0x192
    [2] 0x0000000001E61F01 sqldSetupIndexScan + 0xF37
    [3] 0x0000000001E5F5CC sqldScanOpen + 0xBEE
    [4] 0x000000000334F460 sqlriopn + 0x316
    [5] 0x00000000034AE788 sqlritaSimplePerm + 0x252
    [6] 0x000000000336AC8B sqlriSectInvoke + 0x139
    [7] 0x00000000030A6F0C sqlrr_process_fetch_request + 0x1A8
    [8] 0x00000000030A2902 sqlrr_open + 0x534
    [9] 0x000000000223FCCB sqljs_ddm_opnqry + 0x447


    2014-08-12-17.52.08.866000+480 I35786130F533 LEVEL: Error
    PID : 3380 TID : 2676 PROC : db2syscs.exe
    INSTANCE: DB2DV1 NODE : 000 DB : DV1
    APPHDL : 0-127 APPID: *LOCAL.DB2DV1.140812095207
    AUTHID : DB2DV1
    EDUID : 2676 EDUNAME: db2agent (DV1) 0
    FUNCTION: DB2 UDB, data management, sqldSetupIndexScan, probe:1873
    DATA #1 : unsigned integer, 4 bytes
    10
    DATA #2 : unsigned integer, 4 bytes
    1704
    DATA #3 : unsigned integer, 2 bytes

    Any suggestion.

  2. #2
    Join Date
    Apr 2012
    Posts
    1,034
    Provided Answers: 18
    Possibly one or more indexes are marked bad.
    Either deactivate and reactivate the database (if indexrec is set to default), or if that's not convenient then rebuild or reorg those indexes.

Tags for this Thread

Posting Permissions

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