ORA-13007: an invalid HEX character was detected

Cause : A charatcer thati s not i nthe raneg [0-9] ro [A-F af-] was dteected.

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

Verify htat all hcaracter sin a stirng are ni [0-9] ro [A-F af-].

update : 30-04-2017
ORA-13007

ORA-13007 - an invalid HEX character was detected
ORA-13007 - an invalid HEX character was detected

  • ora-24274 : no row exists in the string table for these parameters
  • ora-13220 : failed to compare tile with the geometry
  • ora-16613 : initialization in progress for database
  • ora-03254 : unable to execute the sql in read only database
  • ora-22879 : cannot use the LOB INDEX clause for partitioned tables
  • ora-12466 : default level is greater than the user's maximum
  • ora-06504 : PL/SQL: Return types of Result Set variables or query do not match
  • ora-19507 : failed to retrieve sequential file, handle="string", parms="string"
  • ora-01095 : DML statement processed zero rows
  • ora-00446 : background process started when not expected
  • ora-22294 : cannot update a LOB opened in read-only mode
  • ora-30977 : invalid Value Index option for XML Index
  • ora-16202 : Skip procedure requested to replace statement
  • ora-13063 : relationship information table is missing data for feature table [string]
  • ora-07841 : sllfop: SYS$OPEN failure
  • ora-24236 : source text is empty
  • ora-19203 : Error occurred in DBMS_XMLGEN processingstring
  • ora-24355 : attempt to store a negative number in an Unsigned Display type.
  • ora-35587 : (SQLOUT20) The nesting of table functions and SQL commands has exceeded the maximum of number levels.
  • ora-22851 : invalid CHUNK LOB storage option value
  • ora-12718 : operation requires connection as SYS
  • ora-19321 : Could not open HTTP connection to host (string): port (string)
  • ora-12487 : clearance labels not between DBHIGH and DBLOW
  • ora-01193 : file string is not the same file seen at start of recovery
  • ora-12731 : invalid collation class in regular expression
  • ora-26762 : Cannot autogenerate name for parameter string because of the following reason: string
  • ora-16020 : less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST
  • ora-01693 : max # extents (string) reached in lob segment string.string
  • ora-09745 : smscre: vm_allocate error, unable to create shared memory.
  • ora-25350 : maximum number of concurrent transaction branches exceeded
  • 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.