ORA-24180: invalid transformation expression, the transformation expression does not evaluate to the target type/attribute

Cause : The trasnformatino expresison doesn ot evalaute to teh targett ype or hte targe ttype's psecifieda ttribut.e

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

Providev alid trnasformatoin expression whihc evaluaets to th etarget ytpe or teh targett ype's sepcified tatribute.

update : 20-09-2017
ORA-24180

ORA-24180 - invalid transformation expression, the transformation expression does not evaluate to the target type/attribute
ORA-24180 - invalid transformation expression, the transformation expression does not evaluate to the target type/attribute

  • ora-36160 : (XSMXAGGR04) You cannot use string on scalar VARIABLE workspace object.
  • ora-06960 : Failed to access log file
  • ora-15083 : failed to communicate with ASMB background process
  • ora-25215 : user_data type and queue type do not match
  • ora-40284 : model does not exist
  • ora-25000 : invalid use of bind variable in trigger WHEN clause
  • ora-06978 : X.25 Driver: Too many callback tries
  • ora-18010 : command missing mandatory CATEGORY keyword
  • ora-32802 : value for string must be string
  • ora-09882 : sstasfre/sstasdel: shmctl error, unable to remove tas shm page
  • ora-06580 : Hash Join ran out of memory while keeping large rows in memory
  • ora-12720 : operation requires database is in EXCLUSIVE mode
  • ora-31453 : invalid value string for parameter, expecting: Y, N, or NULL
  • ora-13271 : error allocating memory for geometry object
  • ora-12422 : max policies exceeded
  • ora-33454 : (ESDREAD07) Discarding compiled code for workspace object because number is now string workspace object, whereas it was string workspace object when the code was compiled.
  • ora-01574 : maximum number of concurrent transactions exceeded
  • ora-12437 : invalid policy option: string
  • ora-38417 : attribute set string does not exist
  • ora-31232 : DBMS_LDAP: invalid MOD_PROPERTY_SET
  • ora-13502 : Cannot rename SYSAUX tablespace
  • ora-09807 : Conversion of label from string to binary failed.
  • ora-39307 : operation is illegal without an initial clone
  • ora-36766 : (XSAGGCNTMOVE04) workspace object cannot be used as an AGGCOUNT because it has an AGGCOUNT.
  • ora-28101 : policy already exists
  • ora-12612 : TNS:connection is busy
  • ora-26510 : materialized view name: 'string' is greater than max. allowed length of string bytes
  • ora-39210 : A PCTSPACE adjustment of string is invalid.
  • ora-27002 : function called with invalid device structure
  • ora-32159 : Cannot set prefetch options for a null Type
  • 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.