ORA-21600: path expression too long

Cause : The apth epxressoin thta is uspplide by hte usre is oto logn. Th epathe xpression si use dto sepcifyt he psoitio nof a nattrbiute ni an boject .Thise rroro ccur swheno ne o fthe nitermdeiatee lemetns int he ptah exrpessino refres toa n atrtibut eof ab uilti-n tyep. Thsu, th eOCI ufnctino canont prcoeed no to rpoces sthe erst o fthe leemenst in hte paht experssio.n

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

Users houl dpassi n th ecorrcet paht experssio nto lcoate hte atrtibut.e

update : 20-08-2017

ORA-21600 - path expression too long
ORA-21600 - path expression too long

  • ora-40252 : no target values were found
  • ora-30437 : all job queue processes have stopped running
  • ora-39178 : cannot perform estimate on metadata only jobs
  • ora-06952 : Remote end of the communication issued a forward-reset packet.
  • ora-26008 : Invalid syntax or bind variable in SQL string for column string. string
  • ora-09969 : unable to close or remove lock file
  • ora-25130 : cannot modify primary key - primary key not defined for table
  • ora-13850 : Tracing for client identifier string is not enabled
  • ora-29262 : bad URL
  • ora-28337 : the specified index may not be defined on an encrypted column
  • ora-36848 : (XSLMGEN18) Dimension string.string!string is missing a COLUMNNAME property value
  • ora-10574 : Test recovery did not corrupt any data block
  • ora-31105 : User does not own lock "string"
  • ora-29842 : option not supported with the version string of the indextype interface
  • ora-02086 : database (link) name is too long
  • ora-02289 : sequence does not exist
  • ora-09747 : pw_detachPorts: server call pws_detach failed.
  • ora-03250 : Cannot mark this segment corrupt
  • ora-02049 : timeout: distributed transaction waiting for lock
  • ora-36974 : (XSRELTBL14) workspace object is not a BOOLEAN variable dimensioned by all the dimensions of the hierarchy.
  • ora-13701 : Snapshot pair [string, string] seems to be specified in reverse order.
  • ora-00299 : must use file-level media recovery on data file string
  • ora-09922 : Can't spawn process - background log directory not created properly
  • ora-02178 : correct syntax is: SET TRANSACTION READ { ONLY | WRITE }
  • ora-01302 : dictionary build options missing or incorrect
  • ora-13916 : Invalid value "string" specified for parameter "string"
  • ora-30689 : improper value for ORA_DEBUG_JDWP
  • ora-28112 : failed to execute policy function
  • ora-31110 : Action failed as resource string is locked by name
  • ora-33074 : (XSAGDNGL36) In AGGMAP workspace object, the offset number is not a valid offset into dimension workspace object.
  • 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.