# GRA\_\*.log

**URL:** <https://forums.percona.com/t/gra-log/6450>\
**Category:** Percona XtraDB Cluster 5.x\
**Created:** [July 9, 2018, 1:41pm UTC](https://forums.percona.com/t/gra-log/6450 "2018-07-09T13:41:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vietcgi](https://avatars.discourse-cdn.com/v4/letter/v/91b2a8/32.png) [@vietcgi](https://forums.percona.com/u/vietcgi)\
**Post date:** [July 9, 2018, 1:41pm UTC](https://forums.percona.com/t/gra-log/6450/1 "2018-07-09T13:41:00Z")

</div>

Hi there,

We have a cluster of 3 servers and I’ve found quite a few GRA files with the debug logs below. The query looks very abnormal “DROP TABLE `#Tableau\_01\_sid\_003CB13E\_1\_Conn”. We dont’ have any tables called Tableau in our exchange database. I wonder how to get rid of those errors.

Thanks

/_!50530 SET @@SESSION.PSEUDO\_SLAVE\_MODE=1_/;  
/_!50003 SET @OLD\_COMPLETION\_TYPE=@@COMPLETION\_TYPE,COMPLETION\_TYPE=0_/;  
DELIMITER /_!_/;

# at 4

#140113 11:12:42 server id 3 end\_log\_pos 120 CRC32 0xe6f1f7fe Start: binlog v 4, server v 5.6.15-log created 140113 11:12:42 at startup  
ROLLBACK/_!_/;  
BINLOG ’  
qjrUUg8DAAAAdAAAAHgAAAAAAAQANS42LjE1LWxvZwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA  
AAAAAAAAAAAAAAAAAACqOtRSEzgNAAgAEgAEBAQEEgAAXAAEGggAAAAICAgCAAAACgoKGRkAAf73  
8eY=  
'/_!_/;

# at 120

#140113 11:12:43 server id 3 end\_log\_pos 143 CRC32 0x26e85337 Stop

# at 143

#180709 11:35:53 server id 2 end\_log\_pos 114 CRC32 0x60746365 Query thread\_id=3977534 exec\_time=0 error\_code=0  
use `exchange`/_!_/;  
SET TIMESTAMP=1531161353/_!_/;  
SET @@session.pseudo\_thread\_id=3977534/_!_/;  
SET @@session.foreign\_key\_checks=1, @@session.sql\_auto\_is\_null=0, @@session.unique\_checks=1, @@session.autocommit=1/_!_/;  
SET @@session.sql\_mode=1436549120/_!_/;  
SET @@session.auto\_increment\_increment=1, @@session.auto\_increment\_offset=1/_!_/;  
/_!\C utf8 //!_/;  
SET @@session.character\_set\_client=33,@@session.collation\_connection=33,@@session.collation\_server=224/_!_/;  
SET @@session.lc\_time\_names=0/_!_/;  
SET @@session.collation\_database=DEFAULT/_!_/;  
DROP TABLE `#Tableau\_01\_sid\_003CB13E\_1\_Conn  
/_!_/;  
SET @@SESSION.GTID\_NEXT= ‘AUTOMATIC’ /\* added by mysqlbinlog _/ /_!\*/;  
DELIMITER ;

# End of log file

/_!50003 SET COMPLETION\_TYPE=@OLD\_COMPLETION\_TYPE_/;  
/_!50530 SET @@SESSION.PSEUDO\_SLAVE\_MODE=0_/;

---

<div class="post-metadata">

**Author:** ![przemek](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/przemek/32/3_2.png) [@przemek](https://forums.percona.com/u/przemek)\
**Post date:** [August 10, 2018, 9:08am UTC](https://forums.percona.com/t/gra-log/6450/2 "2018-08-10T09:08:52Z")

</div>

This is result of how DDLs are replicated in Galera. Even if you do DDL against a non existing table, so ineffective on the node you work on, it will still get replicated to the other nodes, and these nodes will produce GRA files due to being unable to apply those DDLs.