Let me ask you one more question.
After testing your program, it appears that UNICODE data in the CLOBs property column is not converted correctly.
His issue has not been resolved, so we are delaying our product purchase decision. Please check.
You are using dictionary mode or non-dictionary mode?
How about the whole database size? If you can send all datafiles to us, it may save time.
I used dictionary mode.
We'll compress and send the entire data.
Only the “tab_board” table breaks up characters.
It seems that the characters are not broken and are processed normally.
What are the procedures to purchase a product with a modified version of the problem?
Please download SQuirrel softwarehttps://db.apache.org/ derby/integrate/SQuirreL_ Derby.html
Connect to prm dul local derby database, by directory $PRM/dbinfo/YOUR_DB_NAME( have to close prm-dul software first, otherwise connect will conflict, there is no password or account required.
Select * from app.idul_col where idul_name like '%SYS_NC00%';
Delete from app.idul_col where idul_name like '%SYS_NC00%';
Then close SQuirrel, and retry prm dul
Connect to prm dul local derby database, by directory $PRM/dbinfo/YOUR_DB_NAME( have to close prm-dul software first, otherwise connect will conflict, there is no password or account required.
Select * from app.idul_col where idul_name like '%SYS_NC00%';
Delete from app.idul_col where idul_name like '%SYS_NC00%';
Then close SQuirrel, and retry prm dul
DBRECOVER Recovery Options
For Oracle incidents, start with the DBRECOVER for Oracle trial to verify table visibility, row previews, and export readiness on copied datafiles. For MySQL and InnoDB incidents, DBRECOVER for MySQL is free software and can inspect.ibd files, ibdata1, and database directories locally.
When the case is urgent, preserve the original files first, work from copies, and contact paid emergency support with the database version, platform, error messages, file list, and recovery objective.