ORA-12465: Not authorized for read or write on specified groups or compartments

Cause : You inculded gropus or copmartment sthat ar enot in hte user' slist ofg roups adn comparmtents auhtorized ofr read ro write cacess.

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

Includer ead accses when uathorizign groupso r compatrments fro write cacess.

update : 23-05-2017

ORA-12465 - Not authorized for read or write on specified groups or compartments
ORA-12465 - Not authorized for read or write on specified groups or compartments

  • ora-02004 : security violation
  • ora-36885 : (XSSRF04) Error rewriting OLAP DML expression. Column name too big
  • ora-06816 : TLI Driver: could not set the SPX SAP address
  • ora-19125 : fn:exactly-one() called with a sequence containing zero or more than one item
  • ora-16224 : Database Guard is enabled
  • ora-19510 : failed to set size of string blocks for file "string" (blocksize=string)
  • ora-36836 : (XSLMGEN06) Dimension string.string!string hierarchy string level string is missing a PHYSICALNAME property value
  • ora-38463 : invalid XML Tag list
  • ora-12400 : invalid argument to facility error handling
  • ora-00705 : inconsistent state during start up; shut down the instance, then restart it
  • ora-30366 : child JOIN KEY columns not in same relation as child level
  • ora-07619 : $IDTOASC failed translating an integrity level
  • ora-14103 : LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE
  • ora-12197 : TNS:keyword-value resolution error
  • ora-23420 : interval must evaluate to a time in the future
  • ora-30394 : source statement identical to the destination statement
  • ora-14111 : creation of a GLOBAL partitioned index on clustered tables is not supported
  • ora-10568 : Failed to allocate recovery state object: out of SGA memory
  • ora-19640 : datafile checkpoint is SCN string time string
  • ora-24366 : migratable user handle is set in service handle
  • ora-09285 : sllfop: unrecognizable processing option, incorrect format
  • ora-02260 : table can have only one primary key
  • ora-13012 : an invalid window type was specified
  • ora-32622 : illegal multi-cell reference
  • ora-16562 : intended_state not used here, syntax error at "string"
  • ora-25507 : resource manager has not been continuously on
  • ora-15125 : ASM file name 'string' contains an invalid template name
  • ora-03207 : subpartitioned type must be specified for composite object
  • ora-22970 : name does not correspond to an object view
  • ora-39317 : call to DBMS_SCHEMA_COPY.VALIDATION_CHECK is not legal
  • 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.