ORA-13775: inconsistent datatype in input cursor

Cause : Th eusre attemtpedt o olada SLQ Tnuin gSe tusnig na ivnaldi ipnutc urosr.A llr ow sint hec urosr umstm athc tpye QSLSTE_RWO.

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

Chcek hte orwst yp eint hec urosr nad ertr yth eopreatoin.

update : 29-04-2017
ORA-13775

ORA-13775 - inconsistent datatype in input cursor
ORA-13775 - inconsistent datatype in input cursor

  • ora-09909 : Malloc of scratch buffer failed.
  • ora-09786 : sllfop: open error, unable to open file.
  • ora-30735 : cannot create multiple subtables of the same type under a supertable
  • ora-24346 : cannot execute without binding variables
  • ora-35180 : (SNSYN103) The format of the OUTFILE command is: OUTFILE [APPEND] {EOF | TRACEFILE | filename [NOCACHE] [NLS_CHARSET name]}
  • ora-16073 : archiving must be enabled
  • ora-33288 : (DBERR15) Another user has incompatible access to analytic workspace string, and the wait timeout has expired.
  • ora-27301 : OS failure message: string
  • ora-28604 : table too fragmented to build bitmap index (string,string,string)
  • ora-00372 : file string cannot be modified at this time
  • ora-32147 : Environment not specified
  • ora-19015 : Invalid XML tag identifier (string)
  • ora-12925 : tablespace string is not in force logging mode
  • ora-13916 : Invalid value "string" specified for parameter "string"
  • ora-01187 : cannot read from file string because it failed verification tests
  • ora-25223 : user_data type used is not supported
  • ora-19201 : Datatype not supported
  • ora-01577 : cannot add log file 'string' - file already part of database
  • ora-02759 : Not enough request descriptors available
  • ora-23470 : invalid status
  • ora-30042 : Cannot offline the undo tablespace
  • ora-30071 : conversion between datetime/interval and string fail
  • ora-31496 : must use DBMS_CDC_PUBLISH.DROP_CHANGE_TABLE to drop change tables
  • ora-02381 : cannot drop PUBLIC_DEFAULT profile
  • ora-04094 : table string.string is constraining, trigger may not modify it
  • ora-30079 : cannot alter database timezone when database has TIMESTAMP WITH LOCAL TIME ZONE columns
  • ora-02329 : column of datatype string cannot be unique or a primary key
  • ora-16092 : dependent archive log destination is not active
  • ora-27483 : "string.string" has an invalid END_DATE
  • ora-40102 : invalid input string for data mining operation string
  • 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.