| Bug #25087 | MaxDB broken on Ubuntu 6.10 | ||
|---|---|---|---|
| Submitted: | 15 Dec 2006 8:36 | Modified: | 7 Jan 2008 11:07 |
| Reporter: | Kristian Rink | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MaxDB | Severity: | S1 (Critical) |
| Version: | 7.x | OS: | Linux (Ubuntu Linux 6.10) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | error, rte, server | ||
[15 Dec 2006 8:37]
Kristian Rink
log files of 7.6 atop Ubuntu 6.10
Attachment: knldiag.gz (application/force-download, text), 9.49 KiB.
[19 May 2007 17:17]
Ivan Vaklinov
Same problem on Debian 4.0 Stable ;-( vaklinov:/opt/sdb/programs/bin# ./dbmcli db_create -auto IVDB623 sdb,seeburger OK vaklinov:/opt/sdb/programs/bin# ./dbmcli -d IVDB623 -u sdb,seeburger -i ~ivan/installs/MaxDB/create_instance_ascii_623.txt >param_startsession OK --- >param_init OLTP OK --- >param_put SESSION_TIMEOUT 900 OK --- >param_put MAXUSERTASKS 500 OK --- >param_put _UNICODE NO OK --- >param_put DEFAULT_CODE ASCII OK --- >param_put CACHE_SIZE 50000 OK --- >param_put CAT_CACHE_SUPPLY 4000 OK --- >param_put SHAREDSQL YES OK --- >param_put SHAREDSQL_COMMANDCACHESIZE 120000 OK --- >param_checkall OK --- >param_commitsession OK --- >param_addvolume 1 LOG LOG_001 F 10000 OK --- >param_addvolume 1 DATA DAT_001 F 40000 OK --- >db_admin ERR -24994,ERR_RTE: Runtime environment error 1,Check knldiag! Kernel died before reaching ADMIN state (OS error code 11000)
[15 Aug 2007 21:03]
António Nunes
The same happened on an HP-UX 11.23 64 bits where I am trying to install MAXDB 7.6 build 29 (the same happens with the more recent build 35). So, perhaps the problem you have with the died kernel on UBUNTU Linux is not specific of it (I've found the same error description for Windowsw and SunSe in some foruns going on the net). Regards
[11 Sep 2007 15:47]
Burkhard Diesing
Hello António, I think it is not the same prroblem because. In Kristians case the was a shared library not found. For Ivan problem I need the knldiag fiel to see whats happen. Did your kernel died with: "-24994,ERR_RTE: Runtime environment error 1,Check knldiag! Kernel died before reaching ADMIN state (OS error code 11000)" Please upload the knldiag file from your rundirectory. Regards, Burkhard
[7 Jan 2008 11:07]
Ulf Wendel
Thank you for a problem report. According to http://www.mysql.com/news-and-events/press-release/release_2007_40.html MaxDB has been given back to SAP. If you have purchased MaxDB support from MySQL, please report the issue at the MySQL Customer Support Center on http://support.mysql.com. If you are an open source community member, please report your issue at SAP on http://www.sdn.sap.com/irj/sdn/maxdb .
Description: Currently there seems to be no way whatsoever of getting binary builds of MaxDB to run atop Ubuntu 6.10. * MaxDB 7.5.00.38 fails here while creating a new database instance: [...] ERR -24994,ERR_RTE: runtime environment error 1,Check knldiag! Kernel died before reaching ADMIN state [...] - afterwards, data/wrk/<DBINSTANCE>/ is completely empty, no log files to report. * MaxDB 7.6.00.34 fails with an error similar to that one, also while trying to switch a newly created database to ADMIN or ONLINE: [...] ERR -24994,ERR_RTE: Runtime environment error 1,Check knldiag! Kernel died before reaching ADMIN state (OS error code 11000) [...] In this case, some files are created in data/wrk/<DBINSTANCE>/ but none of the log files does provide any sort of error message. * As for MaxDB 7.5.*, I _think_ I have found one reason why it doesn't work here: - 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 How to repeat: - Install any version of MaxDB 7.x (7.5.00.38, 7.6.00.34) atop a plain Ubuntu 6.10 system. - Create an empty database instance. - Try to initialize this instance using a prepared installation script and observe it entering ADMIN / ONLINE state.