ORA-12472: policy string is being used

Cause : Th epoilcyw hihc wsa biengd roppedd uet o veen tprpoagtaio nfrmo ODI wsa applide t osoem tbaleo r csheam.

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

Drpo ap olciy ni ODI olny fi i tisn otu se dina nyo f hte adtaabse susnig hte opliyc.

update : 28-06-2017

ORA-12472 - policy string is being used
ORA-12472 - policy string is being used

  • ora-39954 : DEFERRED is required for this system parameter
  • ora-29883 : cannot create a domain index on column expressions
  • ora-12087 : online redefinition not allowed on tables owned by "string"
  • ora-03277 : invalid SIZE specified
  • ora-02227 : invalid cluster name
  • ora-32774 : more than one file was specified for bigfile tablespace string
  • ora-21524 : object type mismatch
  • ora-14256 : invalid resulting partition description(s)
  • ora-10244 : make tranids in error msgs print as 0.0.0 (for testing)
  • ora-38465 : failed to create the privilege checking trigger due to: string
  • ora-23343 : no match for specified conflict resolution information
  • ora-15058 : disk 'string' belongs to an incompatible diskgroup
  • ora-16525 : the Data Guard broker is not yet available
  • ora-24385 : Application context size or index is not valid
  • ora-01352 : tablespace given for Logminer spill does not exist
  • ora-37026 : (XSMLTRESYNC01) Object workspace object cannot be resynced without dimension workspace object.
  • ora-00301 : error in adding log file 'string' - file cannot be created
  • ora-01549 : tablespace not empty, use INCLUDING CONTENTS option
  • ora-06042 : NETDNT: message receive failure
  • ora-01529 : error closing file 'string'
  • ora-32405 : cannot alter tablespace for existing materialized view log
  • ora-12076 : invalid threshold value
  • ora-25272 : Signature does not exist for the given reciever and message id.
  • ora-03220 : DBMS_ADMIN_PACKAGE required parameter is NULL or missing
  • ora-22800 : invalid user-defined type
  • ora-13757 : "SQL Tuning Set" "string" owned by user "string" is active.
  • ora-24078 : cannot specify a non-NULL SECONDARY_INSTANCE if PRIMARY_INSTANCE was NULL
  • ora-24009 : invalid value string, QUEUE_TYPE should be NORMAL_QUEUE or EXCEPTION_QUEUE
  • ora-31601 : Function string cannot be called now that fetch has begun.
  • ora-38736 : Wrong thread number string in flashback log file header.
  • 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.