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 : 30-04-2017

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-16637 : an instance failed to access the Data Guard broker configuration
  • ora-19594 : control file already included as string
  • ora-39127 : unexpected error from call to string string
  • ora-28001 : the password has expired
  • ora-01488 : invalid nibble or byte in the input data
  • ora-39709 : incomplete component downgrade; string downgrade aborted
  • ora-01877 : string is too long for internal buffer
  • ora-31655 : no data or metadata objects selected for job
  • ora-13787 : missing SQL profile for statement object "string" for tuning task "string"
  • ora-02143 : invalid STORAGE option
  • ora-09365 : Windows 3.1 Two-Task driver unable to destroy hidden window
  • ora-00114 : missing value for system parameter SERVICE_NAMES
  • ora-39210 : A PCTSPACE adjustment of string is invalid.
  • ora-27069 : attempt to do I/O beyond the range of the file
  • ora-00102 : network protocol string cannot be used by dispatchers
  • ora-39106 : Worker process string failed during startup. Worker error:
  • ora-27089 : unable to release advisory lock
  • ora-06565 : cannot execute string from within stored procedure
  • ora-27140 : attach to post/wait facility failed
  • ora-12468 : max write level does not equal max read level
  • ora-25352 : no current transaction
  • ora-01184 : logfile group string already exists
  • ora-24432 : The statement that was returned is not tagged.
  • ora-23304 : malformed deferred rpc at arg string of string in call string, in tid string
  • ora-30942 : XML Schema Evolution error for schema 'string' table string column 'string'
  • ora-27025 : skgfqsbi: invalid media manager context area size
  • ora-23332 : group string is in use; cannot drop
  • ora-40206 : invalid setting value for setting name string
  • ora-14101 : partition extended table name cannot refer to a synonym
  • ora-39958 : invalid warning category qualifier
  • 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.