Results 1 to 4 of 4
  1. #1
    Join Date
    Jun 2007
    Posts
    12

    Unanswered: raw device problem with solaris and db2 v8

    I'm running a V8.2 fp15 database on Solaris 10 with key tablespaces on a pair of raw devices. Each of these raw devices is on a Veritas-managed RAID5 array.
    This weekend, I started a backup command and both of these raw devices returned an inaccessible device error. (Tablespace state 0x4000) Switching the tablespaces online failed. In the end, the only solution I was able to arrive at was to drop the database, untag the raw devices and restore from backup.
    Has anyone seen a problem like this before? Am I running with known incompatabilities in my system? Any insights are appreciated.
    -Andy Beaton

    Software versions:
    =====================
    DB21085I Instance "***" uses "32" bits and DB2 code release "SQL08028"
    with level identifier "03090106".
    Informational tokens are "DB2 v8.1.0.136", "s070720", "U810953", and FixPak
    "15".
    Product is installed at "/opt/IBM/db2/V8.1".
    ================================================== =====

    NAME: Binaries for VERITAS Volume Manager by Symantec
    CATEGORY: system
    ARCH: sparc
    VERSION: 5.0,REV=05.11.2006.17.55

    ================================================== =====
    Release: 5.10
    Kernel architecture: sun4u
    Application architecture: sparc
    Hardware provider: Sun_Microsystems
    Domain:
    Kernel version: SunOS 5.10 Generic_127111-06

  2. #2
    Join Date
    Oct 2008
    Posts
    11
    Did you see any error messages in db2diag.log or OS logs?

  3. #3
    Join Date
    Jun 2007
    Posts
    12
    No errors were reported by either the OS or db2 before a container tag and tablespace not accessible error in db2diag.log

    ================================================== ==========
    2008-09-26-18.10.32.568956-240 I62428273C2744 LEVEL: Severe
    PID : 11133 TID : 1 PROC : db2agent (<dbname>) 0
    INSTANCE: <instname> NODE : 000 DB : <dbname>
    APPHDL : 0-19 APPID: *LOCAL.instname.080926221027
    FUNCTION: DB2 UDB, buffer pool services, sqlbContainerTagIsValid, probe:100
    MESSAGE : *pTag(CONTAINER_TAG)
    DATA #1 : Hexdump, 512 bytes
    0x02832A00 : 4442 3243 4F4E 5400 0000 0213 5EDC F088 DB2CONT.....^...
    .
    .
    .

    2008-09-26-18.10.32.569429-240 I62431018C2743 LEVEL: Severe
    PID : 11133 TID : 1 PROC : db2agent (<dbname>) 0
    INSTANCE: <instname> NODE : 000 DB : <dbname>
    APPHDL : 0-19 APPID: *LOCAL.instname.080926221027
    FUNCTION: DB2 UDB, buffer pool services, sqlbContainerTagIsValid, probe:200
    MESSAGE : iTag(CONTAINER_TAG)
    DATA #1 : Hexdump, 512 bytes
    0xFFBEB414 : 4442 3243 4F4E 5400 0000 0213 5EDC F088 DB2CONT.....^...
    .
    .
    .
    2008-09-26-18.10.32.587271-240 I62433762C448 LEVEL: Error
    PID : 11133 TID : 1 PROC : db2agent (<dbname>) 0
    INSTANCE: instname NODE : 000 DB : <dbname>
    APPHDL : 0-19 APPID: *LOCAL.instname.080926221027
    FUNCTION: DB2 UDB, buffer pool services, sqlbDMSDoContainerOp, probe:840
    RETCODE : ZRC=0x8402001E=-2080243682=SQLB_CONTAINER_NOT_ACCESSIBLE
    "Container not accessible"

  4. #4
    Join Date
    Oct 2008
    Posts
    11
    Hi

    From these messages I could point the following things here..

    SQLB_CONTAINER_NOT_ACCESSIBLE

    This error may be caused by one of the following conditions:

    o A container (directory, file or raw device) was not found.

    o A container is not tagged as being owned by the proper table
    space.

    o A container tag is corrupt.

    If the error persists, call your IBM service representative.

Posting Permissions

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