Oracle Database Errors or Warnings from Error ORA-34656 to ORA-34804
ORA-34656: (MXSQL24) Additional WHERE clause conditions with CURRENT OF <cursor name> syntax
Cause: A SQL UPDATE or DELETE statement tried to use the CURRENT of <cursor name> syntax with a WHERE clause containing multiple conditions.
Action: When using the CURRENT OF <cursor name> syntax make sure it is the only condition in the WHERE clause.
ORA-34719: (NLSCHARSET03) Character data loss in NTEXT/TEXT conversion
Cause: When character set conversion happens between TEXT and NTEXT either implicitly or explicitly, some characters are lost due to no mapping characters in the destination character set.
Action: Make sure all the characters can be mapped to destination character set or set NLS_NCHAR_CONV_EXCP to be FALSE. Note: This message is the OLAP equivalent of ORA-12713.
ORA-34722: (NLSCHARSET05) CAUTION: Character data loss in character set conversion from string to string
Cause: Some operation required a string to be converted into a different character set, but the string contained characters that didn’t exist in the new character set.
Action: Choose different character sets.
ORA-34726: (NLSCHARSET06) CAUTION: String truncated during character set conversion from string to string
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.
ORA-34731: (NLSSORT01) ‘number’ is not a valid NLS_SORT specification.
Cause: An unrecognized NLS_SORT value was specified in the SORT command or the SORT, SORTLINES or UNIQUELINES function.
Action: Specify a supported NLS_SORT value.
ORA-34738: (NOUPDATE) A severe problem has been detected. Analytic workspace operations have been disabled.
Cause: A previous fatal error has marked the session so that it cannot perform any UPDATEs
Action: Start a new session
ORA-34761: (NXHANDLEALLO) A decimal overflow occurred during an ALLOCATE operation. The results are not reliable.
Cause: While performing an ALLOCATE, a decimal overflow occurred
Action: Correct the data or use a higher precision datatype
ORA-34796: (OCI08) SQL host variable number cannot be bound.
Cause: The data type of the host variable is not supported.
Action: Specify only variables of supported types as host variable names.
ORA-34802: (OCI11) OLAP OCI operation caused ROLLBACK past an UPDATE of an attached analytic workspace. Current operation canceled.
Cause: ROLLBACK past the UPDATE of one of the attached Analytic Workspaces was called. The current operation is aborted, and the Analytic Workspace detached.
Action: Change the called SQL procedure to avoid the ROLLBACK
ORA-34804: (OCI12) The value of SQL host variable number is too long. Use the WIDE keyword for columns that may exceed number bytes.
Cause: The host variable had a text value longer than the maximum SQL VARCHAR length
Action: Use the WIDE keyword in the host variable specification, e.g. :WIDE OLAP_object_name
Above are list of Oracle Database Errors or Warnings from Error ORA-34656 to ORA-34804 received while performing certain operation against Oracle Database or related products.
What are atOracle Database Error Messages?
Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Dabase Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.
Hope this was helpful.
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.