Bug #48196 Got error 134 when reading table(ENGINE=MEMORY)
Submitted: 21 Oct 2009 3:47 Modified: 21 Nov 2009 16:10
Reporter: zhou li Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Memory storage engine Severity:S3 (Non-critical)
Version:5.0.84 OS:Linux (SUSE SLES10.2)
Assigned to: CPU Architecture:Any

[21 Oct 2009 3:47] zhou li
Description:
when I  run the follwing SQL,sometime I  get "ERROR 1030 (HY000): Got error 134 from storage engine" ,and mysql error log "Got error 134 when reading table './toltech/UserOnline'".

update ClientIMInfo set status = 0   where userID not in (select userID from UserOnline);

Note:
ClientIMInfo storage engine is MyISAM
UserOnline  storage engine is MEMORY

How to repeat:
CREATE TABLE `UserOnline` (
  `userID` int(11) NOT NULL    ,
  `loginName` varchar(30) default NULL    ,
  `IMId` varchar(50) default NULL   ,
  `gender` smallint(6) default NULL    ,
 
  `nickName` varchar(30) default NULL   ,
  `imageID` varchar(40) default NULL    ,
 
  `onlineStatus` int(11) default NULL    ,
  `checkTime` bigint(20) default NULL    ,
 
  `deviceID` varchar(32) default NULL    ,
  PRIMARY KEY  (`userID`),
  KEY `nickName` (`nickName`)
) ENGINE=MEMORY DEFAULT CHARSET=utf8 ;

CREATE TABLE `ClientIMInfo` (                                                                                             
                `id` int(11) NOT NULL auto_increment  ,                                                               
                `userIMId` varchar(50) NOT NULL  ,                                                               
                `userIMPwd` varchar(50) NOT NULL  ,                                                          
                `userID` int(11) default NULL  ,                                
                `msgDigest` char(32) default NULL  ,  
                `status` smallint(6) default '0'  ,                                                 
                `creationDate` datetime default NULL  ,                                                            
                `updateTime` timestamp NOT NULL default CURRENT_TIMESTAMP  ,                                 
                PRIMARY KEY  (`id`),                                                                                                    
                UNIQUE KEY `userIMId` (`userIMId`),                                                                                     
                KEY `idx_msgDigest` (`msgDigest`),                                                                                      
                KEY `idx_userID` (`userID`)                                                                                       
              ) ENGINE=MyISAM DEFAULT CHARSET=utf8   ;

when I got error,UserOnline have few row data.
[21 Oct 2009 7:27] Valeriy Kravchuk
Thank you for the problem report. Please, upload a dump of data that demonstrates this problem.
[21 Oct 2009 8:39] zhou li
dump file

Attachment: toltech.sql (application/download, text), 4.19 KiB.

[21 Oct 2009 8:51] zhou li
Actually I don't know how to repeat this error.My client system do insert/update/delete data to table UserOnlie ,and the sql run well.The error will not come out every time when i run "update ClientIMInfo set status = 0   where userID not in (select userID from UserOnline);
"
[21 Oct 2009 10:17] Miguel Solorzano
I couldn't repeat on Ububtu 9.10 64-bit with current source server.
[21 Oct 2009 16:10] Valeriy Kravchuk
Please, check if this is repeatable with a newer version, 5.0.86. Also, please, check the logs at OS level (/var/log/messages etc) for any suspicious messages at the time of these errors 134.
[22 Nov 2009 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".