Results 1 to 6 of 6

Thread: Db2 mqt

  1. #1
    Join Date
    Mar 2012
    Posts
    3

    Unanswered: Db2 mqt

    Does anyone know why DB2 can not drop a MQT table due to dedlock or time out (Reason Code 68)? I get the same error on executing both commands below.

    ALTER TABLE mqt_table_name
    drop materialized query;

    Drop table mqt_table_name;

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    It's probably being used. What DB2 version?

  3. #3
    Join Date
    Mar 2003
    Posts
    280
    Quote Originally Posted by kalwar View Post
    Does anyone know why DB2 can not drop a MQT table due to dedlock or time out (Reason Code 68)? I get the same error on executing both commands below.

    ALTER TABLE mqt_table_name
    drop materialized query;

    Drop table mqt_table_name;
    My guess is that someone is either reading or - indirectly - writing to the mqt. You can determine what is going on with: Lock timeout reporting

    /Lennart

  4. #4
    Join Date
    Mar 2012
    Posts
    3
    Thank you all for the response. this table was created as a prototype and never has been used, other than during the test period. I guess I'll double check iof there is runaway process thats stinn executing in the background.

    BTW: is there a command to override all locks

  5. #5
    Join Date
    Mar 2003
    Posts
    280
    Quote Originally Posted by kalwar View Post
    BTW: is there a command to override all locks
    No, but you can determine the agent holding the locks and force it to stop


    /Lennart

  6. #6
    Join Date
    Mar 2012
    Posts
    3
    Thank you all for the wonderful insights. Appriciate it.

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
  •