Hi,
Perhaps try to (excuse me if my Perl is rusty)
$qxid = $dbh->quote($xid)
$sth = $dbh->prepare("XA ROLLBACK " . $xid)
$sth->execute();
If that doesn't work, and you are familiar with C, you could make a
modification to the server so that after it initializes InnoDB to iterate
and rollback all
Hi,
i don't get rid of this :-)
I use mariadb "10.0.24+maria-1~trusty" on Ubuntu 14.04 and i tried to solve the
situation by writing this hacky perl script :-)
The problem seems to be a bug. From my point of view the only solution might be
to completely restore a existing mysqldump backup.
Hi, Marc!
While not exactly user-friendly, you can still run
$ mysql -e 'xa recover'|hexdump -C
You'll see hex data there.
Regards,
Sergei
On Feb 22, Marc Schöchlin wrote:
> Hi Justin,
>
> how can i get the hex representation of the the transaction identification
> strings?
> ("XA RECOVER
Hi Justin,
how can i get the hex representation of the the transaction identification
strings?
("XA RECOVER CONVERT XID" seems only to be available on MySQL 5.7)
Regards
Marc
Am 22.02.2016 um 15:27 schrieb Justin Swanhart:
> Hi,
>
> I have not tested this, but I think you will need to convert
Hi,
I have not tested this, but I think you will need to convert the strings to
hex then do:
xa rollback 0xabcdef <-- where 0xabcdef is the hex representation of the
string.
--Justin
On Sat, Feb 20, 2016 at 5:53 AM, Marc Schöchlin wrote:
> Hi,
>
> i currently have the
Hi,
i currently have the situation that i cannot modify tables/indices beaus of XA
transactions which are in progress.
mysql://root@localhost:/(none) - 11:37:55 > xa recover;
+--+--+--+--+
| formatID
6 matches
Mail list logo