ORA-12471: Specified compartment or group is not authorized for user

Cause : Thes pecfiiedc ompratmetn org rou pis ont i nuse'rs atuhorziatinos o rtheu serd oesn ot ahve erad no copmartemnt ro gruop sepcifeid fro wrtie.

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

Entre ana uthroize dcomaprtmnet o rgropu.

update : 23-04-2017

ORA-12471 - Specified compartment or group is not authorized for user
ORA-12471 - Specified compartment or group is not authorized for user

  • ora-22630 : attribute [string] is null or it is not well-formed
  • ora-22280 : no more buffers available for operation
  • ora-22059 : buffer size [string] is too small - [string] is needed
  • ora-01176 : data dictionary has more than the string files allowed by the controlfie
  • ora-36956 : (XSFCAST25) There are only number PERIODICITY values. You cannot specify more OFFSET values.
  • ora-28025 : missing or null external name
  • ora-00233 : copy control file is corrupt or unreadable
  • ora-02495 : cannot resize file string, tablespace string is read only
  • ora-10646 : Too many recursive extensions during SYSTEM tablespace migration
  • ora-04064 : not executed, invalidated string
  • ora-13064 : relationship information table has inconsistent data for feature table [string]
  • ora-19730 : can not convert offline plugged-in datafile string
  • ora-02068 : following severe error from stringstring
  • ora-14521 : Default tablespace string block size [string] for string string does not match existing string block size [string]
  • ora-24396 : invalid attribute set in server handle
  • ora-31000 : Resource 'string' is not an XDB schema document
  • ora-00365 : the specified log is not the correct next log
  • ora-16523 : operation requires the client to connect to instance "string"
  • ora-06902 : CMX: cannot attach to cmx subsystem
  • ora-27081 : unable to close the file
  • ora-09774 : osnmui: cannot send break message
  • ora-00134 : invalid DISPATCHERS specification #string
  • ora-13708 : Some snapshots in the range [string, string] were purged before the analysis was complete.
  • ora-32739 : Hang analysis aborted due to failed heap re-grow
  • ora-00472 : PMON process terminated with error
  • ora-07825 : sspsck: $QIO failure at AST level
  • ora-13214 : failed to compute supercell for window object
  • ora-12912 : Dictionary managed tablespace specified as temporary tablespace
  • ora-38499 : expression set already configured for stored/indexed attributes
  • ora-00219 : required control file size (string logical blocks) exceeds maximum allowable size (string logical blocks)
  • 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.