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 : 19-08-2017

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

  • ora-24169 : rule condition has unrecognized variables
  • ora-16758 : the specified apply instance is not running
  • ora-12196 : TNS:received an error from TNS
  • ora-30461 : 'string.string' cannot be refreshed because it is marked DISABLED
  • ora-32618 : incorrect use of MODEL PREVIOUS function
  • ora-26517 : materialized view control entry for 'string.string' was not found
  • ora-08436 : raw data has invalid sign digit
  • ora-19115 : too many context items specified
  • ora-13454 : GeoRaster metadata is invalid
  • ora-09840 : soacon: Name translation failure.
  • ora-19678 : RMAN configuration value exceeds maximum length of string
  • ora-39091 : unable to determine logical standby and streams status
  • ora-28178 : password not provided by proxy
  • ora-12059 : prebuilt table "string"."string" does not exist
  • ora-23476 : cannot import from string to string
  • ora-12913 : Cannot create dictionary managed tablespace
  • ora-00161 : transaction branch length string is illegal (maximum allowed string)
  • ora-16703 : cannot set property while the database is enabled
  • ora-26514 : object 'string.string' not found
  • ora-34802 : (OCI11) OLAP OCI operation caused ROLLBACK past an UPDATE of an attached analytic workspace. Current operation canceled.
  • ora-06530 : Reference to uninitialized composite
  • ora-36996 : (XSRELGID13) Valueset workspace object should be defined over dimension workspace object.
  • ora-28656 : incomplete attribute specification
  • ora-35062 : (QFGET01) Duplicate files found for extension number number of EIF file string.
  • ora-28579 : network error during callback from external procedure agent
  • ora-14642 : Bitmap index mismatch for tables in ALTER TABLE EXCHANGE PARTITION
  • ora-15190 : Internal ASM testing event number 15190
  • ora-02837 : Unable to unlink temporary file
  • ora-30960 : The entity is neither an XPATH nor a NAMESPACE.
  • ora-19719 : length for operation name longer than string
  • 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.