# Possible Bug : INNODB=FORCE ambiguous option

**URL:** <https://forums.percona.com/t/possible-bug-innodb-force-ambiguous-option/2289>\
**Category:** Percona XtraBackup\
**Created:** [September 11, 2012, 4:10pm UTC](https://forums.percona.com/t/possible-bug-innodb-force-ambiguous-option/2289 "2012-09-11T16:10:40Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![niljoshi](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/niljoshi/32/16889_2.png) [@niljoshi](https://forums.percona.com/u/niljoshi)\
**Post date:** [September 18, 2012, 1:02am UTC](https://forums.percona.com/t/possible-bug-innodb-force-ambiguous-option/2289/2 "2012-09-18T01:02:30Z")

</div>

Hi Allen,

It seems, you are hitting this bug. [URL][https://bugs.launchpad.net/percona-xtrabackup/+bug/528752[/URL]](https://bugs.launchpad.net/percona-xtrabackup/+bug/528752%5B/URL%5D)  
As It’s not fixed yet, you can use workaround for now by adding “loose-innodb=force” in my.cnf.

Thanks.

---

_[View the full topic](https://forums.percona.com/t/possible-bug-innodb-force-ambiguous-option/2289)._
