Results 1 to 7 of 7
  1. #1
    Join Date
    Mar 2003
    Posts
    4

    Red face Unanswered: Help ! DB2 / Raw logical device issue on AIX

    Help !

    Im an Oracle DBA, but have been "given" the task of rescuing a DB2 database, and am struggling with the following situation.
    Any suggestions on what to do would be very well received, as I dont seem to be able to overcome this one, and its becoming increasingly urgent!

    Many thanks in advance to anyone who offers me a much needed suggestion !

    John.



    A disk failed in our RAID array, which was being used by DB2 on a pSeries (AIX 4.3.3)

    Our AIX engineer has replaced a disk in the raid array by creating a candidate disk in the SSA array and SWAPping the bad existing disk for a new candidate disk.

    There is a raw logical device used by DB2 on this disk, which still seems to exist (its called Ddata);

    # lsvg -l vg00
    vg00:
    LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
    fslv00 jfs 64 64 1 open/syncd /db2home
    loglv01 jfslog 1 1 1 open/syncd N/A
    Ddata jfs 160 160 1 closed/syncd N/A


    But DB2 cannot find the raw logical device;

    DB2 cannot access the tablespace container
    db2 => LIST TABLESPACE CONTAINERS FOR 2 SHOW DETAIL
    Tablespace Containers for Tablespace 2
    Container ID = 0
    Name = /dev/rDdata
    Type = Disk
    Total pages = 2500000
    Useable pages = 2499968
    Accessible = No


    The tablespace status:
    Tablespace ID = 2
    Name = USERSPACE1
    Type = Database managed space
    Contents = Any data
    State = 0x4000
    Detailed explanation:
    Offline


    and I cannot seem to get the tablespace online;


    db2 => alter tablespace USERSPACE1 switch online
    DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned:
    SQL0293N Error accessing a table space container. SQLSTATE=57048

  2. #2
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650

    Re: Help ! DB2 / Raw logical device issue on AIX

    Have a look at what $INSTHOME/sqllib/db2diag.log says ...

    My feeling is that you will have to restore the tablespace ....

    Have a look at

    http://www-3.ibm.com/cgi-bin/db2www/...5.htm#HDRRECTS

    Sorry for giving a pointer to the documentation at the critical stage you are in ... But see if it helps ....

    Cheers

    Sathyaram


    Originally posted by sudmill
    Help !

    Im an Oracle DBA, but have been "given" the task of rescuing a DB2 database, and am struggling with the following situation.
    Any suggestions on what to do would be very well received, as I dont seem to be able to overcome this one, and its becoming increasingly urgent!

    Many thanks in advance to anyone who offers me a much needed suggestion !

    John.



    A disk failed in our RAID array, which was being used by DB2 on a pSeries (AIX 4.3.3)

    Our AIX engineer has replaced a disk in the raid array by creating a candidate disk in the SSA array and SWAPping the bad existing disk for a new candidate disk.

    There is a raw logical device used by DB2 on this disk, which still seems to exist (its called Ddata);

    # lsvg -l vg00
    vg00:
    LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
    fslv00 jfs 64 64 1 open/syncd /db2home
    loglv01 jfslog 1 1 1 open/syncd N/A
    Ddata jfs 160 160 1 closed/syncd N/A


    But DB2 cannot find the raw logical device;

    DB2 cannot access the tablespace container
    db2 => LIST TABLESPACE CONTAINERS FOR 2 SHOW DETAIL
    Tablespace Containers for Tablespace 2
    Container ID = 0
    Name = /dev/rDdata
    Type = Disk
    Total pages = 2500000
    Useable pages = 2499968
    Accessible = No


    The tablespace status:
    Tablespace ID = 2
    Name = USERSPACE1
    Type = Database managed space
    Contents = Any data
    State = 0x4000
    Detailed explanation:
    Offline


    and I cannot seem to get the tablespace online;


    db2 => alter tablespace USERSPACE1 switch online
    DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned:
    SQL0293N Error accessing a table space container. SQLSTATE=57048

  3. #3
    Join Date
    Mar 2003
    Posts
    4
    Thanks for the assistance.

    The crucial bit of the log is as follows;

    2003-03-03-14.24.54.317223 Instance:db2inst1 Node:000
    PID:20384(db2agent (TARGETDB)) Appid:*LOCAL.db2inst1.030303062453
    buffer_pool_services sqlbDMSDoContainerOp Probe:810 Database:TARGETDB
    DIA9999E An internal error occurred. Report the following error code :
    "FFFFC11E".

    2003-03-03-14.24.54.360839 Instance:db2inst1 Node:000
    PID:20384(db2agent (TARGETDB)) Appid:*LOCAL.db2inst1.030303062453
    buffer_pool_services sqlbDMSDoContainerOp Probe:810 Database:TARGETDB

    Error checking container 0 (/dev/rDdata) for tbsp 2. Rc = FFFFE60A

    2003-03-03-14.24.54.477800 Instance:db2inst1 Node:000
    PID:20384(db2agent (TARGETDB)) Appid:*LOCAL.db2inst1.030303062453
    buffer_pool_services sqlbDMSStartPool Probe:800 Database:TARGETDB
    DIA9999E An internal error occurred. Report the following error code :
    "FFFFC11E".

    2003-03-03-14.24.54.500938 Instance:db2inst1 Node:000
    PID:20384(db2agent (TARGETDB)) Appid:*LOCAL.db2inst1.030303062453
    buffer_pool_services sqlbDMSStartPool Probe:800 Database:TARGETDB

    Tablespace 2 (USERSPACE1)


    2003-03-03-14.24.54.599786 Instance:db2inst1 Node:000
    PID:20384(db2agent (TARGETDB)) Appid:*LOCAL.db2inst1.030303062453
    buffer_pool_services sqlbStartPools Probe:30 Database:TARGETDB

    Tablespace USERSPACE1 (2) is in state x4000.
    Starting it failed. rc=ffff c11e ....



    Can anyone shed any light on this? At th minute Im trying to work out if the is acutally a backup of this database ! (every DBAs nightmare I know!)

    Cheers,

    John.

  4. #4
    Join Date
    Jul 2002
    Location
    ATL
    Posts
    170
    I think the tablespace file does not exist on the raw device you hooked up. It could be the raw device corrupted or wrong raw device.
    My assumptions are based on looking at your db2diag.log

  5. #5
    Join Date
    Aug 2002
    Location
    delhi, india
    Posts
    4
    Originally posted by koganti
    I think the tablespace file does not exist on the raw device you hooked up. It could be the raw device corrupted or wrong raw device.
    My assumptions are based on looking at your db2diag.log

    Yes the tablespace file does not exist ..
    I am also facing the same problem . Can any body tell me what to do in this situtaion ..
    There is no way in which i can get back the container files .
    i just want to drop that tablespace .. but while droping it .DB is giving me error that can't access container
    Regards
    Yogesh

  6. #6
    Join Date
    Sep 2002
    Posts
    456
    Well, your problem is smilar to another one in this forum, so here are my two cents:

    >> Try recovering the file/directory for that tablespace if you guys are taking system backup IF NOT
    >> Restore the database if image is available (consider doing redirected restore) IF NOT
    >> Is this database reproduceable? i.e. read only type of database IF YES then drop and re-create it.

    Please note there might be other options so make your decision with extreme care. I will use the first two options and third one if nothing else is working.

    dollar

    Originally posted by yogeshkansal
    Yes the tablespace file does not exist ..
    I am also facing the same problem . Can any body tell me what to do in this situtaion ..
    There is no way in which i can get back the container files .
    i just want to drop that tablespace .. but while droping it .DB is giving me error that can't access container
    Regards
    Yogesh

  7. #7
    Join Date
    Mar 2003
    Posts
    4
    Just to let you know .. the solution to my problem, was that somehow the raw logical device had a default name, and the entry for the raw device didnt exist in the /dev/ directotry, therefor DB2 could find it.
    Once this was renamed to the correct and expected name, the database seemed ok. Good luck.

Posting Permissions

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