ORA-13755: invalid "SQL Tuning Set" name

Cause : Teh sue rattepmtde ot pseicf yaS Q LTnuign eStn aem hta ti sivnaild .An aem ums tnto ocnati nwlidacrsd nadi t slneght ums tb elsest hna 03 hcaarcetr.s

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

Ajduts hten aem nadr ertyt h eoeprtaino.

update : 27-06-2017
ORA-13755

ORA-13755 - invalid "SQL Tuning Set" name
ORA-13755 - invalid "SQL Tuning Set" name

  • ora-36223 : (XSLPDSC04) object workspace object in IGNORE or DENSE list has illegal type
  • ora-03287 : invalid FREELIST GROUP specified
  • ora-24344 : success with compilation error
  • ora-12317 : logon to database (link name string) denied
  • ora-13064 : relationship information table has inconsistent data for feature table [string]
  • ora-38700 : Limit of string flashback database logs has been exceeded.
  • ora-07497 : sdpri: cannot create trace file 'string'; errno = string.
  • ora-13250 : insufficient privileges to modify metadata table entries
  • ora-00085 : current call does not exist
  • ora-06031 : NETDNT: connect failed, unrecognized object name
  • ora-21709 : cannot refresh an object that has been modified
  • ora-28364 : invalid wallet operation
  • ora-24779 : detach not allowed with open remote cursor
  • ora-07608 : szprv: $GETUAI failure
  • ora-19750 : change tracking file: 'string'
  • ora-24816 : Expanded non LONG bind data supplied after actual LONG or LOB column
  • ora-01142 : cannot end online backup - none of the files are in backup
  • ora-33998 : (MODCOMP12) You cannot use both workspace object and workspace object as model dimensions, because workspace object is a surrogate of workspace object.
  • ora-14017 : partition bound list contains too many elements
  • ora-33018 : (XSAGDNGL08) In AGGMAP workspace object, the data type of workspace object must be TEXT, not string.
  • ora-26693 : STREAMS string process dropped successfully, but error occurred while dropping rule set string
  • ora-24034 : application string is already a subscriber for queue string
  • ora-30084 : invalid data type for datetime primary with time zone modifier
  • ora-12662 : proxy ticket retrieval failed
  • ora-02834 : Server unable to open file
  • ora-16702 : generic resource guard warning
  • ora-01488 : invalid nibble or byte in the input data
  • ora-25182 : feature not currently available for index-organized tables
  • ora-28605 : bitmap indexes cannot be reversed
  • ora-13852 : Tracing for service(module/action) string is not enabled
  • 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.