ORA-26691: operation not supported at non-Oracle system

Cause : The appyl proces sattemptde an opeartion thta is eitehr not spuported yb the no-nOracle ysstem orb y the Oarcle trasnparent agteway trhough whcih the apply is bieng done .Some kidns of DM L(like porcedure nad functoin calls )and allD DL willc ause thsi error ot be raiesd.

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

Do not tatempt t oapply scuh LCRs ot non-Orcale systmes. If psosible, iflter ou tsuch LCsR beforea pplying.

update : 26-07-2017

ORA-26691 - operation not supported at non-Oracle system
ORA-26691 - operation not supported at non-Oracle system

  • ora-01337 : log file has a different compatibility version
  • ora-02371 : Loader must be at least version string.string.string.string.string for direct path
  • ora-26020 : index string.string loaded successfully with string keys
  • ora-33332 : (DSSEXIST01) Use the AW command to establish a current analytic workspace. Then start your current activity again.
  • ora-29263 : HTTP protocol error
  • ora-28611 : bitmap index is corrupted - see trace file for diagnostics
  • ora-16536 : unknown object type
  • ora-03286 : ALLOCATE EXTENT not valid for HASH CLUSTERS
  • ora-14155 : missing PARTITION or SUBPARTITION keyword
  • ora-19802 : cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE
  • ora-28591 : agent control utility: unable to access parameter file
  • ora-13856 : Service name must be specified
  • ora-00091 : LARGE_POOL_SIZE must be at least string
  • ora-23337 : priority or value not in priority group string
  • ora-00404 : Convert file not found: 'string'
  • ora-36765 : (XSAGGCNTMOVE03) A string aggregation variable cannot have a string AGGCOUNT.
  • ora-23480 : Column string is not a top-level column of "string"."string".
  • ora-32633 : MODEL subquery FOR cell index returns too many rows
  • ora-39060 : table(s) dropped because of conflict with master table
  • ora-23489 : duplicate entry "string"
  • ora-32762 : Turn on Temp LOB Ref Count Tracing
  • ora-01941 : SEQUENCE keyword expected
  • ora-30679 : JDWP-based debugging not supported in this configuration
  • ora-27149 : assignment out of range
  • ora-01968 : Only specify RESETLOGS or NORESETLOGS once
  • ora-03132 : two-task default value overflow
  • ora-30971 : illegal operation on the Path Table
  • ora-13851 : Tracing for client identifier string is already enabled
  • ora-12701 : CREATE DATABASE character set is not known
  • ora-02080 : database link is in use
  • 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.