Bug #26219 Unable to install MySQL 4.1.19 - 4.1.22 and 5.0.34 on AIX 5.2 32-bit system
Submitted: 9 Feb 2007 12:01 Modified: 14 Jul 2007 13:06
Reporter: Tero Yliharsila Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Installing Severity:S2 (Serious)
Version:4.1.19, 5.0.34 OS:IBM AIX (AIX 5.2 32-bit)
Assigned to: CPU Architecture:Any
Tags: AIX, regression

[9 Feb 2007 12:01] Tero Yliharsila
Description:
Unable to install MySQL 4.1.19-pro, 4.1.20-pro, 4.1.21-pro, 4.1.22-pro and 5.0.34-enterprise versions on AIX 5.2 32-bit system.
MySQL version 4.1.18-pro can be installed.
The database engine we use is InnoDB.
When "mysql_install_db --user=mysql" is executed, I get the following error message:
Installing all prepared tables
exec(): 0509-036 Cannot load program ./bin/mysqld because of the following
                 errors:
        0509-130 Symbol resolution failed for mysqld because:
        0509-136 Symbol mkstemp64 (number 137) is not exported from 
                 dependent module /usr/lib/libc.a(shr.o).
        0509-192 Examine .loader section symbols with the 
                 'dump -Tv' command.
Installation of system tables failed!

How to repeat:
mysql_install_db --user=mysql
[9 Feb 2007 12:57] Valeriy Kravchuk
Thank you for a problem report. Looks like you are trying to use 64-bit binaries on 32-bit platfrom. Please, send exact file names (or URLs used to download) for the binaries you tried to install.
[12 Feb 2007 6:27] Tero Yliharsila
mysql-pro-4.1.19-ibm-aix5.2.0.0-powerpc.tar.gz,
mysql-pro-4.1.20-ibm-aix5.2.0.0-powerpc.tar.gz,
mysql-pro-4.1.21-ibm-aix5.2.0.0-powerpc.tar.gz,
mysql-pro-4.1.22-ibm-aix5.2.0.0-powerpc.tar.gz,
mysql-enterprise-5.0.34-aix5.2-powerpc.tar.gz
[12 Mar 2007 10:55] Valeriy Kravchuk
Please, try to repeat with latest 5.0.36/5.0.37 binaries and inform about the results.
[22 Mar 2007 2:11] myeros myeros
# scripts/mysql_install_db --user=mysql &
[1]     22404
# Installing all prepared tables
exec(): 0509-036 由于下列错误,不能装入程序 mysqld:
        0509-130 mysqld 的符号解析失败,原因是:
        0509-136   符号 mkstemp64 (编号 130) 没有从
                   从属模块 /usr/lib/threads/libc.a[shr_64.o] 导出。
        0509-192 请使用 'dump -Tv' 命令检查 .loader 节符号。
Installation of system tables failed!

Examine the logs in ./data for more information.
You can also try to start the mysqld daemon with:
./bin/mysqld --skip-grant &
You can use the command line tool
./bin/mysql to connect to the mysql
database and look at the grant tables:

shell> ./bin/mysql -u root mysql
mysql> show tables

Try 'mysqld --help' if you have problems with paths. Using --log
gives you a log in ./data that may be helpful.

The latest information about MySQL is available on the web at
http://www.mysql.com
Please consult the MySQL manual section: 'Problems running mysql_install_db',
and the manual section that describes problems on your OS.
Another information source is the MySQL email archive.
Please check all of the above before mailing us!
And if you do mail us, you MUST use the ./bin/mysqlbug script!

[1] +  完成(1)                   scripts/mysql_install_db --user=mysql &

it's result for aix5.2 install mysql5.0.37
[14 Jun 2007 13:00] Daniel Fischer
Just a comment: mkstemp64 is not related to 64-bit libraries, it is a variant of mkstemp that can work with large files. It should be present on AIX 5.2.
[14 Jun 2007 13:06] Valeriy Kravchuk
These symbols are needed for "large file" support on AIX, even 32-bit. You should have them. On our AIX 5.2 box we have:

bash-2.05a$ nm /usr/lib/libc.a | grep mkstemp64
.mkstemp64           T     1155140
mkstemp64            D      277888          12
bash-2.05a$ uname -a
AIX aix52 2 5 00592F0F4C00
bash-2.05a$ oslevel -r
5200-01

So, please, send the results of commands listed above from your box. As for 4.1.18, maybe "large files" support was just not enabled (by mistake!) in that version.
[14 Jul 2007 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".