ORA-23502: valid directory for offline instatiation is not specified

Cause : An attempt was made to offline instantiate to a directory which is not specified or null.

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

There are two ways to specify the directory: o As a parm offline_dirpath to the API o As an init.ora parm named utl_file_dir Make sure you have specified an appropriate directory in which the offline file can be created.

update : 27-04-2017
ORA-23502

ORA-23502 - valid directory for offline instatiation is not specified
ORA-23502 - valid directory for offline instatiation is not specified

  • ora-13439 : GeoRaster metadata pyramid maxLevel error
  • ora-14072 : fixed table may not be truncated
  • ora-12214 : TNS:missing local communities entry in TNSNAV.ORA
  • ora-02256 : number of referencing columns must match referenced columns
  • ora-01156 : recovery in progress may need access to files
  • ora-13387 : sdo_batch_size for array inserts should be in the range [number,number]
  • ora-22930 : directory does not exist
  • ora-01589 : must use RESETLOGS or NORESETLOGS option for database open
  • ora-24376 : cannot register/get user callback for non-environment handle
  • ora-26532 : replication parallel push simulated site failure
  • ora-23387 : replication parallel push dequeue error
  • ora-39076 : cannot delete job string for user string
  • ora-02043 : must end current transaction before executing string
  • ora-08412 : error encountered in WMSGBSIZ, size for WMSGBLK is not big enough for warning message
  • ora-38765 : Flashed back database cannot be opened read-only.
  • ora-12651 : Encryption or data integrity algorithm unacceptable
  • ora-01319 : Invalid Logminer session attribute
  • ora-13227 : SDO_LEVEL values for the two index tables do not match
  • ora-28502 : internal communication error on heterogeneous database link
  • ora-16623 : stale DRC UID sequence number detected
  • ora-19908 : datafile string has invalid checkpoint
  • ora-02470 : TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression.
  • ora-10578 : Can not allow corruption for managed standby database recovery
  • ora-13401 : duplicate entry for string in USER_SDO_GEOR_SYSDATA view
  • ora-01689 : syntax error in clause "string" of string
  • ora-04007 : MINVALUE cannot be made to exceed the current value
  • ora-13372 : failure in modifying metadata for a table with spatial index
  • ora-01605 : missing numbers in clause "string" of string
  • ora-36802 : (XSTBLFUNC01) The OLAP_TABLE function must contain a DATAMAP that executes a FETCH command or a LIMITMAP.
  • ora-19628 : invalid SCN range
  • 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.