Bug #22255 Using of AWE option for mysql server on Windows cause problem with frm files

• Submitted: 12 Sep 2006 0:49
• Modified: 12 Sep 2006 9:17
• Reporter: Alexey Stroganov
• Status: Won't fix
• Category: MySQL Server: InnoDB storage engine
• Severity: S3 (Non-critical)
• Version: 5.0.24a
• OS: Windows (Windows 2003)
• Assigned to: Heikki Tuuri
• CPU Architecture: Any

[12 Sep 2006 0:49] Alexey Stroganov

Description:
According to our manual (http://dev.mysql.com/doc/refman/5.0/en/innodb-parameters.html) enabling of AWE feature only possible for custom built binaries that should be rebuilt with __WIN2000_ define. But if one will try to use this option on regular binary he will get problem with accessing his innodb tables with following error:

Incorrect information in file: ...

Started server as usual. Table is ok. 

mysql> show table status\G
*************************** 1. row ***************************
           Name: t1
         Engine: InnoDB
        Version: 10
     Row_format: Compact
           Rows: 3
 Avg_row_length: 5461
    Data_length: 16384
Max_data_length: 0
   Index_length: 0
      Data_free: 0
 Auto_increment: NULL
    Create_time: 2006-09-11 21:10:46
    Update_time: NULL
     Check_time: NULL
      Collation: latin1_swedish_ci
       Checksum: NULL
 Create_options:
        Comment: InnoDB free: 4096 kB
1 row in set (0.00 sec)

Restarted server with innodb_additional_mem_pool_size option

mysql> show table status\G
*************************** 1. row ***************************
           Name: t1
         Engine: NULL
        Version: NULL
     Row_format: NULL
           Rows: NULL
 Avg_row_length: NULL
    Data_length: NULL
Max_data_length: NULL
   Index_length: NULL
      Data_free: NULL
 Auto_increment: NULL
    Create_time: NULL
    Update_time: NULL
     Check_time: NULL
      Collation: NULL
       Checksum: NULL
 Create_options: NULL
        Comment: Incorrect information in file: '.\test\t1.frm'
1 row in set (0.00 sec)

There are following messages in the error log:
...
InnoDB: Error: You have specified innodb_buffer_pool_awe_mem_mb
InnoDB: in my.cnf, but AWE can only be used in Windows 2000 and later.
InnoDB: To use AWE, InnoDB must be compiled with __WIN2000__ defined.
060910  2:39:27 [Note] e:\mysql-5.0.24a-win32\bin\mysqld.exe: ready for connections.
Version: '5.0.24a-community'  socket: ''  port: 3306  MySQL Community Edition (GPL)
060910  2:39:35 [ERROR] e:\mysql-5.0.24a-win32\bin\mysqld.exe: Incorrect information in file: '.\test\t1.frm'

I found possible related issue in our bug db: http://bugs.mysql.com/bug.php?id=6581

How to repeat:
Start MySQL server on Windows platfrom with --innodb_additional_mem_pool_size=<any value> and try to access innodb table.

[12 Sep 2006 1:19] Alexey Stroganov

Cut&paste problem in the report above - of course I meant innodb_buffer_pool_awe_mem_mb instead of innodb_additional_mem_pool_size.

[12 Sep 2006 9:17] Heikki Tuuri

This is very low priority since AWE is becoming obsolete rapidly. I put this to the Won't fix state.