Results 1 to 5 of 5
  1. #1
    Join Date
    Jul 2010
    Posts
    4

    Unanswered: Instance aborted automatically

    hi,

    i am using db2 9.5 version. when i start running application, i am getting the below error.

    58004(-901)[IBM][CLI Driver][DB2/AIX64] SQL0901N The SQL statement failed because of a non-severe system error. Subsequent SQL statements can be processed. (Reason "bad opcode".) SQLSTATE=58004


    can anyone advice on this...

  2. #2
    Join Date
    Dec 2008
    Location
    Toronto, Canada
    Posts
    399
    Index data consistency problem toleration is higher
    In Version 9.5, when an index is no longer consistent, an error message (SQL0901N ) is returned to the application instead of the database and instance being brought down.

    When the error message is returned, you can use the INSPECT command or the db2inspect API to do online checking for the cause of the index inconsistency, while still allowing other applications access to those database objects not being evaluated. This type of error toleration is enabled only for regular indexes, on both partitioned and nonpartitioned tables, and for indexes on multidimensional clustering indexes. This type of error toleration is not enabled for multidimensional clustering block indexes, composite block indexes, spatial indexes, and XML indexes.
    DB2 9.5/9.7 on Unix/AIX 6.1/Linux

  3. #3
    Join Date
    Jul 2010
    Posts
    4
    thanks markham

  4. #4
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    You may consider opening a PMR if this error is unresolved.

  5. #5
    Join Date
    Aug 2010
    Posts
    1
    Thanks this was very helpful

Posting Permissions

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