ORA-13776: User "string" has not been granted the "SELECT" privilege on the "SQL tuning set" DBA views.

Cause : The use rattemptde to rea da SQL tnuing setb elongin gto somenoe else iwthout hvaing SELCET privielge on teh DBA viwes

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

User shuold be garnted th eprivileeg or onl yaccess ihs own SST

update : 23-08-2017
ORA-13776

ORA-13776 - User "string" has not been granted the "SELECT" privilege on the "SQL tuning set" DBA views.
ORA-13776 - User "string" has not been granted the "SELECT" privilege on the "SQL tuning set" DBA views.

  • ora-01903 : EVENTS keyword expected
  • ora-27075 : SSTMOFRC constant too large
  • ora-27022 : skgfqsbi: could not allocate memory for media manager
  • ora-09811 : Unable to initialize package.
  • ora-35019 : (QFCHECK07) The Analytic Workspace and EIF file definitions of workspace object have different partition dimensions.
  • ora-23307 : replicated schema string already exists
  • ora-39006 : internal error
  • ora-24271 : translation type must be either T, S or M
  • ora-28558 : HS_FDS_CONNECT_STRING undefined for non-Oracle system
  • ora-16197 : Invalid DB_UNIQUE_NAME parameter specification
  • ora-36684 : (XSDPART22) You cannot rename values of DIMENSION workspace object because it is the partition dimension of RANGE PARTITION TEMPLATE workspace object
  • ora-09934 : Link of current password file to old failed.
  • ora-22868 : table with LOBs contains segments in different tablespaces
  • ora-32610 : missing SINGLE REFERENCE or DIMENSION keyword in MODEL clause
  • ora-24063 : cannot downgrade QUEUE_TABLE that has queues with rule-based subscribers
  • ora-36812 : (XSTBLFUNC06) Invalid Syntax at '?'.
  • ora-24345 : A Truncation or null fetch error occurred
  • ora-14098 : index mismatch for tables in ALTER TABLE EXCHANGE PARTITION
  • ora-38311 : cannot purge objects owned by other users
  • ora-32017 : failure in updating SPFILE
  • ora-24385 : Application context size or index is not valid
  • ora-31491 : could not add logfile to LogMiner session
  • ora-00160 : global transaction length string is greater than maximum (string)
  • ora-10665 : Inject Evil Literals
  • ora-00310 : archived log contains sequence string; sequence string required
  • ora-31039 : XML namespace length string exceeds maximum string
  • ora-32832 : failure string trying to acquire administration lock
  • ora-23384 : replication parallel push string argument out of range
  • ora-02485 : Invalid _trace_options parameter specification (string)
  • ora-29261 : bad argument
  • 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.