ORA-19600: input file is string string (string)

Cause : This message identifies the input file for a failed copy operation. Both the file number and name (if the name has been determined) are shown. For a datafile, the file number refers to the datafile's absolute file number as shown in the DBA_DATA_FILES view. For a datafile-copy, the file number refers to the copy's control file record number as shown in the RECID column of the V$DATAFILE_COPY view. For an archived log, the file number refers to the log's control file record number as shown in the RECID column of the V$ARCHIVED_LOG view.

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

See other error message.

update : 26-06-2017

ORA-19600 - input file is string string (string)
ORA-19600 - input file is string string (string)

  • ora-38958 : Source platform string is in different byte order than target platform string
  • ora-24379 : invalid user callback type
  • ora-25261 : JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation
  • ora-02336 : column attribute cannot be accessed
  • ora-12981 : cannot drop column from an object type table
  • ora-32587 : Cannot drop nonexistent string supplemental logging
  • ora-01666 : control file is for a standby database
  • ora-12232 : TNS:No path available to destination
  • ora-12831 : Must COMMIT or ROLLBACK after executing INSERT with APPEND hint
  • ora-02025 : all tables in the SQL statement must be at the remote database
  • ora-12630 : Native service operation not supported
  • ora-02833 : Server was unable to close file
  • ora-12838 : cannot read/modify an object after modifying it in parallel
  • ora-19861 : additional backup pieces cannot be validated in this conversation
  • ora-22819 : scope of input value does not correspond to the scope of the target
  • ora-03200 : the segment type specification is invalid
  • ora-26092 : only LONG or LOB types can be partial
  • ora-24018 : STOP_QUEUE on string failed, outstanding transactions found
  • ora-16131 : An error occurred during a Terminal Recovery of the standby.
  • ora-00382 : %s not a valid block size, valid range [string..string]
  • ora-37153 : unknown exception caught: (case string)
  • ora-22872 : OID INDEX clause not allowed on tables with primary key based object identifiers
  • ora-00821 : Specified value of sga_target stringM is too small, needs to be at least stringM
  • ora-39048 : Unable to start all workers; only string worker(s) available.
  • ora-00374 : parameter db_block_size = string invalid ; must be a multiple of string in the range [string..string]
  • ora-30438 : unable to access named pipe 'string'
  • ora-27015 : skgfcls: failed to close the file
  • ora-00001 : unique constraint (string.string) violated
  • ora-24075 : cannot specify agent with NULL address and non-NULL protocol
  • ora-08005 : specified row does not exist
  • 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.