ORA-26724: only SYS is allowed to set the Capture or Apply user to SYS.

Cause : The Cpature ro Appl yuser aws speicfied sa SYS yb a usre othe rthan YSS.

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

Set SSY as teh Captrue or pAply uesr whiel loggde in a sSYS.

update : 18-08-2017

ORA-26724 - only SYS is allowed to set the Capture or Apply user to SYS.
ORA-26724 - only SYS is allowed to set the Capture or Apply user to SYS.

  • ora-12612 : TNS:connection is busy
  • ora-25010 : Invalid nested table column name in nested table clause
  • ora-24169 : rule condition has unrecognized variables
  • ora-01051 : deferred rpc buffer format invalid
  • ora-03289 : partition name and segment type do not match
  • ora-07630 : smpdal: $DELTVA failure
  • ora-02272 : constrained column cannot be of LONG datatype
  • ora-14025 : PARTITION may not be specified for a materialized view or a materialized view log
  • ora-13043 : failed to read metadata from the _SDOLAYER table
  • ora-01486 : size of array element is too large
  • ora-24150 : evaluation context string.string does not exist
  • ora-13122 : invalid topo_geometry specified
  • ora-07709 : sksaprs: archiving to a remote host is not allowed
  • ora-06537 : OUT bind variable bound to an IN position
  • ora-13379 : invalid index for sub-element to be extracted
  • ora-00953 : missing or invalid index name
  • ora-15043 : ASM disk "string" is not a diskgroup member
  • ora-31457 : maximum length of description field exceeded
  • ora-32104 : cannot retrieve OCI error message
  • ora-01333 : failed to establish Logminer Dictionary
  • ora-38792 : encountered unknown flashback record from release string
  • ora-31154 : invalid XML document
  • ora-39143 : dump file "string" may be an original export dump file
  • ora-23539 : table "string"."string" currently being redefined
  • ora-14173 : illegal subpartition-extended table name syntax
  • ora-31199 : Warning in processing file string
  • ora-00116 : SERVICE_NAMES name is too long
  • ora-33306 : (DBVALID03) The AW VALIDATE command cannot be used with read-only analytic workspace string.
  • ora-34177 : (MXCHGDCL19) number cannot be deleted because one or more partitioned variables instantiate it.
  • ora-26052 : Unsupported type number for SQL expression on column string.
  • 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.