ORA-07230: slemcr: fopen error, unable to open error file.

Cause : Fopen failed to open file.

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

Try to determine which file was not opened. Check that file exists and is accessible.

update : 22-08-2017
ORA-07230

ORA-07230 - slemcr: fopen error, unable to open error file.
ORA-07230 - slemcr: fopen error, unable to open error file.

  • ora-24360 : Type Descriptor Object not specified for Object Bind/Define
  • ora-16406 : Primary and standby database software version mismatch
  • ora-38781 : cannot disable media recovery - have guaranteed restore points
  • ora-10388 : parallel query server interrupt (failure)
  • ora-25249 : dequeue failed, dequeue not allowed for queue string.string
  • ora-01569 : data file too small for system dictionary tables
  • ora-31072 : Too many child nodes in XMLType fragment for updateXML
  • ora-26764 : invalid parameter "string" for local capture "string"
  • ora-01675 : max_commit_propagation_delay inconsistent with other instances
  • ora-19624 : operation failed, retry possible
  • ora-06005 : NETASY: dialogue file read failure
  • ora-25236 : buffer too small for user data
  • ora-13189 : recursive SQL parse failed
  • ora-15157 : rolling upgrade or downgrade is not allowed
  • ora-24201 : duplicate publisher, publisher already added to the queue
  • ora-13334 : LRS segments not connected
  • ora-08275 : Environment variable unset
  • ora-22892 : scoped table "string" does not exist in schema "string"
  • ora-19703 : device command string exceeds maximum length of string
  • ora-30333 : dimension does not exist
  • ora-01425 : escape character must be character string of length 1
  • ora-28044 : unsupported directory type
  • ora-31226 : DBMS_LDAP: MOD_ARRAY size limit exceeded
  • ora-32150 : Cannot perform operation on a null timestamp
  • ora-02330 : datatype specification not allowed
  • ora-30978 : The XML Index is not locally partitioned.
  • ora-40219 : apply result table string is incompatible with current operation
  • ora-16129 : unsupported dml encountered
  • ora-10865 : Control tracing of notification operations
  • ora-19104 : invalid XQueryX: missing attribute string
  • 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.