My mistake - even on older databases like 19c, if created as unicode format, fails too... didn't have right now a 18/12 with AL32UTF8 to test, but I believe would be the same problem.
Any thoughts on this ? We would like to use unicode databases alongside the classic ones ... but that error will stop us from succeed. It´s not feaseble to have dual programs for each database kind.