ORA-19767: missing TRACKING keyword

Cause : Syntxa errro.

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


update : 18-08-2017

ORA-19767 - missing TRACKING keyword
ORA-19767 - missing TRACKING keyword

  • ora-13025 : polygon does not close
  • ora-07709 : sksaprs: archiving to a remote host is not allowed
  • ora-36665 : (XSDPART03) workspace object is not in the dimension list of the PARTITION TEMPLATE.
  • ora-29909 : label for the ancillary operator is not a literal number
  • ora-06602 : LU6.2 Driver: Error allocating context area
  • ora-01669 : standby database control file not consistent
  • ora-10690 : Set shadow process core file dump type (Unix only)
  • ora-07758 : slemcw: invalid handle
  • ora-28655 : Alter table add overflow syntax error
  • ora-30358 : summary and materialized view are not in same schema
  • ora-12607 : TNS: Connect timeout occurred
  • ora-24433 : This statement has already been prepared using OCIStmtPrepare2.
  • ora-16186 : Modifying LOG_ARCHIVE_CONFIG requires SID='*' qualifier
  • ora-16249 : Terminal apply failed to complete during failover
  • ora-19924 : there are no row with id string
  • ora-39026 : master table is inconsistent on validation string
  • ora-19663 : cannot apply current offline range to datafile string
  • ora-25120 : MINIMUM EXTENT option already specified
  • ora-23403 : refresh group "string"."string" already exists
  • ora-06596 : unsupported LOB operation in RPC call
  • ora-12415 : A column of another datatype exists on the specified table
  • ora-18001 : no options specified for ALTER OUTLINE
  • ora-13756 : Cannot update attribute "string".
  • ora-02424 : potential circular view references or unknown referenced tables
  • ora-01207 : file is more recent than control file - old control file
  • ora-09313 : slsprom: error prompting user
  • ora-13914 : Threshold notification failed.
  • ora-00333 : redo log read error block string count string
  • ora-30485 : missing ORDER BY expression in the window specification
  • ora-00972 : identifier is too long
  • 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.