Bug #34865 Backup with table name 'policy" failed
Submitted: 26 Feb 2008 22:14 Modified: 2 May 2008 10:08
Reporter: mike avergun Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S1 (Critical)
Version:5.0.27 OS:Any
Assigned to: CPU Architecture:Any

[26 Feb 2008 22:14] mike avergun 
Description:
There is a mystery to the specific table name "policy". At different times system refuses to work with it. I had similar bug that developers doomed "not a bug" but it doesn't make work.
This time I manage to create database with this table and worked on. Made a back up that I can successfully restore on this server, but when I take back up to the different server it fails out of blue on the same table with error:

Error while executing this query:CREATE TABLE `policy` (
  `policy_id` int(10) unsigned NOT NULL auto_increment,
  `policy_definition_id` int(10) unsigned NOT NULL,
  `policy_description_id` int(10) unsigned NOT NULL,
  `policy_subject` varchar(255) default NULL,
  `value_policy_type` varchar(45) NOT NULL,
  PRIMARY KEY  (`policy_id`),
  UNIQUE KEY `Index_2` (`policy_definition_id`,`policy_description_id`,`policy_subject`,`value_policy_type`)
) ENGINE=InnoDB AUTO_INCREMENT=4011 DEFAULT CHARSET=latin1;
The server has returned this error message:Can't create table './soemon3/policy.frm' (errno: 150)
MySQL Error.

How to repeat:
I am including backup of the database. 
From MySQL Administrator restore database
Observe error
[27 Feb 2008 12:47] MySQL Verification Team 
Thank you for the bug report. Could you please try with latest released
version and if the issue still exists, please provide the backup file.
Thanks in advance.
[28 Mar 2008 0: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".
[2 Apr 2008 10:08] Susanne Ebrecht 
Mike,

we still need to know if you will get this issues by using our newest version: MySQL 5.0.51a.
[2 May 2008 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".