Results 1 to 4 of 4
  1. #1
    Join Date
    Dec 2002
    Location
    Madrid - Spain
    Posts
    422
    Provided Answers: 1

    Unanswered: Problem reorganizing a long table.

    Good afternoon,
    I have AIX 5.3 DB2 V8.
    I have run the reorg command to 4GB Data table, I aborted the execution and the table has been in a state inaccessible.

    db2 "reorg table schema.table ALLOW READ ACCESS use temporal3"

    The execution was aborted when it started generating locks, lock-waiting.

    Because the state table is inaccessible?

    In the end I had to run a restore of the database.

    Can someone explain the reason or this problem?

    Thank you very much and best regards.
    DBA DB2 for LUW

  2. #2
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    Table in inaccessible state - What is the error message you received?

    Do you know what phase reorg was in when you cancelled it? If it was in index rebuild, then db2 needs to rebuild them before you can access the table.

  3. #3
    Join Date
    Dec 2002
    Location
    Madrid - Spain
    Posts
    422
    Provided Answers: 1
    Good Morning,

    phase unaware that the reorg was like to know?

    At one point it started to generate lock-waiting, why?

    At the time the user had reorg using the table.

    The syntax used in correct?
    db2 "reorg table schema.table use temporal3 ALLOW READ ACCESS"

    Thank you very much and best regards.
    DBA DB2 for LUW

  4. #4
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    Quote Originally Posted by georgipa View Post
    At one point it started to generate lock-waiting, why?
    Reorg acquires locks. Could not find this info in v8 InfoCenter, here's v9.7 link:
    IBM DB2 9.7 for Linux, UNIX and Windows Information Center

Posting Permissions

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