ORA-19594: control file already included as string

Cause : The control file is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of the control file.

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

No action required - the conversation is still active, and more files can be specified.

update : 23-04-2017

ORA-19594 - control file already included as string
ORA-19594 - control file already included as string

  • ora-13002 : specified level is out of range
  • ora-06541 : PL/SQL: compilation error - compilation aborted
  • ora-39003 : unable to get count of total workers alive
  • ora-07707 : error in archive text: need tape label name
  • ora-12222 : TNS:no support is available for the protocol indicated
  • ora-19664 : file type: string, file name: string
  • ora-08343 : srclose: failed to close a redo server connection
  • ora-16655 : specified target standby database invalid
  • ora-28357 : password required to open the wallet
  • ora-10570 : Test recovery complete
  • ora-15094 : attempted to write to file opened in read only mode
  • ora-29299 : Invalid handle for piecewise compress or uncompress
  • ora-02464 : Cluster definition can not be both HASH and INDEX
  • ora-33558 : (LOCKCHECK01) The status or contents of the workspace object dimension cannot be changed while the LOCK_LANGUAGE_DIMS option is set to value.
  • ora-02307 : cannot alter with REPLACE option a type that is not valid
  • ora-06592 : CASE not found while executing CASE statement
  • ora-25294 : Cannot propagate user buffered messages to a database with version lower than 10.2
  • ora-09705 : spcre: cannot initialize latch semaphore
  • ora-19701 : device name exceeds maximum length of string
  • ora-00476 : RECO process terminated with error
  • ora-24194 : attempt to read data in a message as the wrong type
  • ora-13466 : format not appropriate for specified compression method
  • ora-33050 : (XSAGDNGL24) AGGMAP workspace object cannot be used to aggregate workspace object, because it is defined in a different analytic workspace.
  • ora-13504 : No SYSAUX datafile clause specified
  • ora-00307 : requested INSTANCE_NUMBER out of range, maximum is string
  • ora-36179 : (XSNOAGM) No AGGMAP was specified for VARIABLE workspace object.
  • ora-16235 : DDL skipped because import has occurred
  • ora-06121 : NETTCP: access failure
  • ora-12415 : A column of another datatype exists on the specified table
  • ora-21705 : service context is invalid
  • 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.