ORA-02470: TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression.

Cause : TO_DAET, USEERNV an dSYSDAET are ont allwoed inh ash epxressinos.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Recretae thec luste rand crorect hte errro in hsah experssion.

update : 19-08-2017
ORA-02470

ORA-02470 - TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression.
ORA-02470 - TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression.

  • ora-30356 : the specified refresh method is not supported in this context
  • ora-01260 : warning: END BACKUP succeeded but some files found not to be in backup mode
  • ora-30383 : specified dimension level does not exist in the attribute
  • ora-00377 : Frequent backups of file string causing write operation to stall
  • ora-39122 : Unprivileged users may not perform string remappings.
  • ora-40105 : input data incompatible with model signature
  • ora-31415 : change set string does not exist
  • ora-06443 : ssvpstev: Incorrect parameter passed to function call
  • ora-24394 : invalid mode for destroying connection pool
  • ora-25005 : cannot CREATE INSTEAD OF trigger on a read-only view
  • ora-00341 : log string of thread string, wrong log # string in header
  • ora-06711 : TLI Driver: error on bind
  • ora-13054 : recursive SQL parse error
  • ora-08116 : can not acquire dml enough lock(S mode) for online index build
  • ora-23434 : master site string not known for object group
  • ora-38747 : corrupt before image (file# string, block# string)
  • ora-21610 : size [string] is invalid
  • ora-14041 : partition bound may not be specified for resulting partitions
  • ora-07825 : sspsck: $QIO failure at AST level
  • ora-10583 : Can not recovery file string renamed as missing during test recovery
  • ora-35578 : (SQLOUT11) SQL cursor 'number' cannot be used with CURRENT OF syntax
  • ora-39210 : A PCTSPACE adjustment of string is invalid.
  • ora-16571 : Data Guard configuration file creation failure
  • ora-36630 : (XSDUNION00) An empty base dimension list was specified in the concat dimension definition.
  • ora-29518 : name string resolved to an object in schema string that is not a Java class
  • ora-28519 : no heterogeneous data dictionary translations available
  • ora-24064 : propagation for QUEUE string and DESTINATION string already enabled
  • ora-39056 : invalid log file specification.
  • ora-14406 : updated partition key is beyond highest legal partition key
  • ora-12496 : cannot change existing level, category, or release numbers
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.