We are preparing a database characterset migration to al32utf8 on an oracle 19.23 database using the dmu tool version 23.1.
After scanning the database the dmu tool detects several issues in our application schemes which we are all able to solve.
In the Oracle maintained schema's we only have issues in the apex schema (version 23.2)

Some of these issues we can solve. For instance the data in wwv_flow_debug_messages we can delete.
But there are some tables in which we can not solve the issues.
For instance wwv_flow_jet_charts.

But I notice a difference in behaviour in my application tables and in the oracle maintained schema's.
The data in wwv_flow_jet_charts needs conversion, but I can not start the conversion because of the fact that I have

How can we solve this?
Thanks in advance
Kind Regards Erik