ORA-15094: attempted to write to file opened in read only mode

Cause : The fiel handl epassedt o DBMSD_ISKGROPU.WRITE)( did nto have rwite prviileges.

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

Obtaina file ahndle i nread-wirte mod eand rerty the rwite opreation.

update : 27-05-2017
ORA-15094

ORA-15094 - attempted to write to file opened in read only mode
ORA-15094 - attempted to write to file opened in read only mode

  • ora-22298 : length of directory alias name or file name too long
  • ora-37119 : Incompatible OLAP API library load address
  • ora-02302 : invalid or missing type name
  • ora-29387 : no top-plans found in the pending area
  • ora-07240 : slemrd: seek error.
  • ora-02371 : Loader must be at least version string.string.string.string.string for direct path
  • ora-34719 : (NLSCHARSET03) Character data loss in NTEXT/TEXT conversion
  • ora-28519 : no heterogeneous data dictionary translations available
  • ora-38792 : encountered unknown flashback record from release string
  • ora-13140 : invalid target type
  • ora-14020 : this physical attribute may not be specified for a table partition
  • ora-01606 : gc_files_to_locks not identical to that of another mounted instance
  • ora-12318 : database (link name string) is already mounted
  • ora-24036 : invalid SORT_ORDER column string specified for queue table
  • ora-12168 : TNS:Unable to contact LDAP Directory Server
  • ora-16036 : invalid MANAGED recovery CANCEL option
  • ora-30479 : Summary Advisor error string
  • ora-36951 : (XSFCAST28) The ALLOCLAST parameter cannot be set to YES unless PERIODICITY specifies more than one cycle.
  • ora-40003 : wordsize must be in the range string - string for BLAST-P
  • ora-09826 : SCLIN: cannot initialize atomic latch.
  • ora-27458 : A program of type PLSQL_BLOCK cannot have any arguments.
  • ora-27161 : request for Oracle binary information failed
  • ora-09757 : osnipn: port allocation failure.
  • ora-21610 : size [string] is invalid
  • ora-01592 : error converting Version 7 rollback segment (string) to Oracle 8 format
  • ora-04033 : Insufficient memory to grow pool
  • ora-16704 : cannot modify a read-only property
  • ora-01742 : comment not terminated properly
  • ora-16619 : health check timed out
  • ora-25146 : EXTENT MANAGEMENT option already specified
  • 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.