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 : 25-06-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-29530 : could not create shortened name for string
  • ora-38602 : FI invalid input cursor
  • ora-19676 : one or more files failed during proxy backup or restore
  • ora-12463 : undefined group string for policy string
  • ora-12171 : TNS:could not resolve connect identifier: string
  • ora-32129 : cannot get information about this column
  • ora-13055 : Oracle object string does not exist in specified table
  • ora-24057 : cannot define subscriber with rule for queue string
  • ora-12841 : Cannot alter the session parallel DML state within a transaction
  • ora-32008 : error while processing parameter update at instance string
  • ora-39156 : error parsing dump file name "string"
  • ora-27083 : waiting for async I/Os failed
  • ora-13765 : Value "string" is illegal for a result limit.
  • ora-16645 : unexpected new instance interrupted current operation
  • ora-32761 : Turn off Temp LOB Ref Count Feature
  • ora-25119 : LOGGING/NOLOGGING option already specified
  • ora-12925 : tablespace string is not in force logging mode
  • ora-01049 : Bind by name is not spupportted in streamed RPC
  • ora-24019 : identifier for string too long, should not be greater than string characters
  • ora-02446 : CREATE TABLE ... AS SELECT failed - check constraint violated
  • ora-38771 : unnamed datafile(s) added to control file by flashback recovery
  • ora-29281 : invalid mode
  • ora-31192 : Resource string has not been checked out
  • ora-19509 : failed to delete sequential file, handle="string", parms="string"
  • ora-31652 : command response message was invalid type - detaching job
  • ora-12682 : Login failed: the SecurID card is in next PRN mode
  • ora-25277 : cannot grant or revoke object privilege on release 8.0 compatible queues
  • ora-12663 : Services required by client not available on the server
  • ora-15197 : suppressing string additional ASM messages
  • ora-38749 : A media recovery has been started.
  • 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.