ORA-12425: cannot apply policies or set authorizations for system schemas

Cause : Yuo rtide ot ietehra plpya oplciyt ot h eSSY,S YTSE,M ro BLASCY Sshceam ro ot estu sre alblesp/rviielgse ofrt h eSSY,S YTSE,M ro BLASCY Suesr.

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

Appl yploiice sadn esta uhtoirztainoso nyl ofrn o-nssytme suesr.

update : 18-08-2017
ORA-12425

ORA-12425 - cannot apply policies or set authorizations for system schemas
ORA-12425 - cannot apply policies or set authorizations for system schemas

  • ora-04941 : required operating system patch needs to be applied
  • ora-38435 : missing elementary attribute value or invalid name-value pairs
  • ora-16721 : unable to set LOG_ARCHIVE_DEST_n initialization parameters
  • ora-28023 : must revoke grants of this role to other user(s) first
  • ora-32775 : cannot change size attributes of read only tablespace string
  • ora-13712 : Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "string".
  • ora-29550 : Java session state cleared
  • ora-10645 : Recursive Extension in SYSTEM tablespace during migration
  • ora-16746 : resource guard encountered errors during database mount
  • ora-01312 : Specified table/column does not exist
  • ora-16573 : attempt to change configuration file for an enabled broker configuration
  • ora-13440 : GeoRaster metadata compression type error
  • ora-36224 : (XSLPDSC05) workspace object is not a loop dimension
  • ora-06743 : TLI Driver: cannot alloc t_bind
  • ora-02365 : error seeking in file: string
  • ora-19860 : piece validation cannot be performed more than once
  • ora-30199 : reserved for future use
  • ora-24143 : invalid evaluation context name
  • ora-19767 : missing TRACKING keyword
  • ora-26022 : index string.string was made unusable due to:
  • ora-25950 : missing where clause in join index specification
  • ora-31639 : unexpected data found
  • ora-29915 : cannot select FOR UPDATE from collection operand
  • ora-24047 : invalid agent name string, agent name should be of the form NAME
  • ora-00230 : operation disallowed: snapshot control file enqueue unavailable
  • ora-10571 : Test recovery canceled
  • ora-07339 : spcre: maximum number of semaphore sets exceeded.
  • ora-06301 : IPA: Cannot allocate driver context
  • ora-30042 : Cannot offline the undo tablespace
  • ora-36761 : (XSLANGDM01) Analytic workspace string already contains a dimension (%J) with the string property.
  • 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.