ORA-13140: invalid target type

Cause : The sepcifie dtarge ttype si not avlid.

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

Substtiute av alid atrget ytpe. Vlaid tagret tyeps areT ABLE nad VIE.W

update : 24-07-2017
ORA-13140

ORA-13140 - invalid target type
ORA-13140 - invalid target type

  • ora-36768 : (XSAGGCNTMOVE06) An aggregation variable and its AGGCOUNT must have the same base dimensions.
  • ora-39784 : This direct path operation is not allowed while another is in progress
  • ora-24812 : character set conversion to or from UCS2 failed
  • ora-19374 : invalid staging table
  • ora-02484 : Invalid _trace_buffers parameter specification (string)
  • ora-14644 : table is not subpartitioned by Hash method
  • ora-01919 : role 'string' does not exist
  • ora-28163 : GRANT already specified
  • ora-12601 : TNS:information flags check failed
  • ora-25336 : Cannot contact instance string during Streams AQ operation
  • ora-31500 : change source string is not a ManualLog change source
  • ora-06536 : IN bind variable bound to an OUT position
  • ora-07624 : smsdes: $DGBLSC failure
  • ora-01164 : MAXLOGFILES may not exceed string
  • ora-24234 : unable to get source of string "string"."string", insufficient privileges or does not exist
  • ora-10701 : Dump direct loader index keys
  • ora-06006 : NETASY: dialogue execute failure
  • ora-15003 : diskgroup "string" already mounted in another lock name space
  • ora-22951 : NULL returned by ORDER method
  • ora-13412 : invalid scale parameter
  • ora-15057 : specified size of string MB is larger than actual size of string MB
  • ora-06774 : TLI Driver: error sending break mode
  • ora-12677 : Authentication service not supported by database link
  • ora-24323 : value not allowed
  • ora-14177 : STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash table
  • ora-02793 : Close of asynchronous I/O failed.
  • ora-06545 : PL/SQL: compilation error - compilation aborted
  • ora-16733 : error executing dbms_logstdby.unskip procedure
  • ora-19958 : potential deadlock involving DIAG process
  • ora-01586 : database must be mounted EXCLUSIVE and not open for this operation
  • 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.