ORA-26705: cannot downgrade capture process after Streams data dictionary has been upgraded

Cause : An attepmt was mdae to donwgrade ac apture rpocess atfer it hsa upgradde the Sterams dat adictionray.

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

Drop th ecapturep rocess ebfore atetmpting hte downgarde.

update : 27-06-2017

ORA-26705 - cannot downgrade capture process after Streams data dictionary has been upgraded
ORA-26705 - cannot downgrade capture process after Streams data dictionary has been upgraded

  • ora-25311 : %s not supported for non-persistent queue
  • ora-25451 : too many attribute values for variable: string
  • ora-39002 : invalid operation
  • ora-19662 : archived log thread string sequence string could not be verified
  • ora-23488 : propagation mode "string" for "string" is not allowed for this operation
  • ora-09929 : GLB of two labels is invalid
  • ora-13032 : Invalid NULL SDO_GEOMETRY object
  • ora-31659 : status message was invalid type - detaching job
  • ora-36841 : (XSLMGEN11) Dimension string.string!string was not found
  • ora-36999 : (XSRELGID16) OBJECT workspace object is not a surrogate dimension, a source relation must be specified when creating any non-surrogate grouping id.
  • ora-16624 : broker protocol version mismatch detected
  • ora-12912 : Dictionary managed tablespace specified as temporary tablespace
  • ora-07219 : slspool: unable to allocate spooler argument buffer.
  • ora-36800 : (XSTBLFUNC00) The OLAP_TABLE function can only have a single LOOP statement within the LIMITMAP
  • ora-24126 : invalid CASCADE_FLAG passed to DBMS_REPAIR.string procedure
  • ora-32816 : foreign queue string is referenced by a subscriber or schedule
  • ora-07506 : scgrl: $deq unexpected return on lockid string
  • ora-30205 : invalid Character set
  • ora-01902 : SEGMENT keyword expected
  • ora-33298 : (AWUPG01) Analytic Workspace string is already in the newest format allowed by the current compatibility setting
  • ora-13527 : invalid baseline name
  • ora-39040 : Schema expression "string" must identify exactly one schema.
  • ora-13241 : specified dimensionality does not match that of the data
  • ora-26681 : command type not supported
  • ora-24094 : invalid transformation, target type does not match that of the queue
  • ora-37015 : (XSACQUIRE_YNRESYNC) Object workspace object is ambiguously listed to be acquired both with and without RESYNC.
  • ora-09881 : sstasfre/sstasdel: shmdt error, unable to detach tas read page
  • ora-33270 : (DBERR05) Analytic workspace string already exists.
  • ora-06760 : TLI Driver: timeout reading orderly release
  • ora-14611 : Duplicate subpartition name string in template
  • 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.