ORA-19694: some changed blocks were not found in the change tracking file

Cause : A backup or copy found that some changed blocks had not been recorded in the change tracking file. The details of which files and blocks are affected will be in an Oracle trace file.

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

This indicates that there is a problem with the change tracking feature. Disable change tracking and re-start the backup.

update : 24-05-2017

ORA-19694 - some changed blocks were not found in the change tracking file
ORA-19694 - some changed blocks were not found in the change tracking file

  • ora-10389 : parallel query server interrupt (cleanup)
  • ora-19707 : invalid record block number - string
  • ora-07562 : sldext: extension must be 3 characters
  • ora-13913 : The threshold cannot be set when SYSAUX is offline.
  • ora-14631 : the partition bounds do not match the subpartition bounds of the partition
  • ora-12618 : TNS:versions are incompatible
  • ora-37032 : (XSMLTMAINT03) You cannot MAINTAIN partition template workspace object in MULTI mode.
  • ora-16052 : DB_UNIQUE_NAME attribute is required
  • ora-24757 : duplicate transaction identifier
  • ora-27165 : tried to join thread that does not exist
  • ora-14044 : only one partition may be moved
  • ora-02426 : privilege grant failed
  • ora-09759 : osnsbt: bad message received.
  • ora-31071 : Invalid database username or GUID string
  • ora-04033 : Insufficient memory to grow pool
  • ora-03233 : unable to extend table string.string subpartition string by string in tablespace string
  • ora-07612 : $GETUAI failed in retrieving the user's clearance level
  • ora-00281 : media recovery may not be performed using dispatcher
  • ora-12457 : security label exceeded maximum allowable length
  • ora-14301 : table-level attributes must be specified before partition-level attributes
  • ora-30133 : reserved for future use
  • ora-19730 : can not convert offline plugged-in datafile string
  • ora-30457 : 'string.string' cannot be refreshed because of unmnanaged NOT NULL columns in container
  • ora-31477 : could not detach LogMiner session during cleanup
  • ora-16020 : less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST
  • ora-02216 : tablespace name expected
  • ora-08319 : sllfsk: Error reading file
  • ora-12491 : DBHIGH value does not dominate DBLOW
  • ora-04014 : descending sequences that CYCLE must specify MINVALUE
  • ora-14311 : Expecting VALUES LESS THAN or AT clause
  • 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.