ORA-32836: database user string must be granted role string

Cause : The specified database user does not have a required role.

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

Grant the user the indicated role.

update : 21-07-2017
ORA-32836

ORA-32836 - database user string must be granted role string
ORA-32836 - database user string must be granted role string

  • ora-37133 : (XSCCOMP08) You cannot write into an aggregated VARIABLE dimensioned by a COMPRESSED COMPOSITE. Use the CLEAR AGGREGATES command to reenable write access.
  • ora-36974 : (XSRELTBL14) workspace object is not a BOOLEAN variable dimensioned by all the dimensions of the hierarchy.
  • ora-07801 : slbtpd: invalid exponent
  • ora-12226 : TNS:operating system resource quota exceeded
  • ora-02769 : Setting of handler for SIGTERM failed
  • ora-38439 : invalid operation "string"
  • ora-30393 : a query block in the statement did not rewrite
  • ora-36176 : (XSMXAGGR25) Relation workspace object must be a one-dimensional self-relation to be used as a weight for AGGREGATE.
  • ora-38955 : Source platform string not cross platform compliant
  • ora-13013 : the specified topology was not INTERIOR or BOUNDARY
  • ora-39065 : unexpected master process exception in string
  • ora-08106 : cannot create journal table string.string
  • ora-13826 : empty SQL profile not allowed for create or update SQL profile
  • ora-06770 : TLI Driver: error sending version
  • ora-25117 : MIN/MAX/Block Number expected
  • ora-22150 : variable-length array has not been initialized
  • ora-26741 : cannot assemble lobs
  • ora-14266 : data type or length of an index subpartitioning column may not be changed
  • ora-12665 : NLS string open failed
  • ora-22296 : invalid ALTER TABLE option for conversion of LONG datatype to LOB
  • ora-07601 : spguno: $GETJPIW failure
  • ora-13006 : the specified cell number is invalid
  • ora-00376 : file string cannot be read at this time
  • ora-12487 : clearance labels not between DBHIGH and DBLOW
  • ora-13186 : fixed tile size tessellation failed
  • ora-16110 : user procedure processing of logical standby apply DDL
  • ora-06019 : NETASY: invalid login (connect) string
  • ora-00265 : instance recovery required, cannot set ARCHIVELOG mode
  • ora-02302 : invalid or missing type name
  • ora-27470 : failed to re-enable "string.string" after making requested change
  • 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.