Does anyone have any details on RedHat Linux bug 891857?

Huge page support was disabled with SA CR 728597 due to RH bug.

CR 728597: This problem is related to a possible bug in the transparent huge pages (THP) feature introduced in these operating system versions. RedHat bug 891857 has been created to track this issue. There is a huge difference between a RedHat specific bug, a bug that affects only RedHat Enterprise Linux, and a Linux (Kernel?) bug that affects other distributions. Remember that SuSE Enterprise Linux is fully supported by SAP/Sybase.

I don’t have a support contract with RedHat, so I can’t see what bug 891857 actually is.

UPDATE:

With regard to Sybase IQ bug CR728597 and RedHat bug 891857 involving memory corruption due to Direct I/O and Transparent Huge Memory Pages, I was able to reach the RedHat engineer.  Andrea Arcangeli reported the issue to the Linux kernel mailing list back in 2009.  The issue was never resolved because of the complexity of the fix. https://patchwork.kernel.org/patch/11174 includes both the patch to the kernel branch of the time and the ‘repro’ C example.

Share Button

Upgrading Sybase ASE 12.5.4 -> 15.0.3 esd 4 & bug # 643188

Sybase

We’ve been upgrading a number of Sybase ASE databases from the end-of-life’d 12.5.x to v15.0.3 esd 4 the last few weeks.   My coworker (Degang He) ran into an interesting error when the upgrade process was failing on sysprocedures.

Database 'my_db': beginning upgrade step [ID 26]: alter table (table sysprocedures)
Command has been aborted.

Msg 3461, Level 20, State 1:
Server 'my_server', Line 1:
Database 'my_db': upgrade could not install required upgrade item '26'. Please refer to previous error messages to determine the problem. Fix the problem, then try again.

Msg 3451, Level 20, State 1:
Server 'my_server', Line 1:
Database 'my_db': upgrade has failed for this database. Please refer to previous messages for the cause of the failure, correct the problem and try again.

Msg 3454, Level 20, State 1:
Server 'my_server', Line 1:

Database 'my_db': ASE could not completely upgrade this database; upgrade item 1501 could not be installed.

We looked on Sybase’s Solved Cases and Google but didn’t find anything that would really fit the problem.  So we called up Sybase Technical Support.  Somdev Sharma of Sybase was able to determine that this was a bug in the ASE 15x codeline and provided a workaround:

CR #643188:

Title Online database failed with 3461 error during upgrade , ‘max parallel degree’ >1

Workaround:

Before online the database, disable parallel sort via sp_configure ‘max parallel degree’,1

Sanitized:

Online database failed with 3461, 3451 and 3454 errors during upgrade sysprocedures table (upgrade  item ’26’). If ‘max parallel degree’ > 1, then please disable parallel sort with sp_configure ‘max parallel degree’, 1.

After disabling parallel sort, the database was upgraded successfully.

Share Button

Received ‘Can’t call method “value” on an undefined value at /usr/share/perl5/IO/Uncompress/RawInflate.pm’ on Ubuntu 8.04 Server (Hardy Heron)

On my media server, I wanted to set up Perl’s CPAN but when I ran install Bundle::CPAN, I ctrl-c’d out of it when I noticed that bzip2 wasn’t installed.  Silly me.  Soon after I started receiving:

Can’t call method “value” on an undefined value at /usr/share/perl5/IO/Uncompress/RawInflate.pm

Reinstalling Perl and all the related ubuntu packages doesn’t fix it, nor does removing the ~root/.cpan dir.  There is an easy workaround though.

aptitude remove libcompress-raw-zlib-perl
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Reading extended state information      
Initializing package states... Done
Building tag database... Done      
The following packages are BROKEN:
  libio-compress-zlib-perl 
The following packages have been kept back:
  bind9-host dnsutils libbind9-30 libisccfg30 
The following packages will be REMOVED:
  libcompress-raw-zlib-perl 
0 packages upgraded, 0 newly installed, 1 to remove and 4 not upgraded.
Need to get 0B of archives. After unpacking 319kB will be freed.
The following packages have unmet dependencies:
  libio-compress-zlib-perl: Depends: libcompress-raw-zlib-perl (>= 2.008) but it is not installable
Resolving dependencies...
The following actions will resolve these dependencies:

Remove the following packages:
apparmor-utils
libcompress-zlib-perl
libio-compress-zlib-perl
libmp3-tag-perl
librpc-xml-perl
libwww-perl
libxml-parser-perl
ubuntu-standard

Score is 592

Accept this solution? [Y/n/q/?] 

Make a note of the packages that it will remove, then tell it to go ahead. It will remove these packages!

Start cpan, and type in

install Bundle::CPAN

When it is complete, reinstall the ubuntu packages that you removed earlier (for example):

aptitude install apparmor-utils libcompress-zlib-perl libio-compress-zlib-perl libmp3-tag-perl librpc-xml-perl libwww-perl libxml-parser-perl ubuntu-standard

That’s it. Your cpan is working again 🙂

Share Button

SQL::Translator::Parser::DBI::Sybase bug (35380) causes script to fail when sp_helpindex doesn’t return a result set

35380: SQL::Translator::Parser::DBI::Sybase fails when sp_helpindex is empty

Centos 5
Linux dba-dev1 2.6.22.9-default #1 SMP Mon Oct 1 11:26:48 CDT 2007 i686
athlon i386 GNU/Linux

Perl v5.8.8 built for i386-linux-thread-multi
SQL::Translator::0.09000

Sybase ASE’s sp_helpindex will normally return a result set containing
the column “INDEX_NAME” which parse() requires. When no index exists,
sp_helpindex returns a error string similar to “Object does not have any
indexes.” but no result set.

The following workaround simply wraps the selectall_hash with an eval,
if the eval results in no error, then try to use the hash.

diff Sybase_orig.pm Sybase_new.pm
252,259c252,259
< my $h = $dbh->selectall_hashref("sp_helpindex
< $table_info->{TABLE_NAME}", 'INDEX_NAME');
< foreach (values %{$h}) {
<                     my $fields = $_->{'INDEX_KEYS'};
< $fields =~ s/\s*//g;
<                     my $i = $table->add_index(
< name   =>
< $_->{INDEX_NAME},
---
>                 my $h;
>                 eval { $h = $dbh->selectall_hashref("sp_helpindex $table_info->{TABLE_NAME}", 'INDEX_NAME') }; 
>                               unless ($@) {
>                   foreach (values %{$h}) {
>                       my $fields = $_->{'INDEX_KEYS'};
>                       $fields =~ s/\s*//g;
>                       my $i = $table->add_index(
>                                                 name   => $_->{INDEX_NAME},
262,263c262,263
< if ($_->{'INDEX_DESCRIPTION'} =~ /unique/i) {
< $i->type('unique');
---
>                       if ($_->{'INDEX_DESCRIPTION'} =~ /unique/i) {
>                           $i->type('unique');
265,276c265,277
< # we could make this a primary key if there
<                         # isn't already one defined and if there
<                         # aren't any nullable columns in thisindex.
< 
<                         if (!defined($table->primary_key())) {
< $table->primary_key($fields)
< unless grep {
<                                     $table->get_field($_)->is_nullable()
< } split(/,\s*/, $fields);
<                         }
<                     }
<                 }
---
>                           # we could make this a primary key if there
>                           # isn't already one defined and if there
>                           # aren't any nullable columns in thisindex.
>   
>                           if (!defined($table->primary_key())) {
>                               $table->primary_key($fields)
>                                   unless grep {
>                                       $table->get_field($_)->is_nullable()
>                                   } split(/,\s*/, $fields);
>                           }
>                      }
>                  }
>               }
Share Button

ASE 15 stored procedure “sp_tables” doesn’t work with SQL UDFs

The ASE 15 stored procedure sp_tables doesn’t work with SQL UDFs. sp_tables has the udfs coming back as system tables.

repro:
1) create a sql udf in a db
2) run sp_tables, you will see the UDF as a “SYSTEM TABLE”

DBADEV1.sybase_dba.1> sp_tables;
table_qualifier table_owner table_name table_type remarks
--------------- ----------- ---------- ---------- -------
sybase_dba dbo DATE_FORMAT SYSTEM TABLE NULL

In the above example, the DATE_FORMAT UDF is the one at Porting MySQL’s date_format function to Sybase ASE 15.0.2

I’ve opened a case with Sybase to get this fixed – I’ll post the CR # when I get it.

UPDATE:  Sybase assigned CR 497173 to this 🙂

Share Button

Duplicate rows in sysusers??

If you’re like me, you’ve run into lots of different issues with the Sybase ASE DBMS over the years. Today, Drew Montgomery looked at what happens when the 12.5.x -> 12.5.4 upgrade goes bad:

If you receive the 8419 error on sysusers after applying ASE 12.5.4 (or any other upgrade for that matter) such as the following:

01:00000:00472:2007/12/10 14:46:03.86 server Error: 8419, Severity: 20, State: 3
01:00000:00472:2007/12/10 14:46:03.86 server Could not find index descriptor for objid 10, indid 3 in dbid 13.
01:00000:00472:2007/12/10 14:46:03.88 kernel ************************************
01:00000:00472:2007/12/10 14:46:03.88 kernel SQL causing error : select * from sysusers
01:00000:00472:2007/12/10 14:46:03.88 kernel ************************************
01:00000:00472:2007/12/10 14:46:03.88 server SQL Text: select * from sysusers
01:00000:00472:2007/12/10 14:46:03.89 kernel curdb = 13 tempdb = 9 pstat = 0x10000
01:00000:00472:2007/12/10 14:46:03.89 kernel lasterror = 8419 preverror = 0 transtate = 1

Fear not because Drew has you covered with a simple script that will fix the problem. Note that it involves a dump and load of the affected database but you could just restart the ASE server if you don’t mind the down time:

sp_configure "allow updates", 1
go
use db_with_8419
go

select * into tempdb..temp_sysusers from sysusers
go

select uid, cnt= count(*) 
  into tempdb..temp_uid 
  from tempdb..temp_sysusers 
 group by uid 
 having count(*) > 1
go

select s.uid, s.suid
  into tempdb..temp_fixuid 
  from tempdb..temp_sysusers s, tempdb..temp_uid t
 where s.uid = t.uid
go

select uid, min(suid) suid
  into tempdb..temp_rmuid
  from tempdb..temp_fixuid
 group by uid
go

delete tempdb..temp_fixuid
  from tempdb..temp_fixuid f, tempdb..temp_rmuid r
 where f.uid = r.uid
   and f.suid = r.suid
go

alter table tempdb..temp_fixuid add cntr int identity
go

declare @max_uid int
select @max_uid = max(uid) 
  from tempdb..temp_sysusers
 where suid > 16300

update sysusers
   set uid = @max_uid + cntr
  from sysusers s, tempdb..temp_fixuid f
 where s.uid = f.uid
   and s.suid = f.suid
go

use master
go

dump database db_with_8419 to "compress::N::/DumpLocation/dumpfilename.dmp"
go
load database db_with_8419 from "compress::/DumpLocation/dumpfilename.dmp"
go
online database db_with_8419
go

sp_configure "allow updates", 0
go

Bau-jen Liu over at Sybase came up with the following method but it does require rebooting ASE twice:

sp_configure "allow updates", 1 
go 
update ..sysobjects 
set sysstat = 115, type = "U" 
where name = "sysusers" 
go 

Shutdown ASE, reboot, and log back in as a user with sa_role.

use dbname
go 

create unique index ncsysusers2 on sysusers(uid) 
go 

The above CREATE INDEX command may fail due to the presence of duplicate key rows in sysusers. If this occurs, recreate the index as non-unique first:

create index ncsysusers2 on sysusers(uid) 
go 

Now identify any duplicates that may exist in sysusers:

select uid, name, count(*) 
from sysusers 
group by uid 
having count(*) > 1 
go 

Remove any duplicates found using the DELETE command and try the CREATE INDEX again:

create unique index ncsysusers2 on sysusers(uid) 
go 

Now, clean up after yourself:

update ..sysobjects 
set sysstat = 113, type = "S" 
where name = "sysusers" 
go 

sp_configure "allow updates", 0 
go

Sybase has created bug # 298620 for this issue.

Share Button

Sybase Replication Server: Out of Mutexes? wtf?

For those of us that use Sybase’s Replication Server, we have long ago been pacified into believing that there really isn’t much that can be done with Replication Server’s quirks but to endure them.

In today’s edition of the Sybase RepServer Quirks we take a look at the “out of mutexes” error.  A mutex is an exclusive lock on a resource.  If you receive an error about RepServer running out of mutexes, you just don’t have enough defined through RepServer.  Simple huh?

Of course it is.  Ahh..  but then how do how many mutexes your particular Sybase RepServer needs?  How many grains of sand are on the moon?  According to Sybase you should know this already but since you can’t read minds (I hope you can’t because I’m thinking of donuts and not RepServer), I’ll pass on what Sybase is saying when pressed about it (Greg Carter @ Sybase):

> Just to elaborate a bit more on this question of the number of mutexes; as
> you probably know the mutex requirements for RepServer increased
> dramatically with the SMP feature. I have since struggled to come up with a
> formula for estimating mutex requirements so that you may properly set the
> “num_mutexes” configuration. While in the latest iteration of this formula
> I have satisfied myself that all mutexes have been accounted for, still the
> estimate it provides seems to fall short in some cases.
>
> Recent investigations by Connectivity seem to indicate that the problem may
> not be with sizing mutex requirements, but rather with sizing message queue
> (“num_msgqueues”) requirements. It appears that Open Server may be using
> the total of the settings for “num_mutexes” and “num_msgqueues” as the
> upper bound for the creation of these two objects together. So it may be
> that even though “num_mutexes” has been sized properly, if “num_msgqueues”
> is too low then you may see a message regarding the failure to create a
> mutex or the failure to create a message queue depending on which one was
> being created at the time that upper bound was surpassed.
>
> The moral here is that until Open Server resolves this issue you need to
> verify the sizing of both “num_mutexes” and “num_msgqueues” in the event
> that either error message appears since you can not rely on the message to
> indicate which one is low.
>
> For your convenience I’ll include here the latest formulas for estimating
> mutex and message queue requirements. Note that the one for mutexes may not
> agree completely with the one that is given in the 12.6 SMP White Paper – I
> have not compared them.
>
> Mutex requirements for the optimized binary:
> num_mutexes = 75 + Num(partitions) + 4*Num(DSI/S) + 3*Num(DSI/E) +
> 2*Num(Dist) + 2*Num(RepAgent Exec) + 2*Num(RSI User) + 5*Num(Queues) +
> 5*Num(SQT Cache) + Num(rs_subscriptions rows) + Num(RSSD tables) +
> Setting(cm_max_connections) +
> 2*MAX(Admin connections) + 2*Num(Other Connections) + Num(Origins) +
> 2*Num(Threads) + MAX(subscription (de)mat)
>
> Where
> – “Other Connections” are connection to this RepServer including ID Server
> connections, RSM connections, etc.
> – “Origins” are the different origins (or primary databases) that could
> possibly have transactions flowing through this RepServer, whether by a
> RepAgent or by a route (intermediate included)
> – “Threads” includes every thread RepServer may start. These are the
> “Global” thread, the “Initialization” thread, threads for each of the
> daemons (dAIO, dCM, dVersion, dRec, dSub, dStats, dAlarm), RepAgent User
> threads, SQM Writer threads, SQT threads, Distributor threads, DSI/S and
> DSI/E threads, RSI User and RSI threads.
> – “subscription (de)mat” is the number of asynchronous subscription
> management requests for materializing or dematerializing that may be taking
> place at any moment.
>
> Note: For the diagnostic binary you will need to double the figure
> determined with the above formula.
>
> Message queue requirements for the optimized and diagnostic binary:
> num_msgqueues = 10 + Num(DSI/S) + Num(DSI/E) + Num(Queues) + Num(Dist)
>
> Thanks,
> G.Carter

Neither this explanation or the two equations are anywhere in the manuals.  I’ve opened feature request 485482 for RepServer to handle this automagically as there really is NO NEED for a RepServer admin to have to worry about this.  If you are or ever have run into this problem, give Sybase a holler and tell them to fix this bug.

Share Button

HOWTO: Fix Sybase ASE: 17283 error when trying to extend a database segment

Did you ever receive the error 17283 “Procedure ‘sp_extendsegment’, Line 182 ‘tempdev1’ is reserved exclusively as a log device.” error? You can get the 17283 error when there is a device fragment that contains only the log segment. Part of the problem is when you extend the log segment onto a device, it will usually drop all other segments so it becomes ‘log only’.

 device_fragments               size          usage                created             free kbytes
 ------------------------------ ------------- -------------------- ------------------- ----------------
 master                                8.0 MB data and log         Dec 16 2004  4:09AM             3376
 tempdev1                           1024.0 MB data and log         Dec 16 2004  7:02AM          1044480
 tempdev1                            256.0 MB data and log         Mar  9 2005 10:49AM           261120
 tempdev1                            256.0 MB log only             Mar  9 2005 10:54AM not applicable
 tempdev1                            488.0 MB data and log         Mar  9 2005 12:10PM           497760
 tempdev1                            256.0 MB data and log         Mar 11 2005  2:03PM           261120
 tempdev1                            244.0 MB data and log         Mar 11 2005  3:09PM           248880
 tempdev1                            200.0 MB data and log         Jun  1 2005 12:33PM           204000
 tempdev1                            200.0 MB data and log         Jul  8 2005  2:55PM           203808
 tempdev1                            200.0 MB data and log         Jul 21 2005  2:54PM           204000
 tempdev1                           1000.0 MB data and log         Feb  6 2006  1:11PM          1020000

So, how to fix this? Well, Sybase doesn’t provide any way to do so without modifying the system tables.

use master
exec sp_configure "allow updates", 1
go
begin tran
go

since we are dealing with tempdb and we want data and log on all the device fragments, we can make a blanket update. We would make the update more selective if we had other requirements (update only one row or something)

update sysusages set segmap = 7 where dbid = db_id("tempdb")

if the number of rows updated exceed the number of rows for the database, issue a ‘rollback’

select segmap from sysusages where dbid = db_id("tempdb")

all good? if so, issue a ‘commit’

commit tran
go
exec sp_configure "allow updates", 0
go

Now that the system table is updated, we need to refresh the dbtable memory structure so that the changes we made become ‘live’

dbcc dbrepair(tempdb, remap)
go

That’s it! It’s fixed and running with the segmaps without having to restart ASE. Wasn’t that easy?

Share Button

Sybase’s setup causes some installs of ASE to fail

ASE 12.5.4 setup (java version of Installshield) unsets LD_POINTER_GUARD, which will cause some linux distributions to fail to ‘setup’ dataserver.

This appears to be a variation of the issue raised in the "Sybase’s Backup Server for Linux (64bit) is broken 🙁" post.  What is unclear is whether this variable is being undefined by the Sybase supplied Java, Installshield itself or whether Sybase engineering is explicitly undefining it in the Installshield script.  I’ve opened a case with Sybase to ensure that this gets resolved with the ASE 12.5.4 esd 6 ebf.

cat srvbuild0127.001
Sat Jan 27 20:37:05 2007: srvbuild/12.5.4/P/Linux Intel/Linux 2.4.18-18.7.xsmp i686/EBF 13388/OPT/Tue May  9 08:38:07 PDT 2006
Sat Jan 27 20:37:05 2007: Getting attribute values from sybinit resource file `/database/sybase/ASE-12_5/sqlsrv.res’.
Sat Jan 27 20:37:05 2007:
Sat Jan 27 20:37:05 2007:
Sat Jan 27 20:37:05 2007: Warning: Unable to verify /database/sybase/data/sybsystemprocs.raw device size.  Please verify that this device is not already in use and that it has sufficient space available.
type = 1
server_page_size = 2k
master_device_physical_name = /database/sybase/master.raw
master_device_size = 100
master_database_size = 50
sybsystemprocs_device_physical_name = /database/sybase/data/sybsystemprocs.raw
sybsystemprocs_device_size = 300
sybsystemprocs_database_size = 300
errorlog = /database/sybase/ASE-12_5/install/JASONDESKTOP.log
configfile = /database/sybase/ASE-12_5/JASONDESKTOP.cfg
sybsystemdb_device_physical_name = /database/sybase/data/sybsysdb.dat
sybsystemdb_device_size = 1
sybsystemdb_database_size = 1
shmem = /database/sybase/ASE-12_5
default_backup_server = JASONDESKTOP_BS
server_name = JASONDESKTOP
force_buildmaster = yes
Sat Jan 27 20:37:05 2007: (Shell command) /database/sybase/ASE-12_5/bin/dataserver -d/database/sybase/master.raw -b100M -z2k -sJASONDESKTOP -e/database/sybase/ASE-12_5/install/JASONDESKTOP.log -T1623 -f > /tmp/sbNXsSD5 2>&1
dataserver: master device size for this server: 100.0 Mb
dataserver: master database size for this server: 6.0 Mb
dataserver: model database size for this server: 2.0 Mb
00:00000:00000:2007/01/27 20:37:05.95 kernel  Checked out license ASE_DEV
00:00000:00000:2007/01/27 20:37:05.96 kernel  Adaptive Server Enterprise Developer Edition.
00:00000:00000:2007/01/27 20:37:06.05 kernel  Using config area from primary master device.
00:00000:00000:2007/01/27 20:37:06.05 server  Configuration Error: Configuration file, ‘/database/sybase/JASONDESKTOP.cfg’, does not exist.
00:00000:00000:2007/01/27 20:37:06.05 kernel  Warning: A configuration file was not specified and the default file ‘/database/sybase/JASONDESKTOP.cfg’ does not exist. SQL Server creates the default file with the default configuration.
00:00000:00000:2007/01/27 20:37:06.06 kernel  Warning: Using default file ‘/database/sybase/JASONDESKTOP.cfg’ since a configuration file was not specified. Specify a configuration file name in the RUNSERVER file to avoid this message.
00:00000:00000:2007/01/27 20:37:06.08 kernel  os_find_good_keyfile: Found shared memory segment: key 0x6e0300b8, id 121044995
00:00000:00000:2007/01/27 20:37:06.08 kernel  os_find_good_keyfile: If SQL Server using it is not running, remove it by hand
00:00000:00000:2007/01/27 20:37:06.08 kernel  os_find_good_keyfile: Trying a different key
00:00000:00000:2007/01/27 20:37:06.08 kernel  Internal run-time model set for Linux  – Native
00:00000:00000:2007/01/27 20:37:06.08 kernel  Using 1024 file descriptors.
00:00000:00000:2007/01/27 20:37:06.08 kernel  Adaptive Server Enterprise/12.5.4/EBF 13388/P/Linux Intel/Enterprise Linux/ase1254/2006/32-bit/OPT/Fri May 19 23:17:01 2006
00:00000:00000:2007/01/27 20:37:06.08 kernel  Confidential property of Sybase, Inc.
00:00000:00000:2007/01/27 20:37:06.08 kernel  Copyright 1987, 2006
00:00000:00000:2007/01/27 20:37:06.08 kernel  Sybase, Inc.  All rights reserved.
00:00000:00000:2007/01/27 20:37:06.08 kernel  Unpublished rights reserved under U.S. copyright laws.
00:00000:00000:2007/01/27 20:37:06.08 kernel
00:00000:00000:2007/01/27 20:37:06.08 kernel  This software contains confidential and trade secret information of Sybase,
00:00000:00000:2007/01/27 20:37:06.08 kernel  Inc.   Use,  duplication or disclosure of the software and documentation by
00:00000:00000:2007/01/27 20:37:06.08 kernel  the  U.S.  Government  is  subject  to  restrictions set forth in a license
00:00000:00000:2007/01/27 20:37:06.08 kernel  agreement  between  the  Government  and  Sybase,  Inc.  or  other  written
00:00000:00000:2007/01/27 20:37:06.08 kernel  agreement  specifying  the  Government’s rights to use the software and any
00:00000:00000:2007/01/27 20:37:06.08 kernel  applicable FAR provisions, for example, FAR 52.227-19.
00:00000:00000:2007/01/27 20:37:06.08 kernel  Sybase, Inc. One Sybase Drive, Dublin, CA 94568, USA
00:00000:00000:2007/01/27 20:37:06.08 kernel  ASE booted on Linux release 2.6.17-10-generic version #2 SMP Tue Dec 5 22:28:26 UTC 2006.
00:00000:00000:2007/01/27 20:37:06.08 kernel  Using ‘/database/sybase/JASONDESKTOP.cfg’ for configuration information.
00:00000:00000:2007/01/27 20:37:06.08 kernel  Logging ASE messages in file ‘/database/sybase/ASE-12_5/install/JASONDESKTOP.log’.
00:00000:00000:2007/01/27 20:37:06.12 kernel  SQL Server booted with TCP_NODELAY enabled.
00:00000:00000:2007/01/27 20:37:06.12 kernel  SSL Plus v3.1.14 security modules loaded successfully.
00:00000:00000:2007/01/27 20:37:06.12 kernel  Network and device connection limit is 1009.
00:00000:00000:2007/01/27 20:37:06.29 server  Number of blocks left for proc headers: 3232.
00:00000:00000:2007/01/27 20:37:06.29 server  Proc header memory allocated 1616 pages for each per engine cache
00:00000:00000:2007/01/27 20:37:06.32 server  Size of the 2K memory pool: 8192 Kb
00:00000:00000:2007/01/27 20:37:06.32 server  Memory allocated for the default data cache cachelet 1: 8192 Kb
00:00000:00000:2007/01/27 20:37:06.32 kernel  Enabling Linux Kernel asynchronous disk I/O strategy.
00:00000:00000:2007/01/27 20:37:06.32 kernel  Initializing virtual device 0, ‘/database/sybase/master.raw’ with dsync ‘off’.
00:00000:00000:2007/01/27 20:37:06.32 kernel  Virtual device 0 started using asynchronous i/o.
00:00000:00000:2007/01/27 20:37:06.32 kernel  Worker Thread Manager is not enabled for use in SQL Server.
00:00000:00000:2007/01/27 20:37:06.33 kernel  Either the config parameter ‘use security services’ is set to 0, or ASE does not support use of external security mechanisms on this platform. The Security Control Layer will not be initialized. No external security mechanisms will be supported.
00:00000:00000:2007/01/27 20:37:06.33 kernel  Unix interval timer enabled for sysclk interrupts.
00:00000:00000:2007/01/27 20:37:06.38 kernel  engine 0, os pid 8048  online
Segmentation fault
Sat Jan 27 20:37:06 2007: Buildmaster return code: -117.
Sat Jan 27 20:37:06 2007:
Share Button

ASE 12.5.x (64bit) and ASE 15 fail to start using GLIBC

If you are going to be using ASE 12.5 or ASE 15 with the upcoming Red Hat Enterprise Linux 5.0, there are two CRs that you need to know about:

  1. CR 450004 – XP Server and Backupserver (64bit)
  2. CR 432482 – ASE 15

The problem is the result of using the jmp() and longjmp() functions in the GNU C Library version 2.4 (glibc 2.4).

setjmp() and longjmp() are useful for dealing with errors and interrupts encountered in a low-level subroutine of a program. setjmp() saves the stack context/environment in env for later use by longjmp(). The stack context will be invalidated if the function which called setjmp() returns.

Starting in glibc 2.4, the jmpbuf is unavailable due to a security exploit known for several years.  Restricting access to the jmpbuf was an effort by the glibc maintainers to ‘close this hole’ by forcing the application writers to use the sigsetjmp() and siglongjmp() instead.

The problem with using sigsetjmp() and siglongjmp() is that they aren’t thread safe.  This is supposed to be fixed in glibc 2.6 according to a contact at Sybase but Sybase *does* have a workaround for this issue and will be putting it into the ASE v15 codeline when they perform the RHEL 5 certification sometime next year.

I wasn’t able to find much information the supposed exploit.  I only found a few newsgroup posts that didn’t provide any details.

Continue reading “ASE 12.5.x (64bit) and ASE 15 fail to start using GLIBC”

Share Button