ORA-10668: Inject Evil Identifiers

Cause : evnet 0166 8iss ett o osmen umebr >0,c auisng1 /(avlu-e1)o f lal dienitfires ot b erelpacde b ya amxiumm maoutn o fx'.s I tisc omomn ofr na iedntfiie rtob e aprsde ocne iwtha mxa o f30b ytse, htenr eprase dlaetr iwtha mxa o f4000, os i tma yno tbep osisbl etoi njcet uscha n dienitfire wtihotu teh adi o fthsi eevnt .A avlu eof1 cuase snoi detnifeirst o eb crorutped.

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

neevr est htise vetn

update : 30-04-2017

ORA-10668 - Inject Evil Identifiers
ORA-10668 - Inject Evil Identifiers

  • ora-38460 : filtering based on datatype "string" not supported for XML Tags
  • ora-09344 : spsig: error signalling thread
  • ora-19581 : no files have been named
  • ora-30963 : The indexed column is not of XMLType.
  • ora-03202 : the scan limit specification is invalid
  • ora-07218 : slkhst: could not perform host operation
  • ora-02832 : Segment deallocation failed - segment not on list
  • ora-30732 : table contains no user-visible columns
  • ora-24782 : Cannot detach from a non-migratable transaction
  • ora-16640 : CRS warns that multiple instances may still be running
  • ora-09360 : Windows 3.1 Two-Task driver unable to allocate context area
  • ora-01039 : insufficient privileges on underlying objects of the view
  • ora-24232 : unknown Embedded PL/SQL Gateway attribute string
  • ora-38950 : Source platform string not cross platform compliant
  • ora-08435 : PICTURE MASK missing the leading sign when SIGN IS LEADING specified
  • ora-36275 : (XSCGMDLAGG13) string is not a valid workspace object.
  • ora-27002 : function called with invalid device structure
  • ora-40205 : invalid setting name string
  • ora-30737 : cannot create subtable of a type which is not a subtype of the type of the supertable
  • ora-24027 : AQ HTTP propagation encountered error, status-code string, string
  • ora-38790 : BEFORE must be specified with RESETLOGS
  • ora-36342 : (SNSYN200) The format of the CLEAR command is: CLEAR [ ALL | STATUS ] [ AGGREGATES | CHANGES | PRECOMPUTES | NONPRECOMPUTES | CACHE ] FROM var1 [var2, var3...] [USING aggmap]
  • ora-08209 : scngrs: SCN not yet initialized
  • ora-31206 : DBMS_LDAP: PL/SQL - Invalid LDAP search scope.
  • ora-06549 : PL/SQL: failed to dynamically open shared object (DLL): string
  • ora-22994 : source offset is beyond the end of the source LOB
  • ora-28293 : No matched Kerberos Principal found in any user entry
  • ora-12424 : length exceeds binary label size
  • ora-01122 : database file string failed verification check
  • ora-13336 : failure in converting standard diminfo/geometry to LRS dim/geom
  • 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.