ORA-28117: integrity constraint violated - parent record not found

Cause : try to update/insert a child record with new foreign key values, but the corresponding parent row is not visible because of fine-grained security in the parent.

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

make sure that the updated foreign key values must also visible in the parent

update : 26-09-2017

ORA-28117 - integrity constraint violated - parent record not found
ORA-28117 - integrity constraint violated - parent record not found

  • ora-27159 : failure setting process scheduling priority
  • ora-37012 : (XSACQUIRE_TIMEOUT) Object workspace object is locked by another user and the WAIT timed out.
  • ora-13284 : failure to copy geometry object for conversion in place
  • ora-29813 : non-supported object type with associate statement
  • ora-15028 : ASM file 'string' not dropped; currently being accessed
  • ora-04052 : error occurred when looking up remote object stringstringstringstringstring
  • ora-36837 : (XSLMGEN07) Dimension string.string!string is missing a COLUMNNAME property value
  • ora-24182 : attribute number specified does not exist
  • ora-25011 : cannot create trigger on internal AQ table
  • ora-25962 : join index prevents multitable insert or merge
  • ora-23341 : user function required
  • ora-14503 : only one partition name can be specified
  • ora-02222 : invalid PCTINCREASE storage option value
  • ora-29895 : duplicate base datatype specified
  • ora-36779 : (XSPGPOOLOUT) Invalid parameter value. Olap_page_pool_size must be between must be between 2097152 and 2147483647. Olap_page_pool_size remain unmodified.
  • ora-12916 : Cannot use default permanent tablespace with this release
  • ora-13353 : ELEM_INFO_ARRAY not grouped in threes
  • ora-31216 : DBMS_LDAP: PL/SQL - Invalid LDAP rdn.
  • ora-19831 : incompatible string.string.string.string DBMS_BACKUP_RESTORE package: string.string.string.string required
  • ora-09916 : Required password was not specified.
  • ora-00219 : required control file size (string logical blocks) exceeds maximum allowable size (string logical blocks)
  • ora-24410 : scrollable cursor max size exceeded
  • ora-28181 : proxy 'string' failed to enable one or more of the specified initial roles for client 'string'
  • ora-31155 : attribute string not in XDB namespace
  • ora-32026 : %s.string has fewer columns compared to string table.
  • ora-02701 : osnoraenv: error translating oracle image name
  • ora-02219 : invalid NEXT storage option value
  • ora-24422 : error occurred while trying to destroy the Session Pool
  • ora-19024 : Cursor expression must be named
  • ora-39780 : Direct path context operations are not allowed after the context is aborted or finished
  • 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.