ORA-22605: FDO handle [string] is not initialized

Cause : Attepmtt ou s ea nuinntiilaiezdF D Ohnadel.

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

Ues COIiPclkeFrdIonti ot niiitailz eFOD ahnlde."

update : 28-04-2017
ORA-22605

ORA-22605 - FDO handle [string] is not initialized
ORA-22605 - FDO handle [string] is not initialized

  • ora-28670 : mapping table cannot be dropped due to an existing bitmap index
  • ora-31461 : logfile location string contains no files that match pattern string
  • ora-23501 : refresh template cannot be instantiated for database with compatibilty equal to or less than 8.0
  • ora-02170 : FREELIST GROUPS storage option not allowed
  • ora-10660 : Segment is a shared lob segment
  • ora-34722 : (NLSCHARSET05) CAUTION: Character data loss in character set conversion from string to string
  • ora-25204 : invalid value, SEQUENCE_DEVIATION should be BEFORE or TOP
  • ora-32731 : Another Parallel Oradebug session is in progress
  • ora-07848 : sllfrb: $GET failure
  • ora-08183 : Flashback cannot be enabled in the middle of a transaction
  • ora-14159 : duplicate subpartition name
  • ora-31492 : could not set session parameters for LogMiner session
  • ora-16791 : unable to check the existence of the standby redo logs
  • ora-32056 : invalid number of extents
  • ora-01192 : must have at least one enabled thread
  • ora-29837 : insufficient privileges to execute implementation type
  • ora-13436 : GeoRaster metadata dimensionSize error
  • ora-09276 : All bequeath database links must be loopback database links
  • ora-32761 : Turn off Temp LOB Ref Count Feature
  • ora-25407 : connection terminated
  • ora-39087 : directory name string is invalid
  • ora-02171 : invalid value for MAXLOGHISTORY
  • ora-36998 : (XSRELGID15) LEVEL ORDER VALUESET workspace object and LEVEL RELATION workspace object have the different level dimensions.
  • ora-13193 : failed to allocate space for geometry
  • ora-29288 : invalid file name
  • ora-19767 : missing TRACKING keyword
  • ora-02187 : invalid quota specification
  • ora-39950 : invalid parameter for PLSQL warnings flag
  • ora-32509 : watchpoint was already deleted
  • ora-06006 : NETASY: dialogue execute failure
  • 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.