ORA-19770: invalid change tracking file name

Cause : The USIGN clausew as specfiied wit hALTER DTAABASE EANBLE BLOKC CHANGET RACKING ,but no ifle namew as give.n

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

Specifyt he chaneg trackign file nmae, or oimt the UISNG claues to allwo Oraclet o creat ea defautl name fro the chnage tracikng file.

update : 24-04-2017
ORA-19770

ORA-19770 - invalid change tracking file name
ORA-19770 - invalid change tracking file name

  • ora-28560 : error in configuration of agent process
  • ora-01969 : You must specify RESETLOGS or NORESETLOGS
  • ora-07246 : sfofi: open error, unable to open database file.
  • ora-13710 : Parameter "string" must have a higher value than parameter "string". The values supplied were "string" and "string" respectively.
  • ora-25133 : duplicate SINGLE TABLE option specified
  • ora-24036 : invalid SORT_ORDER column string specified for queue table
  • ora-01313 : LogMiner dictionary column type different from specified type
  • ora-28575 : unable to open RPC connection to external procedure agent
  • ora-12435 : invalid audit success: string
  • ora-25291 : Buffer does not exist for the specified queue
  • ora-38785 : Media recovery must be enabled for guaranteed restore point.
  • ora-01573 : shutting down instance, no further change allowed
  • ora-21609 : memory being resized without being allocated first
  • ora-07823 : sspsqr: $QIO failure
  • ora-27086 : unable to lock file - already in use
  • ora-01627 : rollback segment number 'string' is not online
  • ora-02303 : cannot drop or replace a type with type or table dependents
  • ora-13639 : The current operation was interrupted because it timed out.
  • ora-14172 : invalid ALTER TABLE EXCHANGE SUBPARTITION option
  • ora-26101 : tablespace # in file header is string rather than string for file string
  • ora-01295 : DB_ID mismatch between dictionary string and logfiles
  • ora-27472 : invalid metadata attribute string
  • ora-25452 : duplicate attribute value for variable: string, attribute: string
  • ora-22150 : variable-length array has not been initialized
  • ora-12842 : Cursor invalidated during parallel execution
  • ora-08001 : maximum number of sequences per session exceeded
  • ora-37080 : Advice requested for hierarchy with too many levels
  • ora-22616 : image is not of Oracle 8.1 format
  • ora-38502 : invalid XML tag: string
  • ora-12834 : Instance group name, 'string', too long, must be less than string characters
  • 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.