Results 1 to 9 of 9
  1. #1
    Join Date
    Apr 2009
    Posts
    42

    Unanswered: online backup error

    Hello,

    My backup failed with sql0911n. I see this error:


    2009-06-09-00.00.43.926292 I1598A523 LEVEL: Error
    PID : 1960345 TID : 1 PROC : db2bm
    INSTANCE: db2inst1 NODE : 000 DB : UATDB
    APPHDL : 0-694 APPID: *N0.db2inst1.080470543
    FUNCTION: DB2 UDB, database utilities, SqlubTableLock::request, probe:153
    DATA #1 : String, 59 bytes
    Error upgrading lock.
    PoolId: 0, ObjectId: 2, Intent: 3.


    Can you offer some advice? Thank you!

  2. #2
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    SYSIBM.SYSTABLES is locked.
    Most common reason is RUNSTATS ?
    Are you doing one, when you initiate the backup

    Cheers
    Sathyaram
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  3. #3
    Join Date
    Apr 2009
    Posts
    42
    Thank you. I don't think we execute runstats during the week. This is an online backup so why would db2 care if some table is locked? Any reason why it can't backup a table even if it's locked?

  4. #4
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    RUNSTATS takes a exclusive row locks in few system catalog tables ...

    DB2 needs a consistent copy of the system catalog tables for backup. Hence, if the system table is locked (table or row) in exclusive mode, then backup fails.

    If it is a user table that is locked, then backup will continue ...

    Once the system tables are backed up, then it doesn't matter if RUNSTATS starts - as there is a consistent copy already for that image.

    Hope this explains
    Last edited by sathyaram_s; 06-12-09 at 08:02.
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  5. #5
    Join Date
    Nov 2005
    Location
    IL
    Posts
    557
    depending what ver you are on, you might want to check on AUTO_RUNSTATS parm. If it is ON db is doing stats for you.
    --
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows

    DB2 v9.7.0.6 os 6.1.0.0

  6. #6
    Join Date
    Apr 2009
    Posts
    42
    auto runstats is off.

    Is there any workaround for this locking problem?

  7. #7
    Join Date
    Nov 2005
    Location
    IL
    Posts
    557
    Yes, script your script to send a backup into a sleep mode for a while and then do another attempt.

    Check for locks first and either wait or force them. there are more depending on your business requirements.
    --
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows

    DB2 v9.7.0.6 os 6.1.0.0

  8. #8
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    see the following technote for some additional info:
    IBM - DB2 online backup fails with SQL0911N reason code 68

  9. #9
    Join Date
    Apr 2007
    Posts
    6
    This is very common in our environment, most of time the deadlock was caused by runstats or reorg running on the table when backup was started. Also db2diag.log will show you the detail.
    ---------------
    Eric Xu (许 昌)

Posting Permissions

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