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 : 28-04-2017

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

  • ora-00312 : online log string thread string: 'string'
  • ora-30134 : reserved for future use
  • ora-10243 : simulated error for test string of K2GTAB latch cleanup
  • ora-01332 : internal Logminer Dictionary error
  • ora-29918 : cannot create domain indexes on temporary tables
  • ora-19619 : cannot call restoreValidate after files have been named
  • ora-33012 : (XSAGDNGL05) AGGMAP workspace object contains invalid syntax.
  • ora-23379 : connection qualifier "string" is too long
  • ora-01323 : Invalid state
  • ora-38473 : cannot drop a type used for Expression Filter attribute set
  • ora-38468 : column "string" is not identified as a column storing expressions.
  • ora-28291 : No Kerberos Principal Value found.
  • ora-12222 : TNS:no support is available for the protocol indicated
  • ora-28151 : more than one user name specified for command
  • ora-36275 : (XSCGMDLAGG13) string is not a valid workspace object.
  • ora-01103 : database name 'string' in control file is not 'string'
  • ora-33911 : (MAKEDCL29) You cannot define a string in analytic workspace string because it has not been upgraded to version string.
  • ora-24395 : cannot reinitialize non-existent pool
  • ora-00288 : to continue recovery type ALTER DATABASE RECOVER CONTINUE
  • ora-13602 : The specified parameter string is not valid for task or object string.
  • ora-19759 : block change tracking is not enabled
  • ora-01776 : cannot modify more than one base table through a join view
  • ora-07216 : slghst: gethostname error, unable to get name of current host.
  • ora-22996 : NEXT extent size is smaller than LOB chunksize
  • ora-29255 : Cursor contains both bind and define arrays which is not permissible
  • ora-38770 : FLASHBACK DATABASE failed during recovery.
  • ora-37020 : (XSMULTI01) Analytic workspace string is not in MULTI mode.
  • ora-09341 : scumnt: unable to mount database
  • ora-07251 : spcre: semget error, could not allocate any semaphores.
  • ora-09766 : osnmop: buffer allocation failure.
  • 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.