MySQL Bugs: #10476: ERROR 1032 (HY000): Can't find record in ''

Bug #10476	ERROR 1032 (HY000): Can't find record in ''
Submitted:	9 May 2005 14:05	Modified:	27 Jul 2005 18:07
Reporter:	Steve Cersosimo	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	4.1.11	OS:	Solaris (Solaris 2.8)
Assigned to:		CPU Architecture:	Any

Description:
I am getting this error (ERROR 1032 (HY000): Can't find record in '') when performing the following query. It worked in previous versions (specifically 3.23) on the same data in the same table structure.

select User_Name,count(*) as count
from 05_08_05
where concat(Record_Date,' ',Record_Time) > date_sub(now(),interval 60 minute)
group by User_Name
order by count desc
limit 10;

This is a relatively large table 8,274,677 rows. I can provide more details if needed (table & index description, etc.).

Any help would be appreciated.

Current version: mysql-standard-4.1.11-sun-solaris2.8-sparc

Thank you,
Steve Cersosimo

How to repeat:
Perform the above query

Suggested fix:
Unknown

Steve,

please provide what SHOW CREATE TABLE says.

With what mysqld version did you create the table?

Note the upgrade instructions for 4.1 at
http://dev.mysql.com/doc/mysql/en/upgrading-from-4-0.html

If this an InnoDB table where the primary key contains an ENUM, then this might also be a bug fixed in upcoming 4.1.12.

Regards,

Heikki

This is a MyISAM table.  It was created using MySQL 4.1.11.  I create a new table every day to store daily data.  The tables are named MM_DD_YY.  The problem exists for every table including today's table 05_09_05.  Each daily table gets about 17 million rows of data.

show create table 05_08_05;
  05_08_05 |CREATE TABLE `05_08_05` (
  `Radius_Server` varchar(50) NOT NULL default '',
  `Record_Date` date NOT NULL default '0000-00-00',
  `Record_Time` time NOT NULL default '00:00:00',
  `RAS_Client` varchar(15) default NULL,
  `Record_Type` varchar(5) NOT NULL default '',
  `Full_Name` varchar(255) default NULL,
  `Auth_Type` smallint(5) unsigned default NULL,
  `NAS_IP_Address` varchar(15) NOT NULL default '',
  `NAS_Identifier` varchar(30) default NULL,
  `NAS_Port` varchar(15) default NULL,
  `RB_NAS_Real_Port` varchar(15) default NULL,
  `NAS_Port_Type` varchar(30) default NULL,
  `User_Name` varchar(255) NOT NULL default '',
  `Called_Station_ID` varchar(30) default NULL,
  `Calling_Station_ID` varchar(30) default NULL,
  `Acct_Status_Type` smallint(5) unsigned default NULL,
  `Service_Type` smallint(5) unsigned default NULL,
  `Acct_Session_Id` varchar(20) NOT NULL default '',
  `Acct_Link_Count` varchar(5) default NULL,
  `Acct_Multi_Session_Id` varchar(30) default NULL,
  `Framed_Protocol` smallint(5) unsigned default NULL,
  `Framed_IP_Address` varchar(15) NOT NULL default '',
  `Acct_Termination_Cause` varchar(30) default NULL,
  `Acct_Input_Octets` varchar(16) default NULL,
  `Acct_Output_Octets` varchar(16) default NULL,
  `RB_Acct_Input_Octets_64` varchar(16) default NULL,
  `RB_Acct_Output_Octets_64` varchar(16) default NULL,
  `Acct_Session_Time` varchar(16) default NULL,
  `Class` varchar(50) default NULL,
  PRIMARY KEY  (`Record_Date`,`Record_Time`,`User_Name`,`Record_Type`,`Acct_Session_Id`,`Radius_Server`),
  KEY `UserName` (`User_Name`),
  KEY `RecordType` (`Record_Type`),
  KEY `Session` (`Acct_Session_Id`),
  KEY `IP` (`Framed_IP_Address`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1

Steve,

thank you. Looks like it is a bug in the MySQL interpreter.

Can you anonymous ftp the table to

support.mysql.com

to directory

/pub/mysql/secret
?

We can try repeating the problem here.

Regards,

Heikki

I can upload the .frm, .MYD and .MYI files, but that is already over 1.5 GB of data.  I can upload a compressed zip file if you prefer.

Steve,

please upload a .zip or .gz file.

--Heikki

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".

reopened

This looks like the same issue as of bug #9703.

The bug is fixed in 4.1.12.

Hi Steve,

Thank you for your bug report!  This bug is a duplicate of 9703.  A fix
for the bug was included in 4.1.12.

Best Regards