Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MySQL++ - Programming with the C++ API to MySQL
MaxDB - Everything about MaxDB, formerly known as SAP DB
ODBC - ODBC with the MySQL Connector/ODBC driver
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
• Subject: mysql openssl Question
• ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
• Update one field with more fields from another table
• Subject: Getting Identity after INSERT
• ERROR 2002: Can 't connect to local MySQL server through socket
• mysql test 4 1 fails with the gis test
• Subject: MySQL Cluster Software
• Downgrade Mysql from 4 to 3 23
• Mysql 4 0 Oracle Stored Procedure Trigger Conversion
• Can 't access mysql after kernel upgrade
• Executing MySQL Commands From Within C Program
• Comparing and writing out BLOBS
• Subject: Re: Preventing Duplicate Entries
• FULLTEXT query format question
• Strange behavior, Table Level Permission
• Does the binary log enabling affect the MySQL performances?
• mysql:it 's a db not a dbms how it 's possible?!
• mysql have same function mthod as Oracle decode()
 
Subject: InnoDB: Database was not shut down normally!

Subject: InnoDB: Database was not shut down normally!

2007-10-11       - By John Gehring

 Back
I get the following message in the .err file after running my mysql++
application:

071011 10:48:07  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 0 1460518
071011 10:48:07  InnoDB: Starting an apply batch of log records to the
database...
InnoDB: Progress in percents: 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

After running the embedded application, the log does not always contain
messages about "Starting an apply batch of log...". However, the "InnoDB:
Database was not shut down normally!" message is consistently there.

If I access the same database via mysqld, I do not see these messages once I
have opened and closed the database a couple of times. I am shutting down
the mysqld before running the embedded app.

I notice in the mysql++ code that mysql_library_end() is not called, but it
seems that the mysql embedded documentation states that this function should
be called. Can anyone shed some light on this?

I'm running the following (all debug configuration):
mysql++-2.3.2 - built on my machine with Microsoft VC++ 2005, linked
against:
mysql sever 5.1 (using the libmysqld.dll that came with the distribution)