Rollback warning?!

RT Users
1

This is a new message for me, so I thought I would simply ask the list
as to what this means:

[Tue Oct 12 11:35:38 2004] [error] [client 172.1.1.1] FastCGI: server
“/opt/rt3/bin/mason_handler.fcgi” stderr: DBD::mysql::db rollback
failed: Warning: Some non-transactional changed tables couldn’t be
rolled back at
/usr/lib/perl5/site_perl/5.8.3/DBIx/SearchBuilder/Handle.pm line 719.,
referer: https://rt.prvt.net/rt3/Ticket/Display.html?id=629

I know what rollback is, which is pretty nice, but I didn’t know it was
available, and, hence, I don’t know how to implement it in order to get
rid of the warnings.

Any help would be appreciated!

Thanks!
-Rich

2

This is a new message for me, so I thought I would simply ask the list
as to what this means:

[Tue Oct 12 11:35:38 2004] [error] [client 172.1.1.1] FastCGI: server
“/opt/rt3/bin/mason_handler.fcgi” stderr: DBD::mysql::db rollback
failed: Warning: Some non-transactional changed tables couldn’t be
rolled back at
/usr/lib/perl5/site_perl/5.8.3/DBIx/SearchBuilder/Handle.pm line 719.,
referer: https://rt.prvt.net/rt3/Ticket/Display.html?id=629

I know what rollback is, which is pretty nice, but I didn’t know it was
available, and, hence, I don’t know how to implement it in order to get
rid of the warnings.

If you want the tables that are “non-transactional” to be
transactional, you will need to convert them from ISAM to INNODB
type tables. Check out http://www.mysql.com to see how to do that.
I don’t remember =8^).

3

Armed with that information, I found a good article that handles the
pros and cons as well as the steps to convert the tables.

http://builder.com.com/5100-6388-1058872.html

MySQL isn’t liking the syntax… I’ll keep digging at it. :slight_smile:

Thanks!
-Rich

Scott T. Hildreth wrote:

4

What tables do you have that aren’t InnoDB?\On Oct 12, 2004, at 4:07 PM, Rich West wrote:

Armed with that information, I found a good article that handles the
pros and cons as well as the steps to convert the tables.

http://builder.com.com/5100-6388-1058872.html

MySQL isn’t liking the syntax… I’ll keep digging at it. :slight_smile:

Thanks!
-Rich

Scott T. Hildreth wrote:

If you want the tables that are “non-transactional” to be
transactional, you will need to convert them from ISAM to INNODB type
tables. Check out http://www.mysql.com to see how to do that.
I don’t remember =8^).

The rt-users Archives

Be sure to check out the RT wiki at http://wiki.bestpractical.com

5

This particular system has been upgraded over the years from rt 1.x to
the current release.

All of the tables were MyISAM.

I just upgraded the tables to InnoDB (ALTER TABLE TYPE=InnoDB)
and all is well with the world of RT.

-Rich

6

Rich West wrote:

Armed with that information, I found a good article that handles the
pros and cons as well as the steps to convert the tables.

FYI

MySQL manual is best source of the info about MySQL
16.7.2 Converting MyISAM Tables to InnoDB

http://dev.mysql.com/doc/mysql/en/Converting_tables_to_InnoDB.html