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 : 28-04-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-25101 : duplicate REBUILD option specification
  • ora-08187 : snapshot expression not allowed here
  • ora-00702 : bootstrap verison 'string' inconsistent with version 'string'
  • ora-07627 : smsfre: $CRETVA failure
  • ora-30105 : 'string' is not a legal boolean for 'string'
  • ora-33217 : (CINSERT20) Custom member values cannot be added to concat dimension workspace object, or to any of its bases, because it is not defined as UNIQUE.
  • ora-16566 : unsupported document type
  • ora-04032 : pga_aggregate_target must be set before switching to auto mode
  • ora-22293 : LOB already opened in the same transaction
  • ora-38309 : object not purgable
  • ora-28012 : Manual commit not allowed here
  • ora-01903 : EVENTS keyword expected
  • ora-01930 : auditing the object is not supported
  • ora-02453 : duplicate HASH IS specification
  • ora-16654 : Fast-Start Failover is enabled
  • ora-31086 : insufficient privileges to register schema "string"
  • ora-38413 : elementary attribute name may not be longer than 32 characters
  • ora-25199 : partitioning key of a index-organized table must be a subset of the primary key
  • ora-10659 : Segment being shrunk is not a lob
  • ora-14277 : tables in EXCHANGE SUBPARTITION must have the same number of columns
  • ora-08195 : Flashback Table operation is not supported on partitions
  • ora-04070 : invalid trigger name
  • ora-30109 : could not open parameter file 'string'
  • ora-31692 : The following SQL statement failed trying to insert a row into the Master table: string
  • ora-12100 : materialized view log on "string"."string" already has sequence
  • ora-13029 : Invalid SRID in the SDO_GEOMETRY object
  • ora-01373 : insufficient memory for staging persistent LogMiner session
  • ora-36887 : (XSSRF06) Error rewriting OLAP DML expression. Column name string is not a valid ADT column.
  • ora-00481 : LMON process terminated with error
  • ora-24814 : operation not allowed for temporary LOBs
  • 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.