ORA-16808: unable to resolve the full path name

Cause : An attempt to resolve the full path name from a string failed.

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

Check the Data Guard broker log for the full error stack. This likely the result of an operating system error.

update : 19-08-2017

ORA-16808 - unable to resolve the full path name
ORA-16808 - unable to resolve the full path name

  • ora-29267 : illegal call
  • ora-13523 : unable to allocate required space for return type
  • ora-24332 : invalid object type
  • ora-12703 : this character set conversion is not supported
  • ora-13031 : Invalid Gtype in the SDO_GEOMETRY object for point object
  • ora-01424 : missing or illegal character following the escape character
  • ora-00405 : compatibility type "string"
  • ora-08263 : ora_addr: cannot free listener address
  • ora-30970 : option not supported for XML Index
  • ora-33625 : (FRASSIGN02) You cannot use the APPEND keyword with concat dimension workspace object.
  • ora-12912 : Dictionary managed tablespace specified as temporary tablespace
  • ora-24363 : measurements in characters illegal here
  • ora-30085 : syntax error was found in overlaps predicate
  • ora-13111 : cannot add topo_geometry layer [string] to topology
  • ora-13828 : generated SQL profile name string already exists
  • ora-01682 : read-only DB cannot allocate temporary space in tablespace string
  • ora-38608 : FI itemset minimum-length(string) should not be greater than maximum length(string)
  • ora-31632 : master table "string.string" not found, invalid, or inaccessible
  • ora-30658 : attempt was made to create a temporary table with EXTERNAL organization
  • ora-03230 : segment only contains string blocks of unused space above high water mark
  • ora-02349 : invalid user-defined type - type is incomplete
  • ora-39210 : A PCTSPACE adjustment of string is invalid.
  • ora-00386 : use_indirect_data_buffers not supported
  • ora-08264 : ora_addr: cannot close nameserver
  • ora-31111 : table string cannot be hierarchically enabled
  • ora-16066 : remote archival disabled
  • ora-02430 : cannot enable constraint (string) - no such constraint
  • ora-12914 : Cannot migrate tablespace to dictionary managed type
  • ora-38952 : Source database not compatible
  • ora-31447 : cannot create change tables in the SYS schema
  • 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.