Results 1 to 6 of 6
  1. #1
    Join Date
    Mar 2001
    Location
    Lexington, KY
    Posts
    606

    Unanswered: ASE 12.5.3.4, SuSE9, and trace flag 1630

    We're running ASE on SuSE, and per the latest EBF:

    CR 403972 - Async i/o support on SuSE

    Prior to ASE 12.5.3 ESD#2 release, ASE was able to automatically
    switch to using Posix Async i/o on SuSE Linux (32 bit) systems.
    Due to 376419 fix in ASE 12.5.3 ESD#2, ASE incorrectlty reports
    that ASE is using KAIO while it is using Posix AIO.
    This can lead to unexpected behavior of ASE. ASE should be booted with
    traceflag 1630 on 32-bit SuSE Linux to explicitly enable Posix async i/o.
    --------

    Running with trace flag 1630 gives:
    /opt/sybase/ASE/install # ./startserver -f RUN_SYBPANDA
    /opt/sybase/ASE/install # /opt/sybase/ASE-12_5/bin/dataserver: relocation error: /lib/librt.so.1: symbol __librt_multiple_threads, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

    Any ideas?
    Thanks,

    Matt

  2. #2
    Join Date
    May 2005
    Location
    Paris
    Posts
    46
    Hi,

    you have read this technote :

    http://www.sybase.com/detail?id=1036918



    Workaround: Disable Large Memory Support by setting extended cache size to zero. To do this, execute this command:

    sp_configure "extended cache size", 0


    normally you have right in 12.5.3 ESD3 and ESD4 should resolve this bug.


    I have personnaly a box with the same configuration :
    Adaptive Server Enterprise/12.5.3/EBF 12876 ESD#4/P/Linux Intel/Enterprise Linux/ase1253/1923/32-bit/OPT/Thu Sep 8 06:16:18 2005

    and my errorlog :

    00:00000:00000:2005/10/11 11:57:50.36 kernel Enabling (RT) Posix asynchronous disk I/O strategy.
    00:00000:00000:2005/10/11 11:57:50.39 kernel Initializing virtual device 0, '/sybase/sybase_devices/IENA_SQL/master.dat' with dsync 'on'.
    00:00000:00000:2005/10/11 11:57:50.40 kernel Virtual device 0 started using asynchronous i/o.


    strange, I will check a eventual solution ...

  3. #3
    Join Date
    May 2005
    Location
    Paris
    Posts
    46
    1630 Use platform specific Async I/O mechanism.
    When set it enables Posix Async I/O.
    The default is KAIO. (This is a Sun specific flag).


    may you try without this traceflag ?

    are you using FS or raw devices ?
    and device option dsync ?

  4. #4
    Join Date
    May 2005
    Location
    Paris
    Posts
    46
    CR 403972 is fixed in ASE 12.5.3 ESD #5.
    It has a sanitized description of:

    "On SuSE 32 bit Linux platform,
    ASE incorrectly identifies AIO to be KAIO while using Posix AIO.
    This can lead to ASE hang. Solution is to start ASE with trace flag 1630. "

    ??

  5. #5
    Join Date
    Mar 2001
    Location
    Lexington, KY
    Posts
    606
    Ok, so we should wait to ESD #5? And after we upgrade, we should not use tf 1630??
    Thanks,

    Matt

  6. #6
    Join Date
    May 2005
    Location
    Paris
    Posts
    46
    hi,
    So the next ESD will be normally Ok for the next month (december 2005),

    for the traceflag, I don't know really.

    I think you could let it active for the moment.

Posting Permissions

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