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 : 19-08-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-09779 : snyGetPort: failure to allocate a port.
  • ora-25207 : enqueue failed, queue string.string is disabled from enqueueing
  • ora-13368 : simple polygon type has more than one exterior ring
  • ora-14023 : creation of GLOBAL partitioned cluster indices is not supported
  • ora-27301 : OS failure message: string
  • ora-08185 : Flashback not supported for user SYS
  • ora-32772 : BIGFILE is invalid option for this type of tablespace
  • ora-13051 : failed to initialize spatial object
  • ora-01919 : role 'string' does not exist
  • ora-06530 : Reference to uninitialized composite
  • ora-33078 : (XSAGDNGL39) In AGGMAP workspace object, the hierarchy dimension QDR workspace object must refer to a dimension.
  • ora-12638 : Credential retrieval failed
  • ora-09208 : sftcls: error closing file
  • ora-09839 : removeCallback: callback port is not in the callback set.
  • ora-32733 : Error occurred when executing Parallel Oradebug
  • ora-14601 : Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template
  • ora-14039 : partitioning columns must form a subset of key columns of a UNIQUE index
  • ora-30435 : job_queue_processes must be non-zero in order to refresh summaries
  • ora-35017 : (QFCHECK06) The Analytic Workspace and EIF file definitions of workspace object have different partitioning methods.
  • ora-19283 : XQ0031 - It is a static error if the version number specified in a version declaration is not supported by the implementation.
  • ora-12619 : TNS:unable to grant requested service
  • ora-10941 : trace name context forever
  • ora-37023 : (XSMLTUPD01) Object workspace object cannot be updated without dimension workspace object.
  • ora-26738 : %s 'string' is not empty
  • ora-14002 : only one GLOBAL clause may be specified
  • ora-00113 : protocol name string is too long
  • ora-02175 : invalid rollback segment name
  • ora-02351 : internal error: string
  • ora-36912 : (XSAGDNGL48) In AGGMAP workspace object, MODEL workspace object cannot be simultaneous.
  • ora-39500 : failed to notify CRS of a Startup/Shutdown event for database "string", instance "string" (ignored)
  • 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.