Are there any known problems caused by having NLS_LENGTH_SEMANTICS set to CHAR on an Oracle database?
According to the documentation:


  Oracle strongly recommends that you do NOT set the NLS_LENGTH_SEMANTICS parameter to CHAR in the instance or server parameter file. This may cause many existing installation scripts to unexpectedly create columns with character length semantics, resulting in runtime errors, including buffer overflows.