ORA-19772: change tracking file name exceeds limit of string characters

Cause : The nmae speicfied ofr thec hanget rackign filei s tool ong.

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

Speciyf a shroter cahnge tarckingf ile nmae.

update : 26-04-2017
ORA-19772

ORA-19772 - change tracking file name exceeds limit of string characters
ORA-19772 - change tracking file name exceeds limit of string characters

  • ora-13374 : SDO_MBR not supported for geodetic data
  • ora-29523 : authorization error for unknown referenced name
  • ora-15150 : instance lock mode 'string' conflicts with other ASM instance(s)
  • ora-02299 : cannot validate (string.string) - duplicate keys found
  • ora-29848 : error occurred in the execution of ODCIINDEXMERGEPARTITION routine
  • ora-06811 : TLI Driver: could not set the IPX network number at init
  • ora-29344 : Owner validation failed - failed to match owner 'string'
  • ora-26732 : invalid file group string privilege
  • ora-13363 : no valid ETYPE in the geometry
  • ora-14049 : invalid ALTER TABLE MODIFY PARTITION option
  • ora-35062 : (QFGET01) Duplicate files found for extension number number of EIF file string.
  • ora-15120 : ASM file name 'string' does not begin with the ASM prefix character
  • ora-30647 : error retrieving access parameters for external table string.string
  • ora-31495 : error in synchronous change table on "string"."string"
  • ora-26036 : subpartition load specified but table string is not subpartitioned
  • ora-19931 : file string has invalid creation SCN string
  • ora-25531 : MTTR specified is too small: string
  • ora-32403 : cannot use new values from mv log on "string"."string"
  • ora-00163 : internal database name length string is greater than maximum (string)
  • ora-10659 : Segment being shrunk is not a lob
  • ora-29556 : object type has changed
  • ora-16120 : dependencies being computed for transaction at SCN string
  • ora-21522 : attempted to use an invalid connection in OCI (object mode only)
  • ora-24354 : number fetched too large to fit in COBOL display type buffer.
  • ora-26747 : The one-to-many transformation function string encountered the following error: string
  • ora-28342 : integrity check fails on column key
  • ora-16652 : Fast-Start Failover target standby database is disabled
  • ora-00409 : COMPATIBLE needs to be string or higher to use AUTO SEGMENT SPACE MANAGEMENT
  • ora-02148 : EXCLUSIVE specified multiple times
  • ora-37117 : olapi history retention has been disabled
  • 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.