all things cbl

I think I have it figured out. It was a problem with the InnoDB from my 4.1.x installation when I copied it over to my 5.0.15 install. I dumped my InnoDB data files, logs, and recreated them on startup (on the new box), then did a restore from a dump of the RT (ticketing system) database. This seemed to fix the problem.

Weird thing was, before I dumped my InnoDB data files, I tried dumping the database and restoring it from dump. No go. I couldn’t get it to insert the first row in the first table.. So I did the above. Oh and then I tweaked some settings on my InnoDB part of my.cnf. Here’s some of them for future reference. Oh and I was able to recreate my InnoDB files correctly (i had forgot about the auto-extend file so one of my innodb data files before got up to 1102MB before I created a new one.. so now I have 3×1024MBs and a 512MB that can autoextend to 1024MB max.. much cleaner)

innodb_log_files_in_group = 3
innodb_log_file_size = 256M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_log_archive = 0
innodb_buffer_pool_size = 1G
innodb_additional_mem_pool_size = 32M
innodb_file_io_threads = 4
innodb_thread_concurrency = 16
innodb_lock_wait_timeout = 60

Anyway, tonight will be the test. Shall it work? Shall everything work? I sure hope so. I’m still running 5.0.17 (CVS snapshot from last night).. I think I’ll keep it around for the time being.

Stay tuned.. More later..