Oracle Database Errors or Warnings from Error ORA-02471 to ORA-02479



ORA-02471: SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly used in hash expre\ssion.
Cause: SYSDATE, UID, USER, ROWNUM, or LEVEL are not allowed in hash expression\s.
Action: Recreate the cluster and remove the offending keywords.
ORA-02472: PL/SQL functions not allowed in hash expressions
Cause: A PL/SQL function was used in the hash expression.
Action: Recreate the cluster and remove the PL/SQL function.
ORA-02473: Error while evaluating the cluster’s hash expression.
Cause: An error occurred while evaluating the clusters hash expression.
Action: Correct the query and retry.

ORA-02474: Fixed hash area extents used (string) exceeds maximum allowed (string)
Cause: The number of extents required for creating the fixed hash area exceeds the maximum number allowed.
Action: Reduce the number of extents required by increasing the extent allocation sizes within the STORAGE clause.
ORA-02475: maximum cluster chain block count of string has been exceeded
Cause: The number of blocks in a cluster chain exceeds the maximum number allowed.
Action: Increase SIZE parameter in CREATE CLUSTER statement or reconsider suitability of cluster key.
ORA-02476: can not create index due to parallel direct load on table
Cause: A parallel direct load is occurring to the specified table.
Action: Retry statement after load is complete.

ORA-02477: can not perform parallel direct load on object string
Cause: A parallel direct load is not possible because an index is is being created on the table.
Action: Retry load after index creation is complete.
ORA-02478: merge into base segment would overflow MAXEXTENTS limit
Cause: Merge of temporary segment into base segment failed because MAXEXTENTS was larger than the total in the temp and base segments
Action: Use a larger value for MAXEXTENTS on the base segment or make the extents in the temporary segments larger
ORA-02479: error while translating file name for parallel load
Cause: An invalid file name was specified to load data into.
Action: Specify a valid database file.

Above are list of Oracle Database Errors or Warnings from Error ORA-02471 to ORA-02479 received while performing certain operation against Oracle Database or related products.

What are Oracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database.  Each Oracle Database 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.

SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.


SQL Server Errors or Failures from Error: 15021 to Error: 15050



Error: 15021, Severity: 16, Invalid value given for parameter %s. Specify a valid parameter value.
Error: 15022, Severity: 16, The specified user name is already aliased.
Error: 15023, Severity: 16, User, group, or role ‘%s’ already exists in the current database.
Error: 15025, Severity: 16, The server principal ‘%s’ already exists.
Error: 15026, Severity: 16, Logical device ‘%s’ already exists.

Error: 15028, Severity: 16, The server ‘%s’ already exists.
Error: 15032, Severity: 16, The database ‘%s’ already exists. Specify a unique database name.
Error: 15033, Severity: 16, ‘%s’ is not a valid official language name.
Error: 15034, Severity: 16, The application role password must not be NULL.

Error: 15036, Severity: 16, The data type ‘%s’ does not exist or you do not have permission.
Error: 15040, Severity: 16, User-defined error messages must have an ID greater than 50000.
Error: 15041, Severity: 16, User-defined error messages must have a severity level between 1 and 25.
Error: 15042, Severity: 10, The @with_log parameter is ignored for messages that are not us_english version.
Error: 15043, Severity: 16, You must specify ‘REPLACE’ to overwrite an existing message.
Error: 15044, Severity: 16, The type “%s” is an unknown backup device type. Use the type “disk” or “tape”.
Error: 15045, Severity: 16, The logical name cannot be NULL.
Error: 15046, Severity: 16, The physical name cannot be NULL.
Error: 15048, Severity: 10, Valid values of the database compatibility level are %d, %d, or %d.
Error: 15049, Severity: 11, Cannot unbind from ‘%s’. Use ALTR TABLE DROP CONSTRAINT.
Error: 15050, Severity: 11, Cannot bind default ‘%s’. The default must be created using the CREATE DEFAULT statement.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.