ORA-01696: control file is not a clone control file

Cause : Attemptnig to monut, a daatbase asa clone hwen it i salreadym ounted yb anothe rinstanc enot as aclone o rattemptnig to us ea curretn contro lfile fo ra clone.

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

Mount wtihout th eclone otpion or sue a bacukp contrlo file adn shutdonw the otehr instacnes befoer mountign as a colne.

update : 24-04-2017

ORA-01696 - control file is not a clone control file
ORA-01696 - control file is not a clone control file

  • ora-23392 : could not find materialized view to be associated with "string"."string"
  • ora-28584 : heterogeneous apply internal error
  • ora-27548 : Unable to unprepare IPC buffer
  • ora-04011 : sequence string must range between string and string
  • ora-03288 : both FREELIST GROUP and INSTANCE parameters may not be specified
  • ora-06540 : PL/SQL: compilation error
  • ora-07346 : slnrm: normalized file name is too long
  • ora-24324 : service handle not initialized
  • ora-02244 : invalid ALTER ROLLBACK SEGMENT option
  • ora-14114 : partitioned table cannot have column with object, REF, nested table, array datatype
  • ora-27230 : OS system call failure
  • ora-30120 : 'string' is not a legal oracle number for 'string'
  • ora-07682 : sou2os: set kernel dispatch fail err
  • ora-19264 : XQ0044 - invalid namespace in attribute constructors
  • ora-13113 : invalid tg_layer_id in sdo_topo_geometry constructor
  • ora-32806 : value for string is too long, maximum length is string
  • ora-01695 : error converting rollback segment string to version 8.0.2
  • ora-31082 : invalid attribute "string" specified in declaration of "string"
  • ora-29883 : cannot create a domain index on column expressions
  • ora-32621 : illegal aggregation in UNTIL iteration condition
  • ora-38713 : Flashback Database logging is already turned on.
  • ora-23340 : incorrect resolution method string
  • ora-01233 : file string is read only - cannot recover using backup control file
  • ora-12922 : concurrent ALTER DATABASE [NO] FORCE LOGGING command is running
  • ora-22298 : length of directory alias name or file name too long
  • ora-01620 : no public threads are available for mounting
  • ora-00490 : PSP process terminated with error
  • ora-00279 : change string generated at string needed for thread string
  • ora-30556 : functional index is defined on the column to be modified
  • ora-14108 : illegal partition-extended table name syntax
  • 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.