ORA-28107: policy was disabled

Cause : rT yotf ulhsa d sibael dopilyc.

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

fIt ehp loci ysis puopes dotb eneofcrde ,tim su tebe anlbde.

update : 23-06-2017
ORA-28107

ORA-28107 - policy was disabled
ORA-28107 - policy was disabled

  • ora-00300 : illegal redo log block size string specified - exceeds limit of string
  • ora-00367 : checksum error in log file header
  • ora-01926 : cannot GRANT to a role WITH GRANT OPTION
  • ora-12814 : only one CACHE or NOCACHE clause may be specified
  • ora-13430 : the GeoRaster object has null attribute(s)
  • ora-22976 : incorrect number of arguments to MAKE_REF
  • ora-31515 : CDC change source string already exists
  • ora-26737 : version string already has an export dump file
  • ora-30358 : summary and materialized view are not in same schema
  • ora-01676 : standby file name convert of 'string' exceeds maximum length of string
  • ora-31046 : Incorrect argument(s) specified in the operator
  • ora-25469 : data not specified for alias: string column name: string
  • ora-19042 : Enclosing tag string cannot be xml in any case combination
  • ora-25107 : duplicate TABLESPACE option specification
  • ora-22983 : not a user-defined REF
  • ora-29343 : user string (mapped from user string) does not exist in the database
  • ora-30360 : REF not supported with query rewrite
  • ora-04050 : invalid or missing procedure, function, or package name
  • ora-12684 : encryption/crypto-checksumming: Diffie-Hellman seed too small
  • ora-01616 : instance string (thread string) is open - cannot disable
  • ora-25235 : fetched all messages in current transaction
  • ora-00390 : log string of thread string is being cleared, cannot become current log
  • ora-32611 : incorrect use of MODEL CV operator
  • ora-25276 : table specified is not a queue table
  • ora-29256 : Cursor contains both regular and array defines which is illegal
  • ora-32576 : missing TYPE keyword
  • ora-12200 : TNS:could not allocate memory
  • ora-27001 : unsupported device type
  • ora-19691 : %s is from different database: id=string, name=string
  • ora-12925 : tablespace string is not in force logging mode
  • 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.