MySQL Bugs: #77968: In TIME type values like "10:98:72", are getting inserted

Bug #77968	In TIME type values like "10:98:72", are getting inserted
Submitted:	6 Aug 2015 21:59	Modified:	17 Aug 2015 11:10
Reporter:	jafar husain	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: Data Types	Severity:	S1 (Critical)
Version:	5.0.15 Standard Log	OS:	Linux
Assigned to:		CPU Architecture:	Any
Tags:	Minutes are out of Range, SECONDS

Description:
In TIME type values like "10:98:72", "11:98:72", are getting inserted, Not in a particular server, but we found it for different rows in the Master and Multiple Slaves.

We cannot insert them manually, if we try, values will get truncated to "00:00:00", with a warning.

Manual updation is working fine on the same records also. In the binary log, correct values are present for the same record.

Table check is fine. No error found in the error log.

Kindly help.

How to repeat:
Not able to repeat is manually.

We cannot insert them manually, if we try, values will get truncated to "00:00:00", with a warning.

Table Structure from Dump, with Data:

-- MySQL dump 10.10
--
-- Host: localhost    Database: property
-- ------------------------------------------------------
-- Server version       5.0.15-standard-log

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;

--
-- Table structure for table `property_details`
--

DROP TABLE IF EXISTS `property_details`;
CREATE TABLE `property_details` (
  `ctyhocn` varchar(7) NOT NULL default '',
  `name` varchar(75) default NULL,
  `description` text,
  `city` varchar(21) default NULL,
  `prime_city` varchar(40) default NULL,
  `country_code` varchar(5) default NULL,
  `state_code` char(3) default NULL,
  `brand_id` char(2) default NULL,
  `address` varchar(35) default NULL,
  `zip` varchar(10) default NULL,
  `phone_number` varchar(25) default NULL,
  `toll_free_phone_number` varchar(20) default NULL,
  `hotel_fax_number` varchar(25) default NULL,
  `currency_code` char(3) default NULL,
  `status` char(1) default NULL,
  `total_rooms` int(11) default NULL,
  `time_zone` varchar(8) default NULL,
  `gmt_hours` float default NULL,
  `chain_id` char(2) default NULL,
  `location_description` text,
  `location_directions` text,
  `check_in_time` time default NULL,
  `check_out_time` time default NULL,
  `hhonors_reward_category` char(1) default NULL,
  `aaa_rating` char(1) default NULL,
  `hh_points_mode` char(1) default NULL,
  `locale` varchar(5) NOT NULL,
  `issource` bit(1) NOT NULL,
  `wni_id` int(4) default NULL,
  `expanded_rewards_eligible` char(1) default 'N',
  `upgrade_eligible` char(1) default 'N',
  PRIMARY KEY  (`locale`,`ctyhocn`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table `property_details`
--

/*!40000 ALTER TABLE `property_details` DISABLE KEYS */;
LOCK TABLES `property_details` WRITE;

INSERT INTO `property_details` VALUES ('MCWMCHX',NULL,'','Mason City',NULL,'US','IA','HP','2101 4th Street SW','50401','',NULL,'',NULL,'C',83,NULL,-5,'XS','','','15:00:00','11:98:72',NULL,NULL,'D',
'en_US','\0',NULL,'N','N'),
('TSNTGGI',NULL,'','Tianjin',NULL,'CN','NA','GI','airport industrial park',NULL,'',NULL,'',NULL,'C',138,NULL,8,'GI','','','15:00:00','11:98
:72',NULL,NULL,'D','en_US','\0',NULL,'N','N'),

Have not been able to repeat this.  It is advised to upgrade to the current GA version,  which is 5.6.26 as of today.  The number of bug fixes between 5.0.15 and 5.6.26 is really too huge to list here,  but it is very likely one of them solved the issue.

Hi Shane,

Can we do anything to resolve the issue without upgrading, can we check any variables/configuration due to which this error can be comming.

Regards
Syed Jafar