ORA-01170: file not found 'string'

Cause : ALL datafiles and, if NORESETLOGS, ALL logfiles MUST be accessible by the process for CREATE CONTROLFILE.

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

The file specified probably contains a typing error. Double check command and the existance of all files and then resubmit.

update : 28-07-2017

ORA-01170 - file not found 'string'
ORA-01170 - file not found 'string'

  • ora-37072 : (XSMCSESS00) Object workspace object has the wrong type.
  • ora-04014 : descending sequences that CYCLE must specify MINVALUE
  • ora-23462 : flavor string in use at site string
  • ora-19276 : XP0005 - XPath step specifies an invalid element/attribute name: (string)
  • ora-22131 : hexadecimal string length is zero
  • ora-01907 : TABLESPACE keyword expected
  • ora-38101 : Invalid column in the INSERT VALUES Clause: string
  • ora-31618 : dump file size too small
  • ora-14520 : Tablespace string block size [string] does not match existing object block size [string]
  • ora-10620 : Operation not allowed on this segment
  • ora-33022 : (XSAGDNGL10) The measure dimension workspace object must be a TEXT or ID base dimension that does not dimension AGGMAP workspace object, but is in the same analytic workspace.
  • ora-12569 : TNS:packet checksum failure
  • ora-22150 : variable-length array has not been initialized
  • ora-00094 : %s requires an integer value
  • ora-39137 : cannot specify a TABLE_EXISTS_ACTION of string for a job with no metadata
  • ora-27074 : unable to determine limit for open files
  • ora-22308 : operation not allowed on evolved type
  • ora-24052 : cannot propagate object type payloads with LOB attributes to an 8.0 release
  • ora-15183 : ASMLIB initialization error [string]
  • ora-16639 : specified instance inactive or currently unavailable
  • ora-13204 : failed to create spatial index table
  • ora-01613 : instance string (thread string) only has string logs - at least 2 logs required to enable.
  • ora-01879 : the hh25 field must be between 0 and 24
  • ora-12623 : TNS:operation is illegal in this state
  • ora-16823 : redo transport mode is incompatible for current operation
  • ora-32100 : operation invalid on transient object
  • ora-29854 : keyword BITMAP may not be used in creating domain indexes
  • ora-30991 : cannot use DOM to add special attribute to schema-based parent
  • ora-30369 : maximum number of columns is 32
  • ora-16811 : apply instance not recorded by the Data Guard broker
  • 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.