Non-UTF8 DADs and PlsqlTransferMode RAW

Question

Hey, so here's our situation. Oracle DB 10g and OAS 10g 9.0.4.2. We have a lot of DAD-based PL/SQL apps, with DADs set up per language. Some time ago, we converted the databases to UTF8. Everything worked pretty much fine, except for all the errors about language conversion in our logs. We've been getting our app developers/site managers to slowly move over to using new UTF8 DADs, but many of the old language-specific DADs are in use.
Well, some of the pages had the problem with mismatched content length (see Note:244544.1) but no one saw that as a big deal - until this weekend, when we moved over to a new load balancer, and the LB is waiting for the page to "finish" before passing it on to the user, making all our non-UTF8 DAD apps hang when using non-English languages. Big production problem.
So the docs seem to say that the magic solution for me is to set all my non-UTF8 DADs to PlsqlTransferMode RAW. I've tested this and it resolves the problem at hand, but it scares all the application managers here who worry that it'll have some kind of side effects.
So question to all - in a reasonably complex environment, with a heavily international Internet user base (wide variety of browsers, character settings, etc) - could there be any unforseen impact from changing from CHAR to RAW for the transfer mode? Or should it be utterly transparent to the end user, given that all the data is stored in the DB in utf8?
Thanks,
Ernest

Answer 1

There is something similar before:
wwv_flow.accept was not found on this server
what lead to some DAD changes....revert is helping ?
Regards,
Damir