You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2020/12/08 04:17:33 UTC

[GitHub] [shardingsphere] tristaZero edited a comment on issue #8513: Please help to check whether it is a bug or a configuration error?

tristaZero edited a comment on issue #8513:
URL: https://github.com/apache/shardingsphere/issues/8513#issuecomment-739649399


   Hi Which SQL causes the following exception?
   
   > [Err] 10002 - 2Unknown exception: [Can not route tables for [PROFILING], please make sure the tables are in same schema.]
   
   Given the log you provided, I guess `SET PROFILING=1` ran well, didn't it?
   
   ```
   [INFO ] 23:45:25.746 [ShardingSphere-Command-0] ShardingSphere-SQL - Logic SQL: SET PROFILING=1;
   [INFO ] 23:45:25.746 [ShardingSphere-Command-0] ShardingSphere-SQL - SQLStatement: MySQLSetStatement()
   [INFO ] 23:45:25.746 [ShardingSphere-Command-0] ShardingSphere-SQL - Actual SQL: bpm_data_1 ::: SET PROFILING=1;
   [INFO ] 23:45:25.746 [ShardingSphere-Command-0] ShardingSphere-SQL - Actual SQL: bpm_data_2 ::: SET PROFILING=1;
   [INFO ] 23:45:25.749 [ShardingSphere-Command-1] ShardingSphere-SQL - Logic SQL: SHOW STATUS
   ```


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org