ORA-25457: evaluation function string returns failure

Cause : The speicfied evlauation ufnction erturned afailured uring eavluation ,causinge valuatino to terimnate.

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

Check agruments ot evaluaet and rerty.

update : 26-04-2017

ORA-25457 - evaluation function string returns failure
ORA-25457 - evaluation function string returns failure

  • ora-27458 : A program of type PLSQL_BLOCK cannot have any arguments.
  • ora-26015 : Array column string in table string is not supported by direct path
  • ora-07577 : no such user in authorization file
  • ora-07643 : smsalo: SMSVAR is invalid
  • ora-37003 : (AWLISTALL01) number readers
  • ora-28368 : cannot auto-create wallet
  • ora-31687 : error creating worker process string with worker id string
  • ora-24756 : transaction does not exist
  • ora-39761 : stream reset required before loading this stream again
  • ora-01077 : background process initialization failure
  • ora-01531 : a database already open by the instance
  • ora-28031 : maximum of string enabled roles exceeded
  • ora-16773 : error starting Redo Apply
  • ora-13838 : invalid ADDRESS value
  • ora-36806 : (XSTBLFUNC03) The OLAP_TABLE function refers to an invalid ADT attribute: string.
  • ora-16411 : ONDEMAND archival requires active managed recovery operation
  • ora-28165 : proxy 'string' may not specify password-protected role 'string' for client 'string'
  • ora-09216 : sdnfy: bad value 'string' for parameter string
  • ora-14117 : partition resides in offlined tablespace
  • ora-37101 : (XSVPART01) Partitioning information can only be given for variables dimensioned by a PARTITION TEMPLATE.
  • ora-30072 : invalid time zone value
  • ora-01904 : DATAFILE keyword expected
  • ora-27501 : IPC error creating a port
  • ora-04095 : trigger 'string' already exists on another table, cannot replace it
  • ora-33265 : (DBERRBSZ) Analytic workspace string cannot be opened. Tablespace blocksize number does not match database cache size number.
  • ora-38471 : ROWIDs for table aliases cannot be null
  • ora-25118 : invalid DUMP DATAFILE/TEMPFILE option
  • ora-33050 : (XSAGDNGL24) AGGMAP workspace object cannot be used to aggregate workspace object, because it is defined in a different analytic workspace.
  • ora-13225 : specified index table name is too long for a spatial index
  • ora-16533 : inconsistent Data Guard broker state
  • 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.