ORA-13142: invalid PROXIMITY window definition

Cause : The RPOXIMTIY widnow sepcifide is ont correctl ydefiend.

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

A PRXOIMIT Ywindwo is edfine dby sepcifynig a ecnterp ointa nd ar adiu.s Thec ente rpoin tis dfeinedb y NDv alue.s Theer sholud beN D+1 avlues.

update : 24-04-2017
ORA-13142

ORA-13142 - invalid PROXIMITY window definition
ORA-13142 - invalid PROXIMITY window definition

  • ora-01165 : MAXDATAFILES may not exceed string
  • ora-00443 : background process "string" did not start
  • ora-08000 : maximum number of session sequence lists exceeded
  • ora-34164 : (MXCGVAR01) A dimension used to define a local string variable cannot be located. Execution cannot continue.
  • ora-02001 : user SYS is not permitted to create indexes with freelist groups
  • ora-31222 : DBMS_LDAP: PL/SQL - Invalid LDAP SSL authentication mode.
  • ora-29848 : error occurred in the execution of ODCIINDEXMERGEPARTITION routine
  • ora-38904 : DML error logging is not supported for LOB column "string"
  • ora-38307 : object not in RECYCLE BIN
  • ora-16957 : SQL Analyze time limit interrupt
  • ora-14640 : add/coalesce index partition operation is valid only for hash partitioned global indexes
  • ora-28581 : protocol error while executing recursive external procedure
  • ora-01148 : cannot refresh file size for datafile string
  • ora-16768 : SQL Apply unexpectedly offline
  • ora-26746 : DDL rule "string"."string" not allowed for this operation
  • ora-28007 : the password cannot be reused
  • ora-36849 : (XSLMGEN19) AW owner does not match View token owner
  • ora-29913 : error in executing string callout
  • ora-01248 : file string was created in the future of incomplete recovery
  • ora-23504 : columns added to table do not match list of columns to be added
  • ora-38435 : missing elementary attribute value or invalid name-value pairs
  • ora-28163 : GRANT already specified
  • ora-33280 : (DBERR10) Analytic workspace string cannot be attached in MULTI mode until the changes made and updated in RW or EXCLUSIVE mode are committed or rolled back.
  • ora-19912 : cannot recover to target incarnation string
  • ora-26529 : local store callback term phase failed for 'string.string'
  • ora-02826 : Illegal block size
  • ora-16026 : parameter string contains an invalid attribute value
  • ora-00081 : address range [string, string) is not readable
  • ora-32032 : free temporary object number not available
  • ora-17621 : failed to register the memory with Oracle Disk Manager library
  • 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.