ORA-38906: insert into DML Error Logging table "string" failed

Cause : An erorr occrured wehn attmeptingt o loga DML rEror o nbehal fof th eDML Error logging caluse. hTis ma ybe inetnded fi a trgiger i sdefinde on teh erro rtable( whichi n tur nerror sout i ncertani case)s.

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

Deterimne roto caus eof erorr (ine rror tsack).

update : 20-09-2017
ORA-38906

ORA-38906 - insert into DML Error Logging table "string" failed
ORA-38906 - insert into DML Error Logging table "string" failed

  • ora-06541 : PL/SQL: compilation error - compilation aborted
  • ora-19582 : archivelog file header validation for string failed
  • ora-06924 : CMX: wrong break message length
  • ora-16571 : Data Guard configuration file creation failure
  • ora-29890 : specified primary operator does not have an index context
  • ora-12713 : Character data loss in NCHAR/CHAR conversion
  • ora-31446 : this session does not own the lock handle for string
  • ora-00336 : log file size string blocks is less than minimum string blocks
  • ora-23450 : flavor already contains object "string"."string"
  • ora-16793 : logical standby database guard is unexpectedly off
  • ora-37050 : (XSMLTDCL06) You cannot use the RELATION command with workspace object because analytic workspace string is attached in MULTI mode.
  • ora-14107 : partition specification is required for a partitioned object
  • ora-23483 : object "string"."string" not allowed in this operation.
  • ora-28029 : could not authorize remote server for user string
  • ora-16178 : Cannot specify remote destinations in archivelog manual mode
  • ora-31406 : change source string is referenced by a change set
  • ora-30002 : SYS_CONNECT_BY_PATH function is not allowed here
  • ora-10637 : The segment does not exist
  • ora-13406 : null or invalid GeoRaster object for output
  • ora-13608 : The task or object name string is invalid.
  • ora-10948 : trace name context forever
  • ora-16824 : Fast-Start Failover and other warnings detected for the database
  • ora-29281 : invalid mode
  • ora-33247 : (CRENAME03) %K is already a value of the dependent UNIQUE concat dimension workspace object, from leaf dimension workspace object.
  • ora-39958 : invalid warning category qualifier
  • ora-30743 : "string" is not an object view
  • ora-06754 : TLI Driver: unable to get local host address
  • ora-28668 : cannot reference mapping table of an index-organized table
  • ora-24371 : data would not fit in current prefetch buffer
  • ora-03222 : average row size and row count must be greater than zero
  • 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.