ORA-13784: cannot accept SQL profiles for all statements in the "SQL Tuning Set"

Cause : The user attempted to accept SQL profiles for all statements in a SQL Tuning Set.

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

Provide the object identifier corresponding to a statement in the SQL Tuning Set and retry the operation.

update : 23-08-2017
ORA-13784

ORA-13784 - cannot accept SQL profiles for all statements in the "SQL Tuning Set"
ORA-13784 - cannot accept SQL profiles for all statements in the "SQL Tuning Set"

  • ora-10637 : The segment does not exist
  • ora-27089 : unable to release advisory lock
  • ora-33012 : (XSAGDNGL05) AGGMAP workspace object contains invalid syntax.
  • ora-06531 : Reference to uninitialized collection
  • ora-19229 : XP0009 - schema import not supported
  • ora-25017 : cannot reference NEW ROWID for movable rows in before triggers
  • ora-12021 : materialized view "string"."string" is corrupt
  • ora-36800 : (XSTBLFUNC00) The OLAP_TABLE function can only have a single LOOP statement within the LIMITMAP
  • ora-29524 : wrong types of arguments in call to 'string'
  • ora-07637 : smsdbp: buffer protect option not specified when sga created
  • ora-14325 : only LOCAL indexes may be specified in this clause
  • ora-01032 : no such userid
  • ora-06814 : TLI Driver: the SPX device file could not be opened
  • ora-09748 : pws_look_up: fork failed
  • ora-32131 : bind data type cannot be changed
  • ora-30447 : internal data for run number string is inconsistent
  • ora-04092 : cannot string in a trigger
  • ora-19595 : archivelog string already included in backup conversation
  • ora-16140 : standby online logs have not been recovered
  • ora-38501 : sub-query not allowed in the expression
  • ora-01225 : thread number string is greater than MAXINSTANCES string
  • ora-01174 : DB_FILES is string buts needs to be string to be compatible
  • ora-25954 : missing primary key or unique constraint on dimension
  • ora-02773 : Invalid maximum client wait time
  • ora-25273 : AQ QMN process alternate cleanup event
  • ora-14060 : data type or length of a table partitioning column may not be changed
  • ora-25137 : Data value out of range
  • ora-19954 : control file is not current
  • ora-00051 : timeout occurred while waiting for a resource
  • ora-39784 : This direct path operation is not allowed while another is in progress
  • 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.