Tweeted twitter.com/StackDBAs/status/655020241207037952
2 added 8 characters in body
source | link

I've always thought that anyone using a database where NLS_LENGTH_SEMANTICSNLS_LENGTH_SEMANTICS set to BYTEBYTE when using a multi-byte character set needed their heads examined, but recently a customer of ours said that they had experienced problems applying Oracle patches on databases where NLS_LENGTH_SEMANTICSNLS_LENGTH_SEMANTICS is set to CHARCHAR. Is there anything to this? Is it a known problem?

I've always thought that anyone using a database where NLS_LENGTH_SEMANTICS set to BYTE when using a multi-byte character set needed their heads examined, but recently a customer of ours said that they had experienced problems applying Oracle patches on databases where NLS_LENGTH_SEMANTICS is set to CHAR. Is there anything to this? Is it a known problem?

I've always thought that anyone using a database where NLS_LENGTH_SEMANTICS set to BYTE when using a multi-byte character set needed their heads examined, but recently a customer of ours said that they had experienced problems applying Oracle patches on databases where NLS_LENGTH_SEMANTICS is set to CHAR. Is there anything to this? Is it a known problem?

1
source | link

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

I've always thought that anyone using a database where NLS_LENGTH_SEMANTICS set to BYTE when using a multi-byte character set needed their heads examined, but recently a customer of ours said that they had experienced problems applying Oracle patches on databases where NLS_LENGTH_SEMANTICS is set to CHAR. Is there anything to this? Is it a known problem?