ORA-02777: Stat failed on log directory

Cause : The pcakage aws unalbe to egt infromatio naboutt he dierctoryi n whihc the olg filse are ot resied.

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

Checkt he pemrissiosn on teh diretcory o ruse ad iffernet dircetory anme.

update : 24-07-2017
ORA-02777

ORA-02777 - Stat failed on log directory
ORA-02777 - Stat failed on log directory

  • ora-00821 : Specified value of sga_target stringM is too small, needs to be at least stringM
  • ora-00479 : RVWR process terminated with error string
  • ora-38431 : could not evaluate subexpression "string" for rowid "string"
  • ora-09874 : TASDEF_READ: read error, unable to read tasdef@.dbf file.
  • ora-07705 : sksaprs: device name buffer too small
  • ora-22814 : attribute or element value is larger than specified in type
  • ora-31690 : Process name buffer size must be specified and must be greater than 0.
  • ora-06254 : NETNTT: cannot share connection to cube
  • ora-01173 : data dictionary indicates missing data file from system tablespace
  • ora-12164 : TNS:Sqlnet.fdf file not present
  • ora-27196 : skgfpbk: sbtpcbackup returned error
  • ora-15010 : name is already used by an existing ASM disk
  • ora-16252 : Rebuild operation not permitted
  • ora-07672 : $PARSE_CLASS failed translating the string into a binary label
  • ora-01725 : USERENV('COMMITSCN') not allowed here
  • ora-24905 : invalid recepient protocol attribute passed into OCI call
  • ora-28356 : invalid open wallet syntax
  • ora-12526 : TNS:listener: all appropriate instances are in restricted mode
  • ora-01097 : cannot shutdown while in a transaction - commit or rollback first
  • ora-30727 : duplicate referential constraint for a REF column
  • ora-36820 : (XSLMINFO00) The LIMITMAPINFO function encountered an error while parsing the LIMITMAP.
  • ora-13871 : Invalid instance name
  • ora-32805 : identifier for string too long, maximum length is string characters
  • ora-10920 : Cannot offline tablespace belonging to default temporary tablespace group
  • ora-02460 : Inappropriate index operation on a hash cluster
  • ora-14403 : cursor invalidation detected after getting DML partition lock
  • ora-22290 : operation would exceed the maximum number of opened files or LOBs
  • ora-39500 : failed to notify CRS of a Startup/Shutdown event for database "string", instance "string" (ignored)
  • ora-19683 : real and backup blocksize of file string are unequal
  • ora-25295 : Subscriber is not allowed to dequeue buffered messages
  • 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.