Closed wj-li closed 1 year ago
You should not configure tables that do not exist in actualdatanodes.
You should not configure tables that do not exist in actualdatanodes.
Here's the actual tables.
You should not configure tables that do not exist in actualdatanodes.
It doesn't seem to be in shardingSphereSchema.
You should not configure tables that do not exist in actualdatanodes.
Here's the actual tables.
Yes, you configured a lot of tables that do not exist.
actual-data-nodes: ds0.T_FSN_DATA_$->{2022..2099}$->{['01','02','03','04','05','06','07','08','09','10','11','12']}$->{['01','02','03','04','05','06','07','08','09','10','11','12','13','14','15','16','17','18','19','20','21','22','23','24','25','26','27','28','29','30','31']}
It looks like this issue doesn't have any PRs that need to reach the master branch.
Hello , this issue has not received a reply for several days. This issue is supposed to be closed.
Bug Report
For English only, other languages will not accept.
Before report a bug, make sure you have:
Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot reproduce it on current information, we will close it.
Please answer these questions before submitting your issue. Thanks!
Which version of ShardingSphere did you use?
5.1.1
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-JDBC
Expected behavior
Actual behavior
Here's my config,use Oracle 11g
Reason analyze (If you can)
Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
Example codes for reproduce this issue (such as a github link).