Bug #45676 falcon_ddl fails due to missing tables after recovery
Submitted: 23 Jun 2009 12:34 Modified: 26 May 2010 17:53
Reporter: Olav Sandstå Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Server: Falcon storage engine Severity:S2 (Serious)
Version:6.0.12-alpha OS:Linux
Assigned to: Christopher Powers CPU Architecture:Any
Tags: F_RECOVERY

[23 Jun 2009 12:34] Olav Sandstå
Description:
falcon_ddl fails on some platforms with an error message similar to this when doing validation of the database after a "successful" recovery:

# 19:14:30 Verifying table: m; database: x
# 19:14:30 7: TransID=781  CommitNoUpdates  (null)
# 19:14:30 090622 19:14:30 [ERROR] Server is attempting to access a table ./x/m#P#s,
# 19:14:30 which doesn't exist in Falcon.
DBD::mysql::st execute failed: Table 'x.m' doesn't exist at lib/GenTest/Reporter/Recovery.pm line 171, <RDRFH> line 318.
DBD::mysql::st fetchrow_hashref failed: fetch() without execute() at lib/GenTest/Reporter/Recovery.pm line 175, <RDRFH> line 318.
# 19:14:30 090622 19:14:30 [ERROR] Server is attempting to access a table ./x/m#P#s,
# 19:14:30 which doesn't exist in Falcon.
DBD::mysql::st execute failed: Table 'x.m' doesn't exist at lib/GenTest/Reporter/Recovery.pm line 207, <RDRFH> line 318.
# 19:14:30 Failing query is SELECT * FROM `x`.`m` /* no extra predicate */.

How to repeat:
Seen multiple times after running falcon_ddl test.