Bug #11475 | 1016 error. tables are not accessable and cannot be repaired | ||
---|---|---|---|
Submitted: | 21 Jun 2005 10:06 | Modified: | 23 Jul 2005 8:04 |
Reporter: | John Macrae | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S1 (Critical) |
Version: | 4.1.9 | OS: | Windows (Win 2003 Server) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[21 Jun 2005 10:06]
John Macrae
[21 Jun 2005 10:23]
Aleksey Kishkin
Hi! Please send the output of SHOW INNODB STATUS\G
[21 Jun 2005 12:43]
John Macrae
mysql> connect mysql Connection id: 2 Current database: mysql mysql> SHOW INNODB STATUS\G *************************** 1. row *************************** Status: ===================================== 050621 15:39:54 INNODB MONITOR OUTPUT ===================================== Per second averages calculated from the last 31 seconds ---------- SEMAPHORES ---------- OS WAIT ARRAY INFO: reservation count 3, signal count 3 Mutex spin waits 0, rounds 0, OS waits 0 RW-shared spins 6, OS waits 3; RW-excl spins 0, OS waits 0 ------------ TRANSACTIONS ------------ Trx id counter 0 6284800 Purge done for trx's n:o < 0 6284268 undo n:o < 0 0 History list length 1 Total number of lock structs in row lock hash table 0 LIST OF TRANSACTIONS FOR EACH SESSION: ---TRANSACTION 0 0, not started, OS thread id 2452 MySQL thread id 2, query id 2 localhost 127.0.0.1 root SHOW INNODB STATUS -------- FILE I/O -------- I/O thread 0 state: wait Windows aio (insert buffer thread) I/O thread 1 state: wait Windows aio (log thread) I/O thread 2 state: wait Windows aio (read thread) I/O thread 3 state: wait Windows aio (write thread) Pending normal aio reads: 0, aio writes: 0, ibuf aio reads: 0, log i/o's: 0, sync i/o's: 0 Pending flushes (fsync) log: 0; buffer pool: 0 75 OS file reads, 4 OS file writes, 4 OS fsyncs 2.34 reads/s, 43526 avg bytes/read, 0.12 writes/s, 0.12 fsyncs/s ------------------------------------- INSERT BUFFER AND ADAPTIVE HASH INDEX ------------------------------------- Ibuf for space 0: size 1, free list len 0, seg size 2, is empty Ibuf for space 0: size 1, free list len 0, seg size 2, 0 inserts, 0 merged recs, 0 merges Hash table size 186869, used cells 0, node heap has 0 buffer(s) 0.00 hash searches/s, 0.84 non-hash searches/s --- LOG --- Log sequence number 0 11676952 Log flushed up to 0 11676952 Last checkpoint at 0 11676952 0 pending log writes, 0 pending chkp writes 9 log i/o's done, 0.28 log i/o's/second ---------------------- BUFFER POOL AND MEMORY ---------------------- Total memory allocated 54847168; in additional pool allocated 165248 Buffer pool size 2880 Free buffers 2815 Database pages 65 Modified db pages 0 Pending reads 0 Pending writes: LRU 0, flush list 0, single page 0 Pages read 65, created 0, written 0 2.03 reads/s, 0.00 creates/s, 0.00 writes/s Buffer pool hit rate 705 / 1000 -------------- ROW OPERATIONS -------------- 0 queries inside InnoDB, 0 queries in queue Main thread id 2428, state: waiting for server activity Number of rows inserted 0, updated 0, deleted 0, read 0 0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 0.00 reads/s ---------------------------- END OF INNODB MONITOR OUTPUT ============================ 1 row in set, 1 warning (0.06 sec) mysql>
[21 Jun 2005 14:51]
Heikki Tuuri
Hi! Please post the error message verbatim. Have you mixed ibdata files or .ibd files? My first guess is that you have mixed those files, and the InnoDB tables really are not in the files you are currently using. Regards, Heikki
[21 Jun 2005 15:24]
John Macrae
There were no seperate files. We have one ibdata file. There are added isam files as part of the whole db which are things such as help (see dir list). The ISAM files are ok, the innodb files are unavailable. Example error (note I changed the pw and user in the listing): mysql> repair table ims_bugs; +----------------+--------+----------+------------------------------------------ --+ | Table | Op | Msg_type | Msg_text | +----------------+--------+----------+------------------------------------------ --+ | mysql.ims_bugs | repair | error | Can't open file: 'ims_bugs.ibd' (errno: 1 ) | +----------------+--------+----------+------------------------------------------ --+ 1 row in set (0.08 sec) mysql> ><><><><><><><><><><><><><><><><><><><><><><><><>< C:\Program Files\MySQL\MySQL Server 4.1\data\mysql>mysqldump -uxxxxxxxx -pxxxxxxxx -- all-databases -- MySQL dump 10.9 -- -- Host: localhost Database: -- ------------------------------------------------------ -- Server version 4.1.9-nt /*!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 */; /*!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" */; -- -- Current Database: `mysql` -- CREATE DATABASE /*!32312 IF NOT EXISTS*/ `mysql` /*!40100 DEFAULT CHARACTER SET latin1 */; USE `mysql`; mysqldump: Got error: 1016: Can't open file: 'ims_attachments.ibd' (errno: 1) wh en using LOCK TABLES ><><><><><><><><><><><><><><><><><><><><><><><><>< ><><><><><><><><><><><><><><><><><><><><><><><><>< C:\Program Files\MySQL\MySQL Server 4.1\data\mysql> Directory of C:\Program Files\MySQL\MySQL Server 4.1\data\mysql 06/20/2005 03:27 PM <DIR> . 06/20/2005 03:27 PM <DIR> .. 01/11/2005 11:59 PM 8,820 columns_priv.frm 01/11/2005 11:59 PM 0 columns_priv.MYD 01/11/2005 11:59 PM 1,024 columns_priv.MYI 01/11/2005 11:59 PM 9,178 db.frm 06/20/2005 03:31 PM 866 db.MYD 06/20/2005 03:31 PM 4,096 db.MYI 01/11/2005 11:59 PM 8,665 func.frm 01/11/2005 11:59 PM 0 func.MYD 01/11/2005 11:59 PM 1,024 func.MYI 01/11/2005 11:59 PM 8,700 help_category.frm 01/11/2005 11:59 PM 864 help_category.MYD 01/11/2005 11:59 PM 3,072 help_category.MYI 01/11/2005 11:59 PM 8,612 help_keyword.frm 01/11/2005 11:59 PM 7,320 help_keyword.MYD 01/11/2005 11:59 PM 13,312 help_keyword.MYI 01/11/2005 11:59 PM 8,630 help_relation.frm 01/11/2005 11:59 PM 5,103 help_relation.MYD 01/11/2005 11:59 PM 9,216 help_relation.MYI 01/11/2005 11:59 PM 8,770 help_topic.frm 01/11/2005 11:59 PM 166,324 help_topic.MYD 01/11/2005 11:59 PM 15,360 help_topic.MYI 01/11/2005 11:59 PM 9,148 host.frm 01/11/2005 11:59 PM 0 host.MYD 01/11/2005 11:59 PM 1,024 host.MYI 06/20/2005 02:57 PM <DIR> imsfrm 06/20/2005 12:00 PM 8,714 ims_attachments.frm 06/20/2005 12:00 PM 8,710 ims_bughistory.frm 06/20/2005 12:00 PM 9,080 ims_bugs.frm 06/20/2005 12:00 PM 8,710 ims_bugtypes.frm 06/20/2005 12:00 PM 8,630 ims_customers.frm 06/20/2005 12:00 PM 8,606 ims_dependencies.frm 06/20/2005 12:00 PM 8,738 ims_freetext.frm 06/20/2005 12:00 PM 8,626 ims_mailing.frm 06/20/2005 12:00 PM 8,620 ims_odt.frm 06/20/2005 12:00 PM 8,668 ims_os.frm 06/20/2005 12:00 PM 8,996 ims_preferences.frm 06/20/2005 12:00 PM 8,674 ims_products.frm 06/20/2005 12:00 PM 8,628 ims_settings.frm 06/20/2005 12:00 PM 8,710 ims_severities.frm 06/20/2005 12:00 PM 8,710 ims_statuses.frm 06/20/2005 12:00 PM 13,548 ims_users.frm 06/20/2005 12:00 PM 8,630 ims_usersgroup.frm 06/20/2005 12:00 PM 8,680 ims_userslinks.frm 01/11/2005 11:59 PM 8,925 tables_priv.frm 01/11/2005 11:59 PM 0 tables_priv.MYD 01/11/2005 11:59 PM 1,024 tables_priv.MYI 01/11/2005 11:59 PM 8,636 time_zone.frm 01/11/2005 11:59 PM 0 time_zone.MYD 01/11/2005 11:59 PM 1,024 time_zone.MYI 01/11/2005 11:59 PM 8,624 time_zone_leap_second.frm 01/11/2005 11:59 PM 0 time_zone_leap_second.MYD 01/11/2005 11:59 PM 1,024 time_zone_leap_second.MYI 01/11/2005 11:59 PM 8,606 time_zone_name.frm 01/11/2005 11:59 PM 0 time_zone_name.MYD 01/11/2005 11:59 PM 1,024 time_zone_name.MYI 01/11/2005 11:59 PM 8,686 time_zone_transition.frm 01/11/2005 11:59 PM 0 time_zone_transition.MYD 01/11/2005 11:59 PM 1,024 time_zone_transition.MYI 01/11/2005 11:59 PM 8,748 time_zone_transition_type.frm 01/11/2005 11:59 PM 0 time_zone_transition_type.MYD 01/11/2005 11:59 PM 1,024 time_zone_transition_type.MYI 01/11/2005 11:59 PM 9,992 user.frm 06/20/2005 03:31 PM 264 user.MYD 06/20/2005 03:31 PM 2,048 user.MYI 63 File(s) 531,479 bytes 3 Dir(s) 36,391,776,256 bytes free C:\Program Files\MySQL\MySQL Server 4.1\data\mysql>
[21 Jun 2005 18:29]
Heikki Tuuri
John, did you move the database from Unix? A possibility is that the table names contain upper case letters. On Windows InnoDB assumes that internally all table names are in lower case. But the most probable reason for the problem is that you are using an ibdata1 file that does not really contain InnoDB tables. Please check the creation time of the ibdata file. It should be earlier than the creation time of the corresponding .frm files. Regards, Heikki
[21 Jun 2005 19:09]
John Macrae
The files were created on win nt. the .frm files were lost. however, they were recreated and copied over--the .frm files are identical. If I look at the ibdata and iblog_files (using a copy) they contain the data that used to be visable in the data base before the crash. the file type (of the ims_ files) is innodb when i use sysyog to look at the database. are there any utilites to extract data to sql or csv files?
[21 Jun 2005 20:15]
Heikki Tuuri
John, please print SHOW VARIABLES; and check that datadir or innodb_data_home_dir and innodb_data_file_path really point at the right ibdata file. mysqld may be actually reading a new, recreated empty ibdata file from somewhere else. Or, you may have dropped all the InnoDB tables! That would explain how the .frm files disappeared. Putting the .frm files back does not bring your dropped tables back :(. You can use innodb_table_monitor to print the contents of the internal InnoDB data dictionary in the ibdata file. Read very carefully the instructions at: http://dev.mysql.com/doc/mysql/en/innodb-monitor.html Regards, Heikki
[21 Jun 2005 22:59]
John Macrae
I have run the show command (show tables) and the missing tables are listed (the IMS_ tables in the directory listings.) The my.ini file points to the correct directory where the data file and logs are. We did not confirm any drop the DB/tables. A show table status reveals the table names with null columns and a warning "Can't open file 'ims_attachments.ibd" (error: 1). Again, the raw records seem to be in the ibdata file ( guessing from a stream output of the file) I assume, if the data exisits, any drop action only edits some pointers and does not recover the space. If so, can the missing .ibd table records be rebuilt?
[22 Jun 2005 5:28]
Heikki Tuuri
John, please use innodb_table_monitor to check if the tables still exist in the ibdata file. If the tables have been DROPped, it may be possible to recover them, but it will be a costly consulting operation. Regards, Heikki
[22 Jun 2005 8:52]
John Macrae
This is the output from the innodb_table_monitor show table. It has rows data colums--what gives!!!!!! =========================================== 050622 11:51:05 INNODB TABLE MONITOR OUTPUT =========================================== -------------------------------------- TABLE: name SYS_FOREIGN, id 0 11, columns 8, indexes 3, appr.rows 0 COLUMNS: ID: DATA_VARCHAR prtype 1 len 0 prec 0; FOR_NAME: DATA_VARCHAR prtype 1 len 0 prec 0; REF_NAME: DATA_VARCHAR prtype 1 len 0 prec 0; N_COLS: DATA_INT len 4 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name ID_IND, id 0 11, fields 1/6, type 3 root page 46, appr.key vals 0, leaf pages 1, size pages 1 FIELDS: ID DB_TRX_ID DB_ROLL_PTR FOR_NAME REF_NAME N_COLS INDEX: name FOR_IND, id 0 12, fields 1/2, type 0 root page 47, appr.key vals 0, leaf pages 1, size pages 1 FIELDS: FOR_NAME ID INDEX: name REF_IND, id 0 13, fields 1/2, type 0 root page 48, appr.key vals 0, leaf pages 1, size pages 1 FIELDS: REF_NAME ID -------------------------------------- TABLE: name SYS_FOREIGN_COLS, id 0 12, columns 8, indexes 1, appr.rows 0 COLUMNS: ID: DATA_VARCHAR prtype 1 len 0 prec 0; POS: DATA_INT len 4 prec 0; FOR_COL_NAME: DATA_VARCHAR prtype 1 len 0 prec 0; REF_COL_NAME: DATA_VARCHAR prtype 1 len 0 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name ID_IND, id 0 14, fields 2/6, type 3 root page 49, appr.key vals 0, leaf pages 1, size pages 1 FIELDS: ID POS DB_TRX_ID DB_ROLL_PTR FOR_COL_NAME REF_COL_NAME -------------------------------------- TABLE: name mysql/innodb_table_monitor, id 0 70, columns 5, indexes 1, appr.rows 0 COLUMNS: a: DATA_INT len 4 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name GEN_CLUST_INDEX, id 0 77, fields 0/4, type 1 root page 50, appr.key vals 0, leaf pages 1, size pages 1 FIELDS: DB_ROW_ID DB_TRX_ID DB_ROLL_PTR a -------------------------------------- TABLE: name mysql/innoodb_monitor, id 0 71, columns 5, indexes 1, appr.rows 0 COLUMNS: a: DATA_INT len 4 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name GEN_CLUST_INDEX, id 0 78, fields 0/4, type 1 root page 51, appr.key vals 0, leaf pages 1, size pages 1 FIELDS: DB_ROW_ID DB_TRX_ID DB_ROLL_PTR a -------------------------------------- TABLE: name test_statistics/ims_attachments, id 0 49, columns 9, indexes 1, appr.rows 168 COLUMNS: id: DATA_INT len 4 prec 0; bug_id: DATA_INT len 4 prec 0; file_name: DATA_MYSQL len 765 prec 0; description: DATA_MYSQL len 765 prec 0; file_size: DATA_INT len 8 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name PRIMARY, id 0 53, fields 1/7, type 3 root page 512, appr.key vals 168, leaf pages 20, size pages 21 FIELDS: id DB_TRX_ID DB_ROLL_PTR bug_id file_name description file_size -------------------------------------- TABLE: name test_statistics/ims_bughistory, id 0 50, columns 9, indexes 1, appr.rows 5140 COLUMNS: id: DATA_INT len 4 prec 0; bug_id: DATA_INT len 4 prec 0; comment: type 12 len 765 prec 0; creator: DATA_INT len 4 prec 0; creation_date: DATA_INT len 4 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name PRIMARY, id 0 54, fields 1/7, type 3 root page 534, appr.key vals 5140, leaf pages 18, size pages 19 FIELDS: id DB_TRX_ID DB_ROLL_PTR bug_id comment creator creation_date -------------------------------------- TABLE: name test_statistics/ims_bugs, id 0 51, columns 18, indexes 1, appr.rows 933 COLUMNS: id: DATA_INT len 4 prec 0; title: type 12 len 150 prec 0; odt: type 12 len 765 prec 0; type_id: DATA_INT len 4 prec 0; product_id: DATA_INT len 4 prec 0; severity_id: DATA_INT len 4 prec 0; status_id: DATA_INT len 4 prec 0; os_id: DATA_INT len 4 prec 0; assigned_to: DATA_INT len 4 prec 0; creator_id: DATA_INT len 4 prec 0; change_date: DATA_INT len 4 prec 0; creation_date: DATA_INT len 4 prec 0; objective_date: DATA_INT len 4 prec 0; close_date: DATA_INT len 4 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name PRIMARY, id 0 55, fields 1/16, type 3 root page 557, appr.key vals 933, leaf pages 8, size pages 9 FIELDS: id DB_TRX_ID DB_ROLL_PTR title odt type_id product_id severity_id status_id os_id assigned_to creator_id change_date creation_date objective_date close_date -------------------------------------- TABLE: name test_statistics/ims_bugtypes, id 0 52, columns 9, indexes 1, appr.rows 156 COLUMNS: id: DATA_INT len 4 prec 0; order_id: DATA_INT len 4 prec 0; product_id: DATA_INT len 4 prec 0; name: type 12 len 765 prec 0; description: type 12 len 765 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name PRIMARY, id 0 56, fields 1/7, type 3 root page 566, appr.key vals 156, leaf pages 1, size pages 1 FIELDS: id DB_TRX_ID DB_ROLL_PTR order_id product_id name description -------------------------------------- TABLE: name test_statistics/ims_customers, id 0 53, columns 7, indexes 1, appr.rows 3 COLUMNS: id: DATA_INT len 4 prec 0; name: type 12 len 765 prec 0; description: type 12 len 765 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name PRIMARY, id 0 57, fields 1/5, type 3 root page 567, appr.key vals 3, leaf pages 1, size pages 1 FIELDS: id DB_TRX_ID DB_ROLL_PTR name description -------------------------------------- TABLE: name test_statistics/ims_dependencies, id 0 54, columns 6, indexes 1, appr.rows 0 COLUMNS: bug_id: DATA_INT len 4 prec 0; depends_on: DATA_INT len 4 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name PRIMARY, id 0 58, fields 1/4, type 3 root page 568, appr.key vals 0, leaf pages 1, size pages 1 FIELDS: bug_id DB_TRX_ID DB_ROLL_PTR depends_on -------------------------------------- TABLE: name test_statistics/ims_freetext, id 0 55, columns 10, indexes 1, appr.rows 2794 COLUMNS: id: DATA_INT len 4 prec 0; bug_id: DATA_INT len 4 prec 0; text: type 5 len 10 prec 0; action: type 12 len 765 prec 0; creator: DATA_INT len 4 prec 0; creation_date: DATA_INT len 4 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name PRIMARY, id 0 59, fields 1/8, type 3 root page 569, appr.key vals 2794, leaf pages 41, size pages 97 FIELDS: id DB_TRX_ID DB_ROLL_PTR bug_id text action creator creation_date -------------------------------------- TABLE: name test_statistics/ims_mailing, id 0 56, columns 7, indexes 1, appr.rows 6645 COLUMNS: id: DATA_INT len 4 prec 0; user_id: DATA_INT len 4 prec 0; bug_id: DATA_INT len 4 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name PRIMARY, id 0 60, fields 1/5, type 3 root page 452, appr.key vals 6645, leaf pages 17, size pages 18 FIELDS: id DB_TRX_ID DB_ROLL_PTR user_id bug_id -------------------------------------- TABLE: name test_statistics/ims_odt, id 0 57, columns 7, indexes 1, appr.rows 0 COLUMNS: id: DATA_INT len 4 prec 0; bug_id: DATA_INT len 4 prec 0; text: type 5 len 10 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name PRIMARY, id 0 61, fields 1/5, type 3 root page 470, appr.key vals 0, leaf pages 1, size pages 1 FIELDS: id DB_TRX_ID DB_ROLL_PTR bug_id text -------------------------------------- TABLE: name test_statistics/ims_os, id 0 58, columns 8, indexes 1, appr.rows 6 COLUMNS: id: DATA_INT len 4 prec 0; order_id: DATA_INT len 4 prec 0; name: type 12 len 765 prec 0; description: type 12 len 765 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name PRIMARY, id 0 62, fields 1/6, type 3 root page 471, appr.key vals 6, leaf pages 1, size pages 1 FIELDS: id DB_TRX_ID DB_ROLL_PTR order_id name description -------------------------------------- TABLE: name test_statistics/ims_preferences, id 0 59, columns 21, indexes 1, appr.rows 91 COLUMNS: user_id: DATA_INT len 4 prec 0; p1: DATA_INT len 1 prec 0; p2: DATA_INT len 1 prec 0; p3: DATA_INT len 1 prec 0; p4: DATA_INT len 1 prec 0; p5: DATA_INT len 1 prec 0; p6: DATA_INT len 1 prec 0; p7: DATA_INT len 1 prec 0; p8: DATA_INT len 1 prec 0; p9: DATA_INT len 1 prec 0; p10: DATA_INT len 1 prec 0; p11: DATA_INT len 1 prec 0; p12: DATA_INT len 1 prec 0; p13: DATA_INT len 1 prec 0; p14: DATA_INT len 1 prec 0; p15: DATA_INT len 1 prec 0; p16: DATA_INT len 1 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name GEN_CLUST_INDEX, id 0 63, fields 0/20, type 1 root page 472, appr.key vals 91, leaf pages 1, size pages 1 FIELDS: DB_ROW_ID DB_TRX_ID DB_ROLL_PTR user_id p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 -------------------------------------- TABLE: name test_statistics/ims_products, id 0 60, columns 8, indexes 1, appr.rows 18 COLUMNS: id: DATA_INT len 4 prec 0; name: type 12 len 765 prec 0; customer_id: DATA_INT len 4 prec 0; description: type 12 len 765 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name PRIMARY, id 0 64, fields 1/6, type 3 root page 473, appr.key vals 18, leaf pages 1, size pages 1 FIELDS: id DB_TRX_ID DB_ROLL_PTR name customer_id description -------------------------------------- TABLE: name test_statistics/ims_settings, id 0 61, columns 7, indexes 1, appr.rows 9 COLUMNS: id: DATA_INT len 4 prec 0; parameter: type 12 len 765 prec 0; value: type 12 len 765 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name PRIMARY, id 0 65, fields 1/5, type 3 root page 474, appr.key vals 9, leaf pages 1, size pages 1 FIELDS: id DB_TRX_ID DB_ROLL_PTR parameter value -------------------------------------- TABLE: name test_statistics/ims_severities, id 0 62, columns 9, indexes 1, appr.rows 76 COLUMNS: id: DATA_INT len 4 prec 0; product_id: DATA_INT len 4 prec 0; order_id: DATA_INT len 4 prec 0; name: type 12 len 765 prec 0; description: type 12 len 765 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name PRIMARY, id 0 66, fields 1/7, type 3 root page 475, appr.key vals 76, leaf pages 1, size pages 1 FIELDS: id DB_TRX_ID DB_ROLL_PTR product_id order_id name description -------------------------------------- TABLE: name test_statistics/ims_statuses, id 0 63, columns 9, indexes 1, appr.rows 77 COLUMNS: id: DATA_INT len 4 prec 0; product_id: DATA_INT len 4 prec 0; order_id: DATA_INT len 4 prec 0; name: type 12 len 765 prec 0; description: type 12 len 765 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name PRIMARY, id 0 67, fields 1/7, type 3 root page 476, appr.key vals 77, leaf pages 1, size pages 1 FIELDS: id DB_TRX_ID DB_ROLL_PTR product_id order_id name description -------------------------------------- TABLE: name test_statistics/ims_users, id 0 64, columns 25, indexes 2, appr.rows 75 COLUMNS: id: DATA_INT len 4 prec 0; logon: type 12 len 150 prec 0; password: type 12 len 150 prec 0; first_name: type 12 len 765 prec 0; last_name: type 12 len 765 prec 0; email: type 12 len 765 prec 0; active: DATA_INT len 1 prec 0; company: type 12 len 765 prec 0; position: type 12 len 765 prec 0; address: type 12 len 765 prec 0; city: type 12 len 765 prec 0; country: type 12 len 765 prec 0; zipcode: type 12 len 30 prec 0; phone: type 12 len 300 prec 0; fax: type 12 len 300 prec 0; lastbug_id: DATA_INT len 4 prec 0; lastfilter: type 5 len 10 prec 0; mail_new_bugs: DATA_INT len 1 prec 0; mail_all_bugs: DATA_INT len 1 prec 0; view_all_users: DATA_INT len 1 prec 0; item_on_page: DATA_INT len 4 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name PRIMARY, id 0 68, fields 1/23, type 3 root page 477, appr.key vals 75, leaf pages 2, size pages 3 FIELDS: id DB_TRX_ID DB_ROLL_PTR logon password first_name last_name email active company position address city country zipcode phone fax lastbug_id lastfilter mail_new_bugs mail_all_bugs view_all_users item_on_page INDEX: name logon, id 0 69, fields 1/2, type 2 root page 478, appr.key vals 104, leaf pages 1, size pages 1 FIELDS: logon id -------------------------------------- TABLE: name test_statistics/ims_usersgroup, id 0 65, columns 7, indexes 1, appr.rows 5 COLUMNS: id: DATA_INT len 4 prec 0; name: type 12 len 765 prec 0; description: type 12 len 765 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name PRIMARY, id 0 70, fields 1/5, type 3 root page 481, appr.key vals 5, leaf pages 1, size pages 1 FIELDS: id DB_TRX_ID DB_ROLL_PTR name description -------------------------------------- TABLE: name test_statistics/ims_userslinks, id 0 66, columns 8, indexes 1, appr.rows 2197 COLUMNS: id: DATA_INT len 4 prec 0; user_id: DATA_INT len 4 prec 0; product_id: DATA_INT len 4 prec 0; usergroup_id: DATA_INT len 4 prec 0; DB_ROW_ID: DATA_SYS DATA_ROW_ID len 6 prec 0; DB_TRX_ID: DATA_SYS DATA_TRX_ID len 6 prec 0; DB_ROLL_PTR: DATA_SYS DATA_ROLL_PTR len 7 prec 0; INDEX: name PRIMARY, id 0 71, fields 1/6, type 3 root page 482, appr.key vals 2197, leaf pages 6, size pages 7 FIELDS: id DB_TRX_ID DB_ROLL_PTR user_id product_id usergroup_id ----------------------------------- END OF INNODB TABLE MONITOR OUTPUT ==================================
[22 Jun 2005 13:49]
Heikki Tuuri
Hi! This is good news. The tables are there, and contain some rows. How did you recreate the .frm files? They should work if properly recreated. Regards, Heikki
[23 Jul 2005 23: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".