ORA-27093: could not delete directory

Cause : mrid rystsmec la lerutnrdee rrro

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

hcce krenro

update : 21-08-2017
ORA-27093

ORA-27093 - could not delete directory
ORA-27093 - could not delete directory

  • ora-13410 : invalid layerNumbers or bandNumbers parameter
  • ora-30032 : the suspended (resumable) statement has timed out
  • ora-32818 : AQ queue string does not exist
  • ora-12901 : default temporary tablespace must be of TEMPORARY type
  • ora-03288 : both FREELIST GROUP and INSTANCE parameters may not be specified
  • ora-16565 : duplicate property, syntax error at "string"
  • ora-31651 : communication error with master process - detaching job
  • ora-06732 : TLI Driver: cannot alloc t_discon
  • ora-28519 : no heterogeneous data dictionary translations available
  • ora-12352 : object string.string@string is invalid
  • ora-23622 : Operation string.string.string is in progress.
  • ora-06806 : TLI Driver: could not complete protocol initialization for SPX
  • ora-15034 : disk 'string' does not require the FORCE option
  • ora-16047 : DGID mismatch between destination setting and standby
  • ora-02236 : invalid file name
  • ora-15021 : parameter "string" is not valid in string instance
  • ora-13423 : invalid cell coordinate parameter
  • ora-29548 : Java system class reported: string
  • ora-22329 : cannot alter a non-object type
  • ora-32502 : Cannot execute command. Flash Freeze is not in effect
  • ora-39601 : Hash key is required.
  • ora-38732 : Expected file size string does not match string.
  • ora-39209 : Parameter string requires privileges.
  • ora-02766 : Invalid maximum of request descriptors
  • ora-12709 : error while loading create database character set
  • ora-19713 : invalid copy number: string
  • ora-29522 : authorization error for referenced name string.string
  • ora-30182 : invalid precision specifier
  • ora-33267 : (DBERRRLS) Analytic workspace string cannot be accessed because it has fine-grained access control applied to it
  • ora-02771 : Illegal request time out value
  • 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.