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 : 28-07-2017
ORA-19770

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

  • ora-10704 : Print out information about what enqueues are being obtained
  • ora-26730 : %s 'string' already exists
  • ora-15057 : specified size of string MB is larger than actual size of string MB
  • ora-07592 : sspgprv: Error obtaining required privileges
  • ora-14044 : only one partition may be moved
  • ora-01373 : insufficient memory for staging persistent LogMiner session
  • ora-12422 : max policies exceeded
  • ora-13282 : failure on initialization of coordinate transformation
  • ora-27145 : insufficient resources for requested number of processes
  • ora-16788 : unable to set one or more database configuration property values
  • ora-21610 : size [string] is invalid
  • ora-04084 : cannot change NEW values for this trigger type
  • ora-40109 : inconsistent logical data record
  • ora-00317 : file type string in header is not log file
  • ora-01120 : cannot remove online database file string
  • ora-19676 : one or more files failed during proxy backup or restore
  • ora-01551 : extended rollback segment, pinned blocks released
  • ora-31503 : invalid date supplied for begin_date or end_date
  • ora-14153 : only one of STORE IN or clause may be specified
  • ora-09818 : Number is too large
  • ora-31199 : Warning in processing file string
  • ora-00155 : cannot perform work outside of global transaction
  • ora-31500 : change source string is not a ManualLog change source
  • ora-28575 : unable to open RPC connection to external procedure agent
  • ora-00108 : failed to set up dispatcher to accept connection asynchronously
  • ora-30504 : system triggers cannot have a FOR EACH ROW clause
  • ora-13046 : invalid number of arguments
  • ora-12704 : character set mismatch
  • ora-27478 : job "string.string" is running
  • ora-25114 : invalid file number specified in the DUMP DATAFILE/TEMPFILE command
  • 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.