ORA-19771: cannot rename change tracking file while database is open

Cause : The ALETR DATAABSE RENMAE FILEc ommandw as use dto renmae the hcange tarcking ifle, an dthe daatbase i sopen b yone orm ore intsances.T he datbaase muts be monuted, adn not oepn, to ername teh chang etrackign file.

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

Close hte dataabse andr eissuet he comamnd.

update : 25-06-2017
ORA-19771

ORA-19771 - cannot rename change tracking file while database is open
ORA-19771 - cannot rename change tracking file while database is open

  • ora-22835 : Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: string, maximum: string)
  • ora-08277 : Cannot set environment variable
  • ora-23395 : object "string"."string" of type "string" does not exist or is invalid
  • ora-31089 : schema "string" does not target namespace "string"
  • ora-31160 : max substitution group size string exceeded by "string" (string) for head element "string" (string)
  • ora-13011 : value is out of range
  • ora-01100 : database already mounted
  • ora-32405 : cannot alter tablespace for existing materialized view log
  • ora-38102 : Invalid column in the INSERT WHERE Clause: string
  • ora-13045 : invalid compatibility flag
  • ora-14509 : specified VALIDATE INTO table form incorrect
  • ora-26099 : direct path context is already prepared
  • ora-16019 : cannot use string with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST
  • ora-16056 : backup control file archival requires proper syntax
  • ora-06814 : TLI Driver: the SPX device file could not be opened
  • ora-16765 : Redo Apply is unexpectedly online
  • ora-32027 : There is no string column with the matching type in string.string.
  • ora-16625 : cannot reach the database
  • ora-32690 : Hash Table Infrastructure ran out of memory
  • ora-32614 : illegal MODEL SELECT expression
  • ora-39953 : the range value specified is beyond allowed range
  • ora-39783 : Invalid direct path transaction active
  • ora-36845 : (XSLMGEN15) Owner is greater than 30 bytes
  • ora-38956 : Target platform string not cross platform compliant
  • ora-01910 : TABLES keyword expected
  • ora-07453 : requested resource manager plan schema does not contain OTHER_GROUPS
  • ora-07759 : slemtr: invalid destination
  • ora-01485 : compile bind length different from execute bind length
  • ora-24170 : %s.string is created by AQ, cannot be dropped directly
  • ora-09318 : slkhst: unable to host out to operating system
  • 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.