For what I have found out so far, MaxDB 7.5.00.* (same as 7.6.00.*) do
per default rely upon LD_ASSUME_KERNEL in order to avoid some threading
related issues (feel free to use the MaxDB mailing list archive or read
here - http://www.mysqltalk.org/sap-db-not-working-on-redhat-phoebe-the-
solution-vt71534.html - to see a few hints on that).
Basically, it boils down to the following, comparing Dapper (where it
works) and Edgy (where it doesn't work). Used stock installations in
both cases, and the error is the same no matter whether using MaxDB
7.5.00 or 7.6.00:
- box #1 (Ubuntu 6.06):
#> LD_ASSUME_KERNEL=2.4.1 x_server update
12916 XSERVER Found other running x_server with version 'X32/LINUX
7.5.0 Build 038-121-133-420'
12926 XSERVER Version after update 'X32/LINUX 7.5.0 Build
038-121-133-420'
- box #2 (Ubuntu 6.10):
#> LD_ASSUME_KERNEL=2.4.1 x_server status
x_server: error while loading shared libraries: libdl.so.2: cannot open
shared object file: No such file or directory
LD_ASSUME_KERNEL=2.4.something seems to be used by default in pre-built
MaxDB packages found at the MaxDB download site, so it is not working so
far. Unfortunately, with MaxDB in Ubuntu-universe being broken because
of unmet dependencies, there is no MaxDB on Edgy at the moment. :/
Cheers,
Kristian
--
Database instance restart error
https://launchpad.net/bugs/53333
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
