Insertion Failure with BLOB Columns

## Bug Report

**For English only**, other languages will not accept.

Before report a bug, make sure you have:

- Searched open and closed [GitHub issues](https://github.com/apache/shardingsphere/issues).
- Read documentation: [ShardingSphere Doc](https://shardingsphere.apache.org/document/current/en/overview).

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?
v5.5.1

### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-JDBC

### Expected behavior
insert success

### Actual behavior
insert failure

### Reason analyze (If you can)
I know it. I can fix this bug, so create this issue. Actually, I already fixed it in my project.

### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
SQL like this:
insert into my_user(id,user_name,addr) values(?,?,?) ::: [122401, 测试blob, java.io.ByteArrayInputStream@685f56ef]

addr is blob type in oracle

### Example codes for reproduce this issue (such as a github link).
I will describe it in detail in the following section

Start with the ShardingSphere-JDBC insert path for the provided SQL and an Oracle BLOB column, using the reported ByteArrayInputStream value as the reproduction case. Confirm the failure and trace the insertion handling; done means the insert succeeds with the BLOB value.

Written by the indexing model from the issue text.