Topic
  • 6 replies
  • Latest Post - ‏2012-10-02T11:55:31Z by SystemAdmin
SystemAdmin
SystemAdmin
5837 Posts

Pinned topic filesystem magic tmpfs

‏2011-07-21T10:30:44Z |
The Express-C working fine until I try to create database onto ramdisk (eg. tmpfs).
At that moment I got system error:


2011-07-20-16.21.11.110440+120 E130762E1115        LEVEL: Error (OS) PID     : 30665                TID  : 47445996202320PROC : db2sysc INSTANCE: venu                 NODE : 000          DB   : PROBA123 EDUID   : 21                   EDUNAME: db2loggr (PROBA123) FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80 MESSAGE : ZRC=0x870F0002=-2029060094=SQLO_BPSE 
"Debug logic error detected" DIA8501C A buffer pool logic error has occurred. CALLED  : OS, -, open                             OSERR: EINVAL (22) DATA #1 : Codepath, 8 bytes 4:11:15:20:22:37 DATA #2 : File name, 74 bytes /sqltemp/sqldata_sqlenpm/db_1/venu/NODE0000/SQL00001/SQLOGDIR/S0000002.LOG DATA #3 : SQO Open File Options, PD_TYPE_SQO_FILE_OPEN_OPTIONS, 4 bytes SQLO_REVISE, SQLO_READWRITE, SQLO_SHAREREAD, SQLO_WRITETHRU, SQLO_SECTOR_ALIGNED, SQLO_NO_THREAD_LEVEL_FILE_LOCK DATA #4 : Hex integer, 4 bytes 0x00000180 DATA #5 : signed integer, 4 bytes 0 DATA #6 : signed integer, 4 bytes 16384 DATA #7 : String, 105 bytes Search 

for ossError*Analysis probe point after 

this log entry 

for further self-diagnosis of 

this problem.


I using DB2 Express-C 9.7 .

Thanks for any advise to solve this problem.
Updated on 2012-10-02T11:55:31Z at 2012-10-02T11:55:31Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    5837 Posts

    Re: filesystem magic tmpfs

    ‏2011-07-21T10:43:35Z  
    Oh, and sorry for my strange display name here. This grabled many year before at conversion of support site, but after many (years/letters I have no success to modify it...
  • SystemAdmin
    SystemAdmin
    5837 Posts

    Re: filesystem magic tmpfs

    ‏2011-11-28T22:23:35Z  
    Oh, and sorry for my strange display name here. This grabled many year before at conversion of support site, but after many (years/letters I have no success to modify it...
    Some additional information:
    The database is created with ATOMATIC STORAGE YES ON ...; DBPATH ON ... command.
    The response is "SQL1042C An unexpected system error occurred SQLSTATE=58004".
  • frabber
    frabber
    2 Posts

    Re: filesystem magic tmpfs

    ‏2012-03-23T08:36:44Z  
    I am in the same boat, I upgraded from 9.1 to 9.7 and now I am unable to create db2 database in ramdisk ( I use a debian live image). Did you ever find a solution to this problem?
  • SystemAdmin
    SystemAdmin
    5837 Posts

    Re: filesystem magic tmpfs

    ‏2012-03-23T09:29:42Z  
    • frabber
    • ‏2012-03-23T08:36:44Z
    I am in the same boat, I upgraded from 9.1 to 9.7 and now I am unable to create db2 database in ramdisk ( I use a debian live image). Did you ever find a solution to this problem?
    Hmm looks like a known issue.. Check this link http://www-01.ibm.com/support/docview.wss?uid=swg1IC63418.

    If possible try any fixpack version of 9.7 eg 97fp1, fp2 etc...

    Thanks
  • frabber
    frabber
    2 Posts

    Re: filesystem magic tmpfs

    ‏2012-03-23T10:40:10Z  
    Hmm looks like a known issue.. Check this link http://www-01.ibm.com/support/docview.wss?uid=swg1IC63418.

    If possible try any fixpack version of 9.7 eg 97fp1, fp2 etc...

    Thanks
    Hello, I have already an applied fp4,

    DB21085I Instance "db2inst1" uses "64" bits and DB2 code release "SQL09074"
    with level identifier "08050107".
    Informational tokens are "DB2 v9.7.0.4", "s110330", "IP23243", and Fix Pack
    "4".

    This is the express version. I also tried the trial version enterprise edition 9.7.5, and had the same error as below.
    I guess installing to ramdisk (tmpfs) for dev purposes is not possible? Used to work with 9.1 though..

    db2diag.log (relevant entries):

    2012-03-23-07.49.06.929530+000 E4314E449 LEVEL: Error (OS)
    PID : 8013 TID : 140565104989984PROC : db2bp
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqlodque, probe:2
    MESSAGE : ZRC=0x870F003E=-2029060034=SQLO_QUE_BAD_HANDLE "Bad Queue Handle"
    DIA8555C An invalid message queue handle was encountered.
    CALLED : OS, -, msgctl OSERR: EINVAL (22)

    2012-03-23-07.54.27.063940+000 E14402E1101 LEVEL: Error (OS)
    PID : 9066 TID : 139967611266816PROC : db2sysc
    INSTANCE: db2inst1 NODE : 000 DB : TestDB
    EDUID : 21 EDUNAME: db2loggr (TestDB)
    FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80
    MESSAGE : ZRC=0x870F0002=-2029060094=SQLO_BPSE "Debug logic error detected"
    DIA8501C A buffer pool logic error has occurred.
    CALLED : OS, -, open OSERR: EINVAL (22)
    DATA #1 : Codepath, 8 bytes
    4:11:15:20:22:37
    DATA #2 : File name, 63 bytes
    /home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/S0000002.LOG
    DATA #3 : SQO Open File Options, PD_TYPE_SQO_FILE_OPEN_OPTIONS, 4 bytes
    SQLO_REVISE, SQLO_READWRITE, SQLO_SHAREREAD, SQLO_WRITETHRU, SQLO_SECTOR_ALIGNED, SQLO_NO_THREAD_LEVEL_FILE_LOCK
    DATA #4 : Hex integer, 4 bytes
    0x00000180
    DATA #5 : signed integer, 4 bytes
    0
    DATA #6 : signed integer, 4 bytes
    16384
    DATA #7 : String, 105 bytes
    Search for ossError*Analysis probe point after this log entry for further
    self-diagnosis of this problem.
    2012-03-23-07.54.27.064688+000 E20509E950 LEVEL: Critical
    PID : 9066 TID : 139967615461120PROC : db2sysc
    INSTANCE: db2inst1 NODE : 000
    APPHDL : 0-8 APPID: *LOCAL.db2inst1.120323075427
    AUTHID : DB2INST1
    EDUID : 20 EDUNAME: db2agent (instance)
    FUNCTION: DB2 UDB, base sys utilities, sqeLocalDatabase::MarkDBBad, probe:10
    MESSAGE : ADM14001C An unexpected and critical error has occurred:
    "DBMarkedBad". The instance may have been shutdown as a result.
    "Automatic" FODC (First Occurrence Data Capture) has been invoked and
    diagnostic information has been recorded in directory
    "/home/db2inst1/sqllib/db2dump/FODC_DBMarkedBad_2012-03-23-07.54.27.0
    64660_0000/". Please look in this directory for detailed evidence
    about what happened and contact IBM support if necessary to diagnose
    the problem.
  • SystemAdmin
    SystemAdmin
    5837 Posts

    Re: filesystem magic tmpfs

    ‏2012-10-02T11:55:31Z  
    • frabber
    • ‏2012-03-23T10:40:10Z
    Hello, I have already an applied fp4,

    DB21085I Instance "db2inst1" uses "64" bits and DB2 code release "SQL09074"
    with level identifier "08050107".
    Informational tokens are "DB2 v9.7.0.4", "s110330", "IP23243", and Fix Pack
    "4".

    This is the express version. I also tried the trial version enterprise edition 9.7.5, and had the same error as below.
    I guess installing to ramdisk (tmpfs) for dev purposes is not possible? Used to work with 9.1 though..

    db2diag.log (relevant entries):

    2012-03-23-07.49.06.929530+000 E4314E449 LEVEL: Error (OS)
    PID : 8013 TID : 140565104989984PROC : db2bp
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqlodque, probe:2
    MESSAGE : ZRC=0x870F003E=-2029060034=SQLO_QUE_BAD_HANDLE "Bad Queue Handle"
    DIA8555C An invalid message queue handle was encountered.
    CALLED : OS, -, msgctl OSERR: EINVAL (22)

    2012-03-23-07.54.27.063940+000 E14402E1101 LEVEL: Error (OS)
    PID : 9066 TID : 139967611266816PROC : db2sysc
    INSTANCE: db2inst1 NODE : 000 DB : TestDB
    EDUID : 21 EDUNAME: db2loggr (TestDB)
    FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80
    MESSAGE : ZRC=0x870F0002=-2029060094=SQLO_BPSE "Debug logic error detected"
    DIA8501C A buffer pool logic error has occurred.
    CALLED : OS, -, open OSERR: EINVAL (22)
    DATA #1 : Codepath, 8 bytes
    4:11:15:20:22:37
    DATA #2 : File name, 63 bytes
    /home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/S0000002.LOG
    DATA #3 : SQO Open File Options, PD_TYPE_SQO_FILE_OPEN_OPTIONS, 4 bytes
    SQLO_REVISE, SQLO_READWRITE, SQLO_SHAREREAD, SQLO_WRITETHRU, SQLO_SECTOR_ALIGNED, SQLO_NO_THREAD_LEVEL_FILE_LOCK
    DATA #4 : Hex integer, 4 bytes
    0x00000180
    DATA #5 : signed integer, 4 bytes
    0
    DATA #6 : signed integer, 4 bytes
    16384
    DATA #7 : String, 105 bytes
    Search for ossError*Analysis probe point after this log entry for further
    self-diagnosis of this problem.
    2012-03-23-07.54.27.064688+000 E20509E950 LEVEL: Critical
    PID : 9066 TID : 139967615461120PROC : db2sysc
    INSTANCE: db2inst1 NODE : 000
    APPHDL : 0-8 APPID: *LOCAL.db2inst1.120323075427
    AUTHID : DB2INST1
    EDUID : 20 EDUNAME: db2agent (instance)
    FUNCTION: DB2 UDB, base sys utilities, sqeLocalDatabase::MarkDBBad, probe:10
    MESSAGE : ADM14001C An unexpected and critical error has occurred:
    "DBMarkedBad". The instance may have been shutdown as a result.
    "Automatic" FODC (First Occurrence Data Capture) has been invoked and
    diagnostic information has been recorded in directory
    "/home/db2inst1/sqllib/db2dump/FODC_DBMarkedBad_2012-03-23-07.54.27.0
    64660_0000/". Please look in this directory for detailed evidence
    about what happened and contact IBM support if necessary to diagnose
    the problem.
    Need to create your ramdisk with a different file system type i.e. ext3
    you can try
    mkfs.ext3 /dev/ram0
    mkdir /ramdisk
    mount /dev/ram0 /ramdisk
    df -h shows the default size maybe 16M

    You can increase by adding ramdisk_size=xxxxxx /etc/grub.conf so it looks like this:
    kernel /vmlinuz-2.6.32-71.el6.x86_64 ro root=/dev/mapper/vg00-lv01 rd_o rhgb quiet ramdisk_size=5000000
    reboot after you are done
    This approx gives you 4.5G