ORA-28115: policy with check option violation

Cause : Policy predicate was evaluated to FALSE with the updated values.

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


update : 24-05-2017

ORA-28115 - policy with check option violation
ORA-28115 - policy with check option violation

  • ora-19800 : Unable to initialize Oracle Managed Destination
  • ora-02071 : error initializing capabilities for remote database string
  • ora-30031 : the suspended (resumable) statement has been aborted
  • ora-29917 : cannot lock a table which gets its rows from a collection operand
  • ora-13227 : SDO_LEVEL values for the two index tables do not match
  • ora-19331 : Last argument to CREATE_DBURI operator must be a column
  • ora-10572 : Test recovery canceled due to errors
  • ora-00041 : active time limit exceeded - session terminated
  • ora-19642 : start SCN of incremental backup is string
  • ora-29278 : SMTP transient error: string
  • ora-24171 : creation properties are only for internal use
  • ora-10916 : TABLESPACE GROUP already specified
  • ora-29880 : such column list already indexed using another domain index and indextype
  • ora-01158 : database string already mounted
  • ora-04017 : invalid value string (length = string) for parameter max_dump_file_size
  • ora-02247 : no option specified for ALTER SESSION
  • ora-39024 : wrong schema specified for job
  • ora-31430 : subscriber view exists
  • ora-06039 : NETDNT: connect failed
  • ora-27367 : program "string.string" associated with this job is disabled
  • ora-07257 : spdcr: translation error expanding program name.
  • ora-00451 : foreground process died unexpectedly
  • ora-14291 : cannot EXCHANGE a composite partition with a non-partitioned table
  • ora-25151 : Rollback Segment cannot be created in this tablespace
  • ora-30735 : cannot create multiple subtables of the same type under a supertable
  • ora-32022 : parameter value longer than string characters
  • ora-16177 : media recovery is not required
  • ora-36170 : (XSMXAGGR12) The data type of the WEIGHT workspace object must be numeric or BOOLEAN, not string.
  • ora-22275 : invalid LOB locator specified
  • ora-10931 : trace name context forever
  • 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.