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 : 29-04-2017

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

  • ora-34901 : (PPWKDAYS01) Blank lines are not allowed in the DAYNAMES option.
  • ora-19223 : XP0003 - syntax error in XQuery expression
  • ora-06137 : NETTCP: error during connection handshake
  • ora-34000 : (MODCOMP13) You cannot use both workspace object and workspace object as model dimensions, because they are both surrogates of dimension workspace object.
  • ora-12451 : label not designated as USER or DATA
  • ora-24013 : invalid value string, RETRY_DELAY should be non-negative
  • ora-13287 : can't transform unknown gtype
  • ora-24420 : OCISessionRelease must be used to release this session.
  • ora-02475 : maximum cluster chain block count of string has been exceeded
  • ora-06774 : TLI Driver: error sending break mode
  • ora-01582 : unable to open control file for backup
  • ora-12640 : Authentication adapter initialization failed
  • ora-28151 : more than one user name specified for command
  • ora-02835 : Server unable to send signal to client
  • ora-34021 : (MSCGADD04) You must specify a partition when maintaining PARTITION TEMPLATE workspace object.
  • ora-00080 : invalid global area specified by level string
  • ora-30399 : a skip level must have at least one column that allows NULL values
  • ora-27546 : Oracle compiled against IPC interface version string.string found version string.string
  • ora-16631 : operation requires shutdown of database/instance "string"
  • ora-39317 : call to DBMS_SCHEMA_COPY.VALIDATION_CHECK is not legal
  • ora-19916 : %s
  • ora-22956 : The set contains no elements
  • ora-24372 : invalid object for describe
  • ora-01294 : error occurred while processing information in dictionary file string, possible corruption
  • ora-29705 : ACTIVE_INSTANCE_COUNT is string which is incompatible with the value in other instances
  • ora-29336 : Internal error [string] [string] from DBMS_PLUGTS
  • ora-00397 : instance recovery process terminated with error
  • ora-24171 : creation properties are only for internal use
  • ora-00042 : Unknown Service name string
  • ora-29260 : network error: 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.