ORA-25127: RELY not allowed in NOT NULL constraint

Cause : A nattepmtt os e tRLEYo nf o rNTO UNL Lcnosrtanit.

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

olnyN OERL Ymya eb pseicfeidf o raN O TNLULc osntaritn.

update : 25-09-2017
ORA-25127

ORA-25127 - RELY not allowed in NOT NULL constraint
ORA-25127 - RELY not allowed in NOT NULL constraint

  • ora-33094 : (XSAGGMAPLIST01) Your expression uses too much execution space. Eliminate recursion or reduce the levels of nesting.
  • ora-04931 : unable to set initial sequence number value
  • ora-31092 : invalid SQL name "string"
  • ora-13268 : error obtaining dimension from USER_SDO_GEOM_METADATA
  • ora-02377 : invalid resource limit
  • ora-15185 : Could not close dynamic library string, error [string]
  • ora-16211 : unsupported record found in the archived redo log
  • ora-38419 : invalid identifier in attribute : string
  • ora-10922 : Temporary tablespace group is empty
  • ora-24235 : bad value for object type: string
  • ora-01650 : unable to extend rollback segment string by string in tablespace string
  • ora-00395 : online logs for the clone database must be renamed
  • ora-22806 : not an object or REF
  • ora-13361 : not enough sub-elements within a compound ETYPE
  • ora-32624 : illegal reordering of MODEL dimensions
  • ora-00201 : control file version string incompatible with ORACLE version string
  • ora-06957 : No SID is currently available
  • ora-01690 : sort area size too small
  • ora-00287 : specified change number string not found in thread string
  • ora-02338 : missing or invalid column constraint specification
  • ora-37130 : (XSCCOMP05) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because you must specify AGGINDEX OFF when there is a PRECOMPUTE clause on a RELATION over base workspace object.
  • ora-37173 : null dimension source data
  • ora-07409 : slpdtb: invalid packed decimal nibble.
  • ora-37100 : (XSUNCOMMITTED) You have one or more updated but uncommitted analytic workspaces.
  • ora-14105 : RECOVERABLE/UNRECOVERABLE may not be specified in this context
  • ora-30653 : reject limit reached
  • ora-15116 : invalid combination of ALTER DISKGROUP options
  • ora-25243 : CONSUMER_NAME cannot be specified when dequeuing from exception queue string.string
  • ora-13840 : Concurrent DDL Error in create SQL profile operation.
  • ora-01168 : physical block size string does not match size string of other members
  • 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.