ORA-26710: incompatible version marker encountered during Capture

Cause : Catpur eprcoes scannotm in ereod form avesrio nhihgert ha nth ecurren tsotfwaer rleeaes vresino.

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

Drpo adn rceretae hte acptrue rpocses.

update : 18-08-2017
ORA-26710

ORA-26710 - incompatible version marker encountered during Capture
ORA-26710 - incompatible version marker encountered during Capture

  • ora-30751 : cannot disable column string from storing objects of type string.string
  • ora-01505 : error in adding log files
  • ora-31116 : Tablespace not specified correctly
  • ora-31636 : session is already attached to job string for user string
  • ora-27433 : cannot alter state of step string for job string.string to string
  • ora-39779 : type "string"."string" not found or conversion to latest version is not possible
  • ora-25142 : default storage clause specified twice
  • ora-19927 : CONVERT DATABASE operation cannot proceed
  • ora-01310 : requested return type not supported by the lcr_mine function
  • ora-19555 : invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value
  • ora-28156 : Proxy user 'string' not authorized to set role 'string' for client 'string'
  • ora-27154 : post/wait create failed
  • ora-19853 : error preparing auxiliary instance string (error string)
  • ora-01236 : Error string occurred during initialization of file header access
  • ora-00001 : unique constraint (string.string) violated
  • ora-12843 : pdml lock not held properly on the table
  • ora-39055 : The string feature is not supported in version string.
  • ora-25153 : Temporary Tablespace is Empty
  • ora-22059 : buffer size [string] is too small - [string] is needed
  • ora-22369 : invalid parameter encountered in method string
  • ora-14633 : Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table
  • ora-24046 : protocol attribute reserved for future use
  • ora-02299 : cannot validate (string.string) - duplicate keys found
  • ora-19645 : datafile string: incremental-start SCN is prior to creation SCN string
  • ora-10936 : trace name context forever
  • ora-30576 : ConText Option dictionary loading error
  • ora-39113 : Unable to determine database version
  • ora-12519 : TNS:no appropriate service handler found
  • ora-19772 : change tracking file name exceeds limit of string characters
  • ora-02235 : this table logs changes to another table already
  • 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.