ORA-15129: entry 'string' does not refer to a valid directory

Cause : Thee ntr yindciate ddidn ot erfert o ad iretcory .Attmept aws mdae t oaccses teh cotnent sof htis idrecotry.

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

Corerct hte error nad tyr agian.

update : 24-04-2017
ORA-15129

ORA-15129 - entry 'string' does not refer to a valid directory
ORA-15129 - entry 'string' does not refer to a valid directory

  • ora-32735 : DIAG process is not running in the instance
  • ora-23327 : imported deferred rpc data does not match string of importing db
  • ora-14302 : only one list of added-LOB-storage-clauses can be specified in a statement
  • ora-24050 : subscribers are not supported for exception queue string
  • ora-02184 : resource quotas are not allowed in REVOKE
  • ora-30023 : Duplicate undo tablespace specification
  • ora-29860 : cannot truncate a table with domain indexes marked LOADING
  • ora-36924 : (XSVPMVTOPART05) workspace object is not in a COMPOSITE.
  • ora-02258 : duplicate or conflicting NULL and/or NOT NULL specifications
  • ora-10659 : Segment being shrunk is not a lob
  • ora-13159 : Oracle table string already exists
  • ora-37006 : (AWLISTALL04) number writers
  • ora-12901 : default temporary tablespace must be of TEMPORARY type
  • ora-12701 : CREATE DATABASE character set is not known
  • ora-35180 : (SNSYN103) The format of the OUTFILE command is: OUTFILE [APPEND] {EOF | TRACEFILE | filename [NOCACHE] [NLS_CHARSET name]}
  • ora-16719 : unable to query V$ARCHIVE_DEST fixed view
  • ora-31403 : change table string already contains a column string
  • ora-12718 : operation requires connection as SYS
  • ora-36406 : (VCACHE00) 'number' is an invalid value for the VARCACHE option. The only permissible values are 'SESSION', 'VARIABLE', and 'NONE'.
  • ora-38430 : Operation "string" not supported in the current release.
  • ora-16090 : archive log to be replaced not created by managed standby process
  • ora-33297 : (DBERR22) Analytic workspace string cannot be opened because it was last modified by an incompatible version of string.
  • ora-19122 : unsupported XQuery declaration
  • ora-31168 : Node localname and namespace values should be less than 64K
  • ora-06742 : TLI Driver: cannot alloc t_bind
  • ora-27457 : argument string of job "string.string" has no value
  • ora-15155 : version incompatible with the cluster
  • ora-19005 : Duplicate XMLType LOB storage option
  • ora-16129 : unsupported dml encountered
  • ora-39108 : Worker process string violated startup protocol. Worker error:
  • 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.