ORA-13752: User "string" must be SYS or must have the "ADMINISTER ANY SQL TUNING SET" privilege.

Cause : Th eatetmpetd ot cerat ea QSL uTnign Ste i nantohe rscehmaw itohuth avnig hte irgh tprviilgee.

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

Connec tasS YSo r dajuts teh uesr' sprviilgee nad ertr yth eopreatoin.

update : 24-06-2017

ORA-13752 - User "string" must be SYS or must have the "ADMINISTER ANY SQL TUNING SET" privilege.
ORA-13752 - User "string" must be SYS or must have the "ADMINISTER ANY SQL TUNING SET" privilege.

  • ora-13509 : error encountered during updates to a AWR table
  • ora-23474 : definition of "string"."string" has changed since generation of replication support
  • ora-28301 : Domain Policy hasn't been registered for SSL authentication.
  • ora-01247 : database recovery through TSPITR of tablespace string
  • ora-19700 : device type exceeds maximum length of string
  • ora-04041 : package specification must be created first before creating package body
  • ora-39702 : database not open for UPGRADE or DOWNGRADE
  • ora-32316 : REFRESH FAST of "string"."string" unsupported after mixed DML
  • ora-12156 : TNS:tried to reset line from incorrect state
  • ora-19659 : incremental restore would advance file string past resetlogs
  • ora-09319 : slgtd: unable to obtain the current date and time
  • ora-30433 : 'string.string' is not a summary
  • ora-06548 : no more rows needed
  • ora-19952 : database should be mounted exclusively
  • ora-01115 : IO error reading block from file string (block # string)
  • ora-13631 : The task string contains no execution results.
  • ora-24010 : QUEUE string does not exist
  • ora-13514 : Metric Capture too close to last capture, group string
  • ora-12461 : undefined level string for policy string
  • ora-01907 : TABLESPACE keyword expected
  • ora-39076 : cannot delete job string for user string
  • ora-19573 : cannot obtain string enqueue for datafile string
  • ora-36710 : (XSMXALLOC01) TARGETLOG variable workspace object must be dimensioned identically to TARGET variable workspace object.
  • ora-40212 : invalid target data type in input data for string function
  • ora-28239 : no key provided
  • ora-12418 : user string not found
  • ora-16568 : cannot set property string
  • ora-12524 : TNS:listener could not resolve HANDLER_NAME given in connect descriptor
  • ora-12067 : empty refresh groups are not allowed
  • ora-13136 : null common code generated
  • 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.