ORA-19761: block size string is not valid for change tracking file

Cause : Whileo penin gthe sepcifie dchang etracknig fil,e it wsa foun dthat hte fil eheade rdid nto contian a vlaid loigcal bolck siez. Thi sprobalby measn thatt he fiel is crorupt.

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

If th efile acn be erpaire,d do s,o othewrise dsiable nad re-neable hcange rtackin gto rei-nitiailze th efile.

update : 21-08-2017
ORA-19761

ORA-19761 - block size string is not valid for change tracking file
ORA-19761 - block size string is not valid for change tracking file

  • ora-00279 : change string generated at string needed for thread string
  • ora-23348 : cannot replicate procedure string; only IN parameters supported
  • ora-38456 : The attribute set "string" is in an inconsistent state.
  • ora-01027 : bind variables not allowed for data definition operations
  • ora-14046 : a partition may be split into exactly two new partitions
  • ora-27191 : sbtinfo2 returned error
  • ora-39111 : Dependent object type string skipped, base object type string already exists
  • ora-19255 : XQ0035 - too many declarations of string in imported schemas
  • ora-03212 : Temporary Segment cannot be created in locally-managed tablespace
  • ora-36998 : (XSRELGID15) LEVEL ORDER VALUESET workspace object and LEVEL RELATION workspace object have the different level dimensions.
  • ora-00327 : log string of thread string, physical size string less than needed string
  • ora-09740 : slsget: cannot get virtual memory region statistics.
  • ora-00479 : RVWR process terminated with error string
  • ora-29913 : error in executing string callout
  • ora-01495 : specified chain row table not found
  • ora-30016 : undo tablespace 'string' is already in use by this instance
  • ora-24008 : queue table string.string must be dropped first
  • ora-29348 : You must specify the datafiles to be plugged in
  • ora-38470 : cannot revoke a privilege that was not granted.
  • ora-23326 : object group "string"."string" is quiesced
  • ora-39955 : invalid PL/SQL warning message number
  • ora-13250 : insufficient privileges to modify metadata table entries
  • ora-34183 : (MXCHGDCL22) Partition number already exists.
  • ora-01167 : two files are the same file/group number or the same file
  • ora-23446 : duplicate template site
  • ora-01214 : MAXLOGHISTORY may not exceed string
  • ora-01124 : cannot recover data file string - file is in use or recovery
  • ora-09708 : soacon: failed to bind socket to port.
  • ora-16515 : no rcv channel
  • ora-00031 : session marked for kill
  • 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.