ORA-01665: control file is not a standby control file

Cause : Attempting to mount, recover or activate a standby database without a standby control file.

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

Create a standby control file before attempting to use the database as a standby database.

update : 24-05-2017

ORA-01665 - control file is not a standby control file
ORA-01665 - control file is not a standby control file

  • ora-01354 : Supplemental log data must be added to run this command
  • ora-12708 : error while loading create database NLS parameter string
  • ora-14626 : values being added already exist in DEFAULT subpartition
  • ora-32618 : incorrect use of MODEL PREVIOUS function
  • ora-12465 : Not authorized for read or write on specified groups or compartments
  • ora-26694 : error while enqueueing into queue string.string
  • ora-09803 : Allocation of string buffer failed.
  • ora-37102 : (XSVPART02) Invalid partition name string.
  • ora-25296 : Queue Table string has a buffered queue string
  • ora-36802 : (XSTBLFUNC01) The OLAP_TABLE function must contain a DATAMAP that executes a FETCH command or a LIMITMAP.
  • ora-25281 : complete reciever information not provided to non-repudiate reciever
  • ora-06906 : CMX: cannot get maximum packet size from CMX
  • ora-07218 : slkhst: could not perform host operation
  • ora-00348 : single-process redo failure. Must abort instance
  • ora-23360 : only one materialized view for master table "string" can be created
  • ora-14019 : partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE
  • ora-09839 : removeCallback: callback port is not in the callback set.
  • ora-01028 : internal two task error
  • ora-24390 : Unsupported scrollable cursor operation
  • ora-28181 : proxy 'string' failed to enable one or more of the specified initial roles for client 'string'
  • ora-09946 : File name too long for buffer
  • ora-25407 : connection terminated
  • ora-06441 : ssvwatev: Incorrect parameter passed to function call
  • ora-30487 : ORDER BY not allowed here
  • ora-12826 : hung parallel query server was killed
  • ora-13044 : the specified tile size is smaller than the tolerance
  • ora-01804 : failure to initialize timezone information
  • ora-10261 : Limit the size of the PGA heap
  • ora-13870 : Database-wide SQL tracing is not enabled
  • ora-28667 : USING INDEX option not allowed for the primary key of an IOT
  • 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.