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 : 25-04-2017
ORA-16808

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

  • ora-27078 : unable to determine limit for open files
  • ora-36402 : (XSSPROP03) The property '$string' requires a leading "$" because it is a system-reserved property name.
  • ora-16652 : Fast-Start Failover target standby database is disabled
  • ora-27053 : blocksize in file header not a multiple of logical block size
  • ora-19590 : conversation already active
  • ora-24240 : invalid database access descriptor (DAD) name
  • ora-16254 : change db_name to string in the client-side parameter file (pfile)
  • ora-00298 : Missing or invalid attribute value
  • ora-19300 : Error occurred in uri processingstring
  • ora-12802 : parallel query server lost contact with coordinator
  • ora-33082 : (XSAGDNGL41) In AGGMAP workspace object, the non-dimensioned valueset workspace object must have a parent QDR in its VALUESET statement over the VALUESET's base dimension.
  • ora-01634 : rollback segment number 'string' is about to go offline
  • ora-01049 : Bind by name is not spupportted in streamed RPC
  • ora-10663 : Object has rowid based materialized views
  • ora-02306 : cannot create a type that already has valid dependent(s)
  • ora-23372 : type string in table string is unsupported
  • ora-31435 : an error occurred during the purge operation
  • ora-32018 : parameter cannot be modified in memory on another instance
  • ora-13021 : element not continuous
  • ora-33074 : (XSAGDNGL36) In AGGMAP workspace object, the offset number is not a valid offset into dimension workspace object.
  • ora-29556 : object type has changed
  • ora-16508 : channel handle not initialized
  • ora-22278 : must update the LOB only through the LOB buffers
  • ora-01680 : unable to extend LOB segment by string in tablespace string
  • ora-32154 : Anydata context not specified
  • ora-19377 : no "SQL Tuning Set" with name like "string" exists for owner like "string"
  • ora-00382 : %s not a valid block size, valid range [string..string]
  • ora-02283 : cannot alter starting sequence number
  • ora-22954 : This multiset operation is not supported for this element type.
  • ora-25142 : default storage clause specified twice
  • 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.