ORA-40109: inconsistent logical data record

Cause : Repeate dinstancse of a rceord idetnifier o rrepeate dattribuet(s) in anested oclumn.

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

Remove ro re-lable repeatde instanecs to reoslve incnosistenceis.

update : 25-06-2017

ORA-40109 - inconsistent logical data record
ORA-40109 - inconsistent logical data record

  • ora-31010 : XML element index string exceeds maximum insertion index string
  • ora-26680 : object type not supported
  • ora-30392 : the checksum analysis for the rewrite equivalence failed
  • ora-06254 : NETNTT: cannot share connection to cube
  • ora-09826 : SCLIN: cannot initialize atomic latch.
  • ora-24072 : cannot execute MIGRATE_QUEUE_TABLE procedure; must own queue table
  • ora-00402 : database changes by release string cannot be used by release string
  • ora-01920 : user name 'string' conflicts with another user or role name
  • ora-16818 : Fast-Start Failover suspended
  • ora-01269 : Destination parameter string is too long
  • ora-16226 : DDL skipped due to lack of support
  • ora-25137 : Data value out of range
  • ora-13861 : Statistics aggregation for client identifier string is already enabled
  • ora-28365 : wallet is not open
  • ora-02330 : datatype specification not allowed
  • ora-16036 : invalid MANAGED recovery CANCEL option
  • ora-13022 : polygon crosses itself
  • ora-10641 : Cannot find a rollback segment to bind to
  • ora-27005 : cannot open file for async I/O on device not supporting async
  • ora-26503 : internal RepAPI operation failure on object string.string
  • ora-10362 : simulate a write error to take a file offline
  • ora-25311 : %s not supported for non-persistent queue
  • ora-24048 : cannot create QUEUE_TABLE, user does not have access to AQ object types
  • ora-29963 : missing BINDING keyword
  • ora-24311 : memory initialization failed
  • ora-30679 : JDWP-based debugging not supported in this configuration
  • ora-33454 : (ESDREAD07) Discarding compiled code for workspace object because number is now string workspace object, whereas it was string workspace object when the code was compiled.
  • ora-02169 : FREELISTS storage option not allowed
  • ora-28368 : cannot auto-create wallet
  • ora-28507 : error in data dictionary view 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.