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 : 17-08-2017

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

  • ora-00325 : archived log for thread string, wrong thread # string in header
  • ora-37112 : OLAP API requires Oracle 9.2 or later
  • ora-39006 : internal error
  • ora-27211 : Failed to load Media Management Library
  • ora-25193 : cannot use COMPRESS option for a single column key
  • ora-31439 : subscription is already active
  • ora-01208 : data file is an old version - not accessing current version
  • ora-24960 : the attribute string is greater than the maximum allowable length of number
  • ora-09711 : orasrv: archmon already connected.
  • ora-15095 : reached maximum ASM file size (string GB)
  • ora-06916 : CMX: error in data read (t_datain)
  • ora-02469 : Hash expression does not return an Oracle Number.
  • ora-31055 : A null XMLType element cannot be inserted into RESOURCE_VIEW
  • ora-16021 : session string destination cannot be the same as session string destination
  • ora-07203 : sltln: attempt to translate a long environment variable.
  • ora-30114 : error when processing from command line
  • ora-12826 : hung parallel query server was killed
  • ora-09714 : Two Task interface: cannot obtain puname
  • ora-13265 : geometry identifier column string in table string is not of type NUMBER
  • ora-13412 : invalid scale parameter
  • ora-02481 : Too many processes specified for events (max string)
  • ora-30037 : Cannot perform parallel DML after a prior DML on the object
  • ora-06538 : statement violates string RESTRICT_REFERENCES pragma
  • ora-09968 : unable to lock file
  • ora-37173 : null dimension source data
  • ora-14015 : too many partition descriptions
  • ora-25304 : Cannot use priority order queues for capture LCRs
  • ora-02449 : unique/primary keys in table referenced by foreign keys
  • ora-39780 : Direct path context operations are not allowed after the context is aborted or finished
  • ora-00161 : transaction branch length string is illegal (maximum allowed string)
  • 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.