Bug #69513 InnoDB: Assertion failure in thread 5616 in file ut0lst.h line 271

Submitted: 19 Jun 2013 14:22 Modified: 18 Aug 2013 13:56
Reporter: Ed Segall Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.6 OS:Windows (Windows 7 Ultimate 64-bit)
Assigned to: CPU Architecture:Any

[19 Jun 2013 14:22] Ed Segall
Description:
MySQL server crashed while synchronizing the database to a model from the Workbench (5.2.. 

Here is the contents of the error log file from today, before restarting the server:

Version: '5.6.10-log'  socket: ''  port: 3306  MySQL Community Server (GPL)
2013-06-19 09:50:30 15f0  InnoDB: Assertion failure in thread 5616 in file ut0lst.h line 271
InnoDB: Failing assertion: list.count > 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Thread 5000 stopped in file ut0ut.cc line 81
InnoDB: Thread 7932 stopped in file os0sync.cc line 783
InnoDB: Thread 7832 stopped in file os0sync.cc line 475
InnoDB: Thread 7372 stopped in file ut0ut.cc line 81
InnoDB: Thread 7740 stopped in file os0sync.cc line 475
InnoDB: Thread 6892 stopped in file os0sync.cc line 475
InnoDB: Thread 5252 stopped in file os0sync.cc line 475

Here is the contents of the general log, from the 10 minutes preceding the crash:

130619  9:40:06	  171 Query	show tables
130619  9:40:11	  171 Query	SELECT DATABASE()
		  171 Init DB	classyard
130619  9:40:14	  171 Query	ALTER TABLE `ClassYard`.`weightclass_cat` 
ADD INDEX `WeightClass_idx` (`WeightClass` ASC)
130619  9:41:10	  171 Query	describe weightclass_cat
130619  9:42:57	  171 Query	help 'describe'
130619  9:43:24	  171 Query	help 'show columns'
130619  9:47:54	  171 Query	help 'show index'
130619  9:48:27	  171 Query	show index from classyard.weightclass_cat
130619  9:50:30	  172 Connect	root@localhost on 
		  172 Query	set autocommit=1
		  172 Query	SET SESSION TRANSACTION ISOLATION LEVEL REPEATABLE READ
		  172 Query	SHOW SESSION VARIABLES LIKE 'lower_case_table_names'
		  172 Query	SELECT current_user()
		  172 Query	SET CHARACTER SET utf8
		  172 Query	SET NAMES utf8
		  172 Query	SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0
		  172 Query	SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0
		  172 Query	SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='TRADITIONAL,ALLOW_INVALID_DATES'
		  172 Query	ALTER TABLE `ClassYard`.`cardb` CHANGE COLUMN `WeightCode` `WeightCode` VARCHAR(1) NULL DEFAULT NULL COMMENT 'EJS: Should always be \' \' or \'’W’ (for UP)\nNOTE: UP-specific behavior'  , 
  ADD CONSTRAINT `fk_cardb_cartype_cat1`
  FOREIGN KEY (`CarType` )
  REFERENCES `ClassYard`.`cartype_cat` (`CarType_Id` )
  ON DELETE RESTRICT
  ON UPDATE RESTRICT, 
  ADD CONSTRAINT `fk_cardb_aeistat_cat1`
  FOREIGN KEY (`AEIStat` )
  REFERENCES `ClassYard`.`aeistat_cat` (`AEIStat` )
  ON DELETE RESTRICT
  ON UPDATE RESTRICT, 
  ADD CONSTRAINT `fk_cardb_weightclass_cat1`
  FOREIGN KEY (`WeightClass` )
  REFERENCES `ClassYard`.`weightclass_cat` (`WeightClass` )
  ON DELETE RESTRICT
  ON UPDATE RESTRICT, 
  ADD CONSTRAINT `fk_cardb_cutdb1`
  FOREIGN KEY (`CrestTimeStamp` , `CutId` )
  REFERENCES `ClassYard`.`cutdb` (`CrestTimeStamp` , `CutId` )
  ON DELETE RESTRICT
  ON UPDATE RESTRICT
		  172 Query	ALTER TABLE `ClassYard`.`cmddb` 
  ADD CONSTRAINT `fk_cmddb_workstation_cat1`
  FOREIGN KEY (`HmiNode` )
  REFERENCES `ClassYard`.`workstation_cat` (`Id` )
  ON DELETE RESTRICT
  ON UPDATE RESTRICT, 
  ADD CONSTRAINT `fk_cmddb_craft_cat1`
  FOREIGN KEY (`Craft` )
  REFERENCES `ClassYard`.`craft_cat` (`CraftCode` )
  ON DELETE RESTRICT
  ON UPDATE RESTRICT
		  172 Query	ALTER TABLE `ClassYard`.`cutdb` 
  ADD CONSTRAINT `fk_cutdb_workstation_cat1`
  FOREIGN KEY (`NodeID` )
  REFERENCES `ClassYard`.`workstation_cat` (`Id` )
  ON DELETE RESTRICT
  ON UPDATE RESTRICT, 
  ADD CONSTRAINT `fk_cutdb_tanp4mapping_cat1`
  FOREIGN KEY (`dest_track` )
  REFERENCES `ClassYard`.`tanp4mapping_cat` (`Track` )
  ON DELETE RESTRICT
  ON UPDATE RESTRICT, 
  ADD CONSTRAINT `fk_cutdb_tanp4mapping_cat2`
  FOREIGN KEY (`ActualTrack` )
  REFERENCES `ClassYard`.`tanp4mapping_cat` (`Track` )
  ON DELETE RESTRICT
  ON UPDATE RESTRICT, 
  ADD CONSTRAINT `fk_cutdb_modes_cat1`
  FOREIGN KEY (`ymode_at_pin_pull` )
  REFERENCES `ClassYard`.`modes_cat` (`ModeNbr` )
  ON DELETE RESTRICT
  ON UPDATE RESTRICT, 
  ADD CONSTRAINT `fk_cutdb_SwingReasons_cat1`
  FOREIGN KEY (`SwingReason` )
  REFERENCES `ClassYard`.`SwingReasons_cat` (`Type` )
  ON DELETE RESTRICT
  ON UPDATE RESTRICT, 
  ADD CONSTRAINT `fk_cutdb_weightclass_cat1`
  FOREIGN KEY (`MaxWCForControl` )
  REFERENCES `ClassYard`.`weightclass_cat` (`WeightClass` )
  ON DELETE RESTRICT
  ON UPDATE RESTRICT, 
  ADD CONSTRAINT `fk_cutdb_crestFailure_cat1`
  FOREIGN KEY (`CrestFailure` )
  REFERENCES `ClassYard`.`crestFailure_cat` (`Type` )
  ON DELETE RESTRICT
  ON UPDATE RESTRICT, 
COMMENT = 'New length, weight and other values were recently added to the cutrec. These changes have not yet been incorporated into this table. '

Additional information:

A MySQL Command Line client window was open at the time of the crash.

The database is running on a laptop, which is put into a Hibernate state once a day. It is also occasionally put into a Sleep state. 

This is a development database, and other clients were not accessing it at the time. 

How to repeat:
I restarted the server and attempted to repeat the database synchronization operation from the Workbench. When I did, the specific error did not repeat, but there were other unexpected errors:

1) The Workbench reported the following:

Executing SQL script in server

ERROR: Error 1050: Table 'classyard/#sql-ib3192' already exists

ALTER TABLE `ClassYard`.`cutdb` 

  ADD CONSTRAINT `fk_cutdb_workstation_cat1`

  FOREIGN KEY (`NodeID` )

  REFERENCES `ClassYard`.`workstation_cat` (`Id` )

  ON DELETE RESTRICT

  ON UPDATE RESTRICT, 

  ADD CONSTRAINT `fk_cutdb_tanp4mapping_cat1`

  FOREIGN KEY (`dest_track` )

  REFERENCES `ClassYard`.`tanp4mapping_cat` (`Track` )

  ON DELETE RESTRICT

  ON UPDATE RESTRICT, 

  ADD CONSTRAINT `fk_cutdb_tanp4mapping_cat2`

  FOREIGN KEY (`ActualTrack` )

  REFERENCES `ClassYard`.`tanp4mapping_cat` (`Track` )

  ON DELETE RESTRICT

  ON UPDATE RESTRICT, 

  ADD CONSTRAINT `fk_cutdb_modes_cat1`

  FOREIGN KEY (`ymode_at_pin_pull` )

  REFERENCES `ClassYard`.`modes_cat` (`ModeNbr` )

  ON DELETE RESTRICT

  ON UPDATE RESTRICT, 

  ADD CONSTRAINT `fk_cutdb_SwingReasons_cat1`

  FOREIGN KEY (`SwingReason` )

  REFERENCES `ClassYard`.`SwingReasons_cat` (`Type` )

  ON DELETE RESTRICT

  ON UPDATE RESTRICT, 

  ADD CONSTRAINT `fk_cutdb_weightclass_cat1`

  FOREIGN KEY (`MaxWCForControl` )

  REFERENCES `ClassYard`.`weightclass_cat` (`WeightClass` )

  ON DELETE RESTRICT

  ON UPDATE RESTRICT, 

  ADD CONSTRAINT `fk_cutdb_crestFailure_cat1`

  FOREIGN KEY (`CrestFailure` )

  REFERENCES `ClassYard`.`crestFailure_cat` (`Type` )

  ON DELETE RESTRICT

  ON UPDATE RESTRICT, 

COMMENT = 'New length, weight and other values were recently added to the cutrec. These changes have not yet been incorporated into this table. ' 

SQL script execution finished: statements: 3 succeeded, 1 failed

2) The console window reported conflicting information about a table (weightclass_cat) that had previously been created:

--------------------------------------------------------------------------
mysql> show index from classyard.weightclass_cat;
No connection. Trying to reconnect...
Connection id:    10
Current database: classyard

ERROR 1146 (42S02): Table 'classyard.weightclass_cat' doesn't exist
mysql> show tables;
+-------------------------+
| Tables_in_classyard     |
+-------------------------+
| actuatortype_cat        |
| aeistat_cat             |
| as_hump                 |
| blockunblock_cat        |
| cardb                   |
| cartype_cat             |
| cmddb                   |
| config_history          |
| couplingspeed           |
| craft_cat               |
| crestfailure_cat        |
| cust_reroutereasons_cat |
| cutdb                   |
| deviationranges_cat     |
| device_cat              |
| device_occupancy        |
| device_spec             |
| dtc                     |
| energylosses            |
| io_event                |
| lead_cat                |
| misroutes               |
| moddb                   |
| modechangereason_cat    |
| modes_cat               |
| mvt                     |
| occreason_cat           |
| params                  |
| radar_spec              |
| radartype_cat           |
| reportlist              |
| reroutereasons_cat      |
| retarder_spec           |
| retarderperformance     |
| retarderposition_cat    |
| retardertypes_cat       |
| retsection_spec         |
| retsectionperformance   |
| rxv                     |
| shift_cat               |
| speedactual             |
| speedeventtype_cat      |
| speedstate_cat          |
| speedtune               |
| stalls                  |
| stalltype_cat           |
| swingreasons_cat        |
| switchhistory           |
| switchname_cat          |
| tanp4mapping_cat        |
| temperatureclass_cat    |
| tsegname_cat            |
| units_cat               |
| wd_history              |
| wd_spec                 |
| wd_v                    |
| wdhistory_view          |
| wdtype_cat              |
| weatherfactors          |
| weightclass_cat         |
| workstation_cat         |
| yardsystem              |
+-------------------------+
62 rows in set (0.00 sec)

mysql> describe weightclass_cat;
ERROR 1146 (42S02): Table 'classyard.weightclass_cat' doesn't exist
mysql>
--------------------------------------------------------------------------

As you can see, according to `show tables`, table weightclass_cat does exist despite the what was reported by the `show index` command.

Here is the contents of the log after restarting: 

2013-06-19 10:09:01 164 [Note] Plugin 'FEDERATED' is disabled.
2013-06-19 10:09:01 164 [Warning] option 'innodb-autoextend-increment': unsigned value 67108864 adjusted to 1000
2013-06-19 10:09:01 1d30 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-06-19 10:09:01 164 [Note] InnoDB: The InnoDB memory heap is disabled
2013-06-19 10:09:01 164 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-06-19 10:09:01 164 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-06-19 10:09:01 164 [Note] InnoDB: CPU does not support crc32 instructions
2013-06-19 10:09:01 164 [Note] InnoDB: Initializing buffer pool, size = 269.0M
2013-06-19 10:09:01 164 [Note] InnoDB: Completed initialization of buffer pool
2013-06-19 10:09:01 164 [Note] InnoDB: Highest supported file format is Barracuda.
2013-06-19 10:09:01 164 [Note] InnoDB: Log scan progressed past the checkpoint lsn 69866521
2013-06-19 10:09:01 164 [Note] InnoDB: Database was not shutdown normally!
2013-06-19 10:09:01 164 [Note] InnoDB: Starting crash recovery.
2013-06-19 10:09:01 164 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-06-19 10:09:02 164 [Note] InnoDB: Restoring possible half-written data pages 
2013-06-19 10:09:02 164 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 69891287
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 14 row operations to undo
InnoDB: Trx id counter is 98560
2013-06-19 10:09:03 164 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2013-06-19 10:09:03 1d30  InnoDB: Rolling back trx with id 98102, 14 rows to undo
2013-06-19 10:09:03 164 [Note] InnoDB: Rollback of trx with id 98102 completed
2013-06-19 10:09:03 164 [Warning] Invalid (old?) table or database name '#sql-ib3192'
2013-06-19 10:09:03 164 [Note] InnoDB: 128 rollback segment(s) are active.
2013-06-19 10:09:03 164 [Note] InnoDB: Waiting for purge to start
2013-06-19 10:09:04 164 [Note] InnoDB: 1.2.10 started; log sequence number 69891287
2013-06-19 10:09:04 164 [Note] Server hostname (bind-address): '*'; port: 3306
2013-06-19 10:09:04 164 [Note] IPv6 is available.
2013-06-19 10:09:04 164 [Note]   - '::' resolves to '::';
2013-06-19 10:09:04 164 [Note] Server socket created on IP: '::'.
2013-06-19 10:09:04 164 [Note] Event Scheduler: Loaded 0 events
2013-06-19 10:09:04 164 [Note] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld: ready for connections.
Version: '5.6.10-log'  socket: ''  port: 3306  MySQL Community Server (GPL)
[19 Jun 2013 14:44] Shane Bester
Hi!  Can you please compress+upload the entire mysql error log?
[20 Jun 2013 19:02] Sveta Smirnova
Thank you for the feedback.

Do you have backup? If yes, please send us output of SHOW CREATE TABLE weightclass_cat and SHOW CREATE TABLE cardb as well as SHOW TABLE STATUS for both tables.
[20 Jun 2013 21:05] Ed Segall
Are you asking whether I backed up the database? Unfortunately, I did not. I'm in a design phase and the database had little or no data in it, so I just followed some recovery procedures that I found until it appeared to be in a useable state. In fact, I believe that at one point I dropped the schema.
[20 Jun 2013 23:12] Sveta Smirnova
Thank you for the feedback.

Actually what I want to know is table structure for both tables and how many rows they had prior crash. Do you have this information? Since you are "in a design phase" I was hoping you do.
[21 Jun 2013 21:09] Ed Segall
I believe that neither table had any rows prior to the crash. 

I don't have a database backup from before the crash, so I can only do `show create table' and `show table status' using the recovered database. (I'll do that in a subsequent comment.) I do have sql exported from the Workbench that I believe was used to create the tables before the problem occurred. I'll include it here:

-- -----------------------------------------------------
-- Table `ClassYard`.`weightclass_cat`
-- -----------------------------------------------------
CREATE  TABLE IF NOT EXISTS `ClassYard`.`weightclass_cat` (
  `WeightClass` VARCHAR(1) NULL ,
  `WeightDescription` VARCHAR(50) NULL DEFAULT NULL )
ENGINE = InnoDB
DEFAULT CHARACTER SET = utf8;

-- -----------------------------------------------------
-- Table `ClassYard`.`cardb`
-- -----------------------------------------------------
CREATE  TABLE IF NOT EXISTS `ClassYard`.`cardb` (
  `CrestTimeStamp` DOUBLE NOT NULL ,
  `CutId` INT(11) NOT NULL ,
  `car_id` VARCHAR(10) NOT NULL ,
  `timeStampStr` DATETIME NULL DEFAULT NULL ,
  `UserLineNum` INT(11) NULL DEFAULT NULL ,
  `NotHump` VARCHAR(1) NULL DEFAULT NULL COMMENT 'EJS: Should this be CHAR?\nShould it relate to a _cat table?' ,
  `CarInfoIndex` INT(11) NULL DEFAULT NULL ,
  `handling_code` VARCHAR(1) NULL COMMENT 'EJS: Should this reference a _cat table?\nHow is this different from yard_handling_code?\nThis column is always empty in NPW database sample. ' ,
  `Commodity` VARCHAR(7) NULL DEFAULT NULL ,
  `IsLoaded` VARCHAR(1) NULL COMMENT 'EJS: Should always be \'T\' or \'F\'' ,
  `CarType` INT(11) NULL DEFAULT NULL ,
  `MIS_Weight` INT(11) NULL DEFAULT NULL ,
  `hump_time` DATETIME NULL COMMENT 'EJS: How is this different from CrestTimeStamp (originally timeStamp)?' ,
  `MovedTF` VARCHAR(1) NULL DEFAULT NULL ,
  `AEIMatchTF` VARCHAR(1) NULL DEFAULT NULL ,
  `WeightCode` VARCHAR(1) NULL COMMENT 'EJS: Should always be \' \' or \'’W’ (for UP)\nNOTE: UP-specific behavior' ,
  `OverWgtValue` INT(11) NULL DEFAULT NULL ,
  `TrainID` INT(11) NULL ,
  `Axles` INT(11) NULL DEFAULT NULL ,
  `MISAxles` INT(11) NULL DEFAULT NULL ,
  `Length` DOUBLE NULL DEFAULT NULL ,
  `MISLength` DOUBLE NULL DEFAULT NULL ,
  `WBTruck` DOUBLE NULL DEFAULT NULL ,
  `WeightClass` INT(11) NULL DEFAULT NULL ,
  `AARCarType` VARCHAR(5) NULL DEFAULT NULL ,
  `CarCode` VARCHAR(5) NULL DEFAULT NULL ,
  `YardHandlingCode` VARCHAR(1) NULL DEFAULT NULL COMMENT 'EJS: How is this different from handlingCode?\nSteve is looking into this. ' ,
  `BearingType` INT(11) NULL DEFAULT NULL ,
  `ArticulatedCount` INT(11) NULL DEFAULT NULL ,
  `OverHand` INT(11) NULL DEFAULT NULL ,
  `SpecialHandling` VARCHAR(7) NULL DEFAULT NULL ,
  `AEIStat` INT(11) NULL DEFAULT NULL ,
  `CarNumInCut` INT(11) NULL DEFAULT -1 ,
  INDEX `car_id` (`car_id` ASC) ,
  INDEX `CarCode` (`CarCode` ASC) ,
  INDEX `timeStamp` (`CrestTimeStamp` ASC) ,
  INDEX `TrainID` (`TrainID` ASC) ,
  INDEX `YardHandlingCode` (`YardHandlingCode` ASC) ,
  PRIMARY KEY (`CrestTimeStamp`, `CutId`) ,
  INDEX `timeStamp_carId` (`CrestTimeStamp` ASC, `car_id` ASC) ,
  INDEX `fk_cardb_cartype_cat1_idx` (`CarType` ASC) ,
  INDEX `fk_cardb_aeistat_cat1_idx` (`AEIStat` ASC) ,
  INDEX `fk_cardb_weightclass_cat1_idx` (`WeightClass` ASC) ,
  INDEX `fk_cardb_cutdb1_idx` (`CrestTimeStamp` ASC, `CutId` ASC) )
ENGINE = InnoDB
DEFAULT CHARACTER SET = utf8
COMMENT = 'EJS: Primary key previously used car_id, now uses CutId.';
[21 Jun 2013 21:16] Ed Segall
mysql> show create table weightclass_cat\G
*************************** 1. row ***************************
       Table: weightclass_cat
Create Table: CREATE TABLE `weightclass_cat` (
  `WeightClass` varchar(1) NOT NULL,
  `WeightDescription` varchar(50) DEFAULT NULL,
  PRIMARY KEY (`WeightClass`),
  KEY `WeightClass_idx` (`WeightClass`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
1 row in set (0.00 sec)

mysql> show create table cardb\G
*************************** 1. row ***************************
       Table: cardb
Create Table: CREATE TABLE `cardb` (
  `CrestTimeStamp` double NOT NULL,
  `CutId` int(11) NOT NULL,
  `car_id` varchar(10) NOT NULL,
  `timeStampStr` datetime DEFAULT NULL,
  `UserLineNum` int(11) DEFAULT NULL,
  `NotHump` varchar(1) DEFAULT NULL COMMENT 'EJS: Should this be CHAR?\nShould it relate to a _cat table?',
  `CarInfoIndex` int(11) DEFAULT NULL,
  `handling_code` varchar(1) DEFAULT NULL COMMENT 'EJS: Should this reference a _cat table?\nHow is this different from yard_handling_code?\nThis column is always empty in NPW database sample. ',
  `Commodity` varchar(7) DEFAULT NULL,
  `IsLoaded` varchar(1) DEFAULT NULL COMMENT 'EJS: Should always be ''T'' or ''F''',
  `CarType` int(11) DEFAULT NULL,
  `MIS_Weight` int(11) DEFAULT NULL,
  `hump_time` datetime DEFAULT NULL COMMENT 'EJS: How is this different from CrestTimeStamp (originally timeStamp)?',
  `MovedTF` varchar(1) DEFAULT NULL,
  `AEIMatchTF` varchar(1) DEFAULT NULL,
  `WeightCode` varchar(1) DEFAULT NULL COMMENT 'EJS: Should always be '' '' or ''’W’ (for UP)\nNOTE: UP-specific behavior',
  `OverWgtValue` int(11) DEFAULT NULL,
  `TrainID` int(11) DEFAULT NULL,
  `Axles` int(11) DEFAULT NULL,
  `MISAxles` int(11) DEFAULT NULL,
  `Length` double DEFAULT NULL,
  `MISLength` double DEFAULT NULL,
  `WBTruck` double DEFAULT NULL,
  `WeightClass` varchar(1) DEFAULT NULL COMMENT 'EJS: Type changed to satisfy MySQL',
  `AARCarType` varchar(5) DEFAULT NULL,
  `CarCode` varchar(5) DEFAULT NULL,
  `YardHandlingCode` varchar(1) DEFAULT NULL COMMENT 'EJS: How is this different from handlingCode?\nSteve is looking into this. ',
  `BearingType` int(11) DEFAULT NULL,
  `ArticulatedCount` int(11) DEFAULT NULL,
  `OverHand` int(11) DEFAULT NULL,
  `SpecialHandling` varchar(7) DEFAULT NULL,
  `AEIStat` int(11) DEFAULT NULL,
  `CarNumInCut` int(11) DEFAULT '-1',
  PRIMARY KEY (`CrestTimeStamp`,`CutId`),
  KEY `car_id` (`car_id`),
  KEY `CarCode` (`CarCode`),
  KEY `timeStamp` (`CrestTimeStamp`),
  KEY `TrainID` (`TrainID`),
  KEY `YardHandlingCode` (`YardHandlingCode`),
  KEY `timeStamp_carId` (`CrestTimeStamp`,`car_id`),
  KEY `fk_cardb_cartype_cat1_idx` (`CarType`),
  KEY `fk_cardb_aeistat_cat1_idx` (`AEIStat`),
  KEY `fk_cardb_weightclass_cat1_idx` (`WeightClass`),
  KEY `fk_cardb_cutdb1_idx` (`CrestTimeStamp`,`CutId`),
  CONSTRAINT `fk_cardb_aeistat_cat1` FOREIGN KEY (`AEIStat`) REFERENCES `aeistat_cat` (`AEIStat`) ON DELETE NO ACTION ON UPDATE NO ACTION,
  CONSTRAINT `fk_cardb_cutdb1` FOREIGN KEY (`CrestTimeStamp`, `CutId`) REFERENCES `cutdb` (`CrestTimeStamp`, `CutId`) ON DELETE NO ACTION ON UPDATE NO ACTION,
  CONSTRAINT `fk_cardb_cartype_cat1` FOREIGN KEY (`CarType`) REFERENCES `cartype_cat` (`CarType_Id`) ON DELETE NO ACTION ON UPDATE NO ACTION,
  CONSTRAINT `fk_cardb_weightclass_cat1` FOREIGN KEY (`WeightClass`) REFERENCES `weightclass_cat` (`WeightClass`) ON DELETE NO ACTION ON UPDATE NO ACTION
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='EJS: Primary key previously used car_id, now uses CutId.'
1 row in set (0.00 sec)

mysql> show table status like 'weightclass_cat'\G
*************************** 1. row ***************************
           Name: weightclass_cat
         Engine: InnoDB
        Version: 10
     Row_format: Compact
           Rows: 0
 Avg_row_length: 0
    Data_length: 16384
Max_data_length: 0
   Index_length: 16384
      Data_free: 0
 Auto_increment: NULL
    Create_time: 2013-06-19 14:33:56
    Update_time: NULL
     Check_time: NULL
      Collation: utf8_general_ci
       Checksum: NULL
 Create_options:
        Comment:
1 row in set (0.00 sec)

mysql> show table status like 'cardb'\G
*************************** 1. row ***************************
           Name: cardb
         Engine: InnoDB
        Version: 10
     Row_format: Compact
           Rows: 0
 Avg_row_length: 0
    Data_length: 16384
Max_data_length: 0
   Index_length: 163840
      Data_free: 0
 Auto_increment: NULL
    Create_time: 2013-06-19 11:51:52
    Update_time: NULL
     Check_time: NULL
      Collation: utf8_general_ci
       Checksum: NULL
 Create_options:
        Comment: EJS: Primary key previously used car_id, now uses CutId.
1 row in set (0.00 sec)
[18 Jul 2013 13:56] Sveta Smirnova
Thank you for the feedback.

Looks like we need also output of SHOW CREATE TABLE cutdb and SHOW CREATE TABLE of all tables, referenced by foreign key constraints.
[19 Aug 2013 1: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".

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.048 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.