ORA-01565: error in identifying file 'string'

Cause : An error occurred while trying to identify a file.

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

Check the error stack for detailed information.

update : 24-04-2017

ORA-01565 - error in identifying file 'string'
ORA-01565 - error in identifying file 'string'

  • ora-30203 : Cannot open mesage file
  • ora-00270 : error creating archive log string
  • ora-30447 : internal data for run number string is inconsistent
  • ora-36378 : (XSAGTHRWEIGHT) While running AGGREGATE with multiple threads, the weight variable workspace object specified by your ARGS variable workspace object must exist in the same analytic workspace as your AGGMAP workspace object.
  • ora-27034 : maximum length of ORACLE_SID exceeded
  • ora-14154 : only one of STORE IN or clause may be specified
  • ora-06020 : NETASY: initialisation failure
  • ora-23454 : flavor string not defined for object group "string"."string"
  • ora-31105 : User does not own lock "string"
  • ora-37084 : Output valueset string must match string's dimensionality
  • ora-29894 : base or varray datatype does not exist
  • ora-13120 : invalid face_id [string]
  • ora-29542 : class string already defined by source string
  • ora-02706 : osnshs: host name too long
  • ora-02188 : Cannot enable instance publicly
  • ora-31099 : XDB Security Internal Error
  • ora-27006 : sbtremove returned error
  • ora-38706 : Cannot turn on FLASHBACK DATABASE logging.
  • ora-09925 : Unable to create audit trail file
  • ora-06255 : NETNTT: cannot read pid of remote process
  • ora-37007 : (AWLISTALL05) number writer
  • ora-14062 : one or more of table's partitions reside in a read-only tablespace
  • ora-22634 : Error adding new instance to AnyDataSet
  • ora-06108 : NETTCP: connect to host failed
  • ora-13260 : layer table string does not exist
  • ora-16529 : bad sender id
  • ora-16253 : Logical Standby cannot start due to incomplete terminal apply
  • ora-16199 : Terminal recovery failed to recover to a consistent point
  • ora-16148 : user requested expiration of managed recovery operation
  • ora-16797 : database is not using a server parameter file
  • 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.