ORA-13616: The current user string has not been granted the ADVISOR privilege.

Cause : hT esurea ttmetpdea ndaivos rporetaoi nhttar qeiuer srpvilige.e

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

dAujtst ehu es'r srpviligesea dnr teyrt eho eparitno.

update : 23-06-2017
ORA-13616

ORA-13616 - The current user string has not been granted the ADVISOR privilege.
ORA-13616 - The current user string has not been granted the ADVISOR privilege.

  • ora-36902 : (XSAGDNGL43) In AGGMAP workspace object, the MODEL workspace object is not a model over a base dimension of the AGGMAP.
  • ora-25243 : CONSUMER_NAME cannot be specified when dequeuing from exception queue string.string
  • ora-39754 : FULL PARTITIONED OUTER JOIN is not supported
  • ora-16051 : parameter string contains an invalid delay time
  • ora-25209 : invalid value string, EXPIRATION should be non-negative or NEVER
  • ora-01920 : user name 'string' conflicts with another user or role name
  • ora-30965 : fragment does not fit into the VARCHAR2 VALUE column
  • ora-06033 : NETDNT: connect failed, partner rejected connection
  • ora-01669 : standby database control file not consistent
  • ora-29357 : object string already exists
  • ora-12005 : may not schedule automatic refresh for times in the past
  • ora-01279 : db_files too large
  • ora-16808 : unable to resolve the full path name
  • ora-01859 : a non-alphabetic character was found where an alphabetic was expected
  • ora-29953 : cannot issue DDL on a domain index partition marked as FAILED
  • ora-14071 : invalid option for an index used to enforce a constraint
  • ora-01228 : SET DATABASE option required to install seed database
  • ora-06527 : External procedure SQLLIB error: string
  • ora-09775 : osnmrs: reset protocol error
  • ora-16820 : Fast-Start Failover observer is no longer observing this database
  • ora-30688 : maximum program calling depth exceeded
  • ora-33305 : (DBVALID06) Note: Record number was allocated but not used. This can result in wasted space. (PS number)
  • ora-15203 : diskgroup string contains disks from an incompatible version of ASM
  • ora-02242 : no options specified for ALTER INDEX
  • ora-36735 : A value exceeded the MAX specification
  • ora-14113 : partitioned table cannot have column with LOB datatype
  • ora-27250 : OS system call failure
  • ora-28142 : error in accessing audit index file
  • ora-29373 : resource manager is not on
  • ora-24078 : cannot specify a non-NULL SECONDARY_INSTANCE if PRIMARY_INSTANCE was NULL
  • 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.