terrymanu commented on issue #26056:
URL:
https://github.com/apache/shardingsphere/issues/26056#issuecomment-3637909397
## Issue Understanding
- Environment: ShardingSphere-JDBC 5.2.0, Oracle 11g, Spring Boot 2.2.5.
Query select count(*) from tbclient1 a where a.client_type in(?,?,?) fails with
“query execution count reported null exception” (only a screenshot, no stack
trace text).
- Config: Screens show ds0/ds1 sharding data sources; exact sharding rules
are not provided in text.
## Root Cause
- Cannot determine yet: missing full exception stack, SQL rewrite/route
logs, driver version, and sharding rules. The message alone doesn’t tell
whether it’s parameter binding, empty routing, datasource config, or a 5.2.0
defect.
## Issue Analysis
- 5.2.0 is old; Oracle support has had fixes since. With no stack trace
and no textual sharding/encrypt/table rules, it’s not reproducible.
- The IN (?,?,?) requires all parameters to be non-null, matching column
types, and SQL Show enabled to see the actual routed SQL.
- Need to know if sharding keys, broadcast tables, or readwrite-splitting
affect this table.
## Conclusion / Next Steps
- Current info is insufficient to decide usage issue vs. bug. Please
provide:
1. Full exception stack trace (including Caused by).
2. Oracle JDBC driver version.
3. Text version of datasource/sharding YAML (especially tbclient1’s
sharding key/rule and readwrite-splitting).
4. Actual routed SQL and parameter values/types with props.sql-show:
true enabled.
5. If the table is unsharded, confirm if only a single datasource is
configured.
After this, we can analyze further. If possible, also retest on the
latest release to rule out fixed issues.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
