Results 1 to 3 of 3
  1. #1
    Join Date
    Aug 2009
    Posts
    11

    Unanswered: The directory where the database is being restored has become full

    Hi Guys,

    I was doing a full db restore and after 2 days I received the message that the directory where the database file is being restored is full. I was checking the size of the disks over the weekend and I saw no growth.

    The thing is, I had the db2 tablespaces spread across different disks. Would the restore place the filesystems on the corresponding disk or try to put everything on the current disk where the restore was issued? I put the output from the db2diag.log, but it shows something about bufferpool.

    db2v 7.1 on SunOS 5.8


    Code:
    2009-08-24-03.29.37.474492   Instance:db2inst1   Node:000
    PID:8259(db2bm.8248.0)   Appid:none
    buffer_pool_services  sqlbDMSDirectWrite   Probe:790 
    
    DiagData
    018a 69c0 0002 0000 0000 00ff 0001 132a       ..i............*                
    0001 122b 0035 8000 0000 0001 0000 0000       ...+.5..........                
    11ec 9200 018a 6a20 0000 0000 0000 0000       ......j ........                
    
    
    2009-08-24-03.29.37.689073   Instance:db2inst1   Node:000
    PID:8259(db2bm.8248.0)   Appid:none
    buffer_pool_services  sqlbDMSDirectWrite   Probe:860 
    DIA3612C Disk was full.
    
    ZRC=FFFFD60C
    
    2009-08-24-03.29.37.863033   Instance:db2inst1   Node:000
    PID:8259(db2bm.8248.0)   Appid:none
    buffer_pool_services  sqlbDMSDirectWrite   Probe:860 
    
     Obj={pool:28;obj:0;type:0} State=x0 Parent={0;0}, EM=0, PP0=0 Page=70656 Cont=0 Offset=70657 BlkSize=14
    
    Data Title:SQLB_OBJECT_DESC PID:8259 Node:000
    001c 0000 0000 0000 0000 0000 0000 0000       ................                
    0000 0000 0000 0000 0000 0000 0000 0000       ................                
    0000 0000 0000 0002 0000 0000 0000 0000       ................                
    0000 4000 0000 0010 0000 0000 0000 0000       ..@.............                
    0000 0000 0000 0000                           ........                
    
    
    2009-08-24-03.29.38.215610   Instance:db2inst1   Node:000
    PID:8259(db2bm.8248.0)   Appid:none
    buffer_pool_services  sqlbDirectWrite   Probe:820 
    DIA3612C Disk was full.
    
    ZRC=FFFFD60C
    
    2009-08-24-03.29.38.335473   Instance:db2inst1   Node:000
    PID:8259(db2bm.8248.0)   Appid:none
    buffer_pool_services  sqlbDirectWrite   Probe:820 
    
     Obj={pool:28;obj:0;type:0} State=x0 Parent={0;0}, EM=0, PP0=0
    
    Data Title:SQLB_OBJECT_DESC PID:8259 Node:000
    001c 0000 0000 0000 0000 0000 0000 0000       ................                
    0000 0000 0000 0000 0000 0000 0000 0000       ................                
    0000 0000 0000 0002 0000 0000 0000 0000       ................                
    0000 4000 0000 0010 0000 0000 0000 0000       ..@.............                
    0000 0000 0000 0000                           ........                
    
    
    2009-08-24-03.29.38.665039   Instance:db2inst1   Node:000
    PID:8259(db2bm.8248.0)   Appid:none
    database_utilities  sqludrdd   Probe:20 
    
    DiagData
    ffff d60c                                     ....                
    
    
    2009-08-24-03.29.38.785031   Instance:db2inst1   Node:000
    PID:8259(db2bm.8248.0)   Appid:none
    database_utilities  sqluwritedms   Probe:20 
    
    DiagData
    ffff d60c                                     ....                
    
    
    2009-08-24-03.29.38.916802   Instance:db2inst1   Node:000
    PID:8259(db2bm.8248.0)   Appid:none
    database_utilities  sqluwritedms   Probe:1220 
    
    ffff d60c                                     ....                
    
    
    2009-08-24-03.29.39.354734   Instance:db2inst1   Node:000
    PID:8248(db2agent (TDWDB))   Appid:*LOCAL.db2inst1.090821205918
    database_utilities  sqludrsa   Probe:0   Database:TDWDB
    
    Restore terminated.
    Last edited by rhayabusa22; 08-24-09 at 11:46.

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    RESTORE re-creates tablespace containers as defined in the backup image. You can figure out which tablespace ran out of space by looking in SYSCAT.TABLESPACES for TBSPACEID=28, which is indicated in the log.
    ---
    "It does not work" is not a valid problem statement.

  3. #3
    Join Date
    Aug 2009
    Posts
    11

    Yeah

    Thanks for the reply; appreciate it. Looked at the disks that hold that tablespace and they are atleast 52% full.

Posting Permissions

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