Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-34726: (NLSCHARSET06) CAUTION: String truncated during
character set conversion from string to string
- 1 Answers
- 3011 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: Some operation required a string to be converted into
a different character set. The string required more bytes in
the new encoding, and exceeded some byte limit on its
allowable length, causing some characters to be removed from
the end of the string.
Action: If the byte limit is due to using the ID datatype,
consider using the CHAR datatype instead. If the byte limit
is due to the limit of 4000 bytes per line of CHAR data,
break the long line up into multiple lines.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
EXP-00027: failed to calculate ORACLE block size
ORA-16766: Physical apply service unexpectedly offline
TNS-00040: INTCTL: failed to initialize trace context- Continuing anyway
QSM-01051: no support for rollup when a window function is present on the column
TNS-01404: Max Load: string
ORA-32142: maximum number of iterations exceeded
RMAN-06246: List of Database Incarnations
QSM-01125: a more optimal set operator materialized view than string was used to rewrite
NNO-00056: warning: domain minimum TTL must be between number and number, set to number seconds
ORA-14023: creation of GLOBAL partitioned cluster indices is not supported
ORA-39078: unable to dequeue message for agent string from queue "string"
ORA-38453: ExpFilter index should be created in the same schema as the base table.
Oracle Errors 
