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 : 28-04-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-36698 : (XSRELTBL03) QDR dimension workspace object should be in the dimension list that dimensions the relation.
  • ora-01045 : user string lacks CREATE SESSION privilege; logon denied
  • ora-24000 : invalid value string, string should be of the form [SCHEMA.]NAME
  • ora-09284 : sllfop: cannot allocate read buffer
  • ora-28656 : incomplete attribute specification
  • ora-15104 : conflicting CONTENTS options
  • ora-19361 : ONLINE option not allowed with this type of index
  • ora-29361 : value string is outside valid range of 0 to 100
  • ora-12523 : TNS:listener could not find instance appropriate for the client connection
  • ora-32608 : missing INCREMENT or DECREMENT keyword in FOR loop
  • ora-29295 : invalid mime header tag
  • ora-24325 : this OCI operation is not currently allowed
  • ora-15038 : disk 'string' size mismatch with diskgroup [string] [string] [string]
  • ora-01306 : dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents
  • ora-22994 : source offset is beyond the end of the source LOB
  • ora-30463 : 'string' is not a detail table of any summary
  • ora-12653 : Authentication control function failed
  • ora-07213 : slgcs: times error, unable to get wall clock.
  • ora-27022 : skgfqsbi: could not allocate memory for media manager
  • ora-19512 : file search failed
  • ora-09821 : Numeric label is not valid
  • ora-16193 : Primary and standby network encryption mismatch
  • ora-02295 : found more than one enable/disable clause for constraint
  • ora-02803 : Retrieval of current time failed
  • ora-38951 : Target platform string not cross platform compliant
  • ora-36198 : (XSAGGR33) The AGGREGATE operator string does not require a weight, but ARGS variable workspace object specified workspace object as a weight.
  • ora-25196 : keyword MOVE in ALTER TABLE MOVE must immediately follow
  • ora-22915 : cannot ALTER a nested table's storage table to ADD/MODIFY columns
  • ora-36204 : (XSAGOP04N) In AGGMAP workspace object, the NAOPERATOR string must be HFIRST, HLAST or HEVEN.
  • ora-19767 : missing TRACKING keyword
  • 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.