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

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-13755 : invalid "SQL Tuning Set" name
  • ora-00401 : the value for parameter string is not supported by this release
  • ora-29291 : file remove operation failed
  • ora-10926 : trace name context forever
  • ora-30372 : fine grain access policy conflicts with materialized view
  • ora-30729 : maximum number of columns exceeded
  • ora-22898 : existing scope clause on "string" points to a table other than the one mentioned in the referential constraint
  • ora-06120 : NETTCP: network driver not loaded
  • ora-27501 : IPC error creating a port
  • ora-01165 : MAXDATAFILES may not exceed string
  • ora-27378 : cannot stop jobs of type EXECUTABLE on this platform
  • ora-07750 : slemcr: fopen failure
  • ora-01950 : no privileges on tablespace 'string'
  • ora-33452 : (ESDREAD06) Discarding compiled code for workspace object because number is now dimensioned by workspace object. It was dimensioned by workspace object when the code was compiled.
  • ora-25264 : cant get signature for this queue
  • ora-16789 : missing standby redo logs
  • ora-02166 : ARCHIVELOG and NOARCHIVELOG specified
  • ora-01980 : error during OS ROLE initialization
  • ora-29517 : recursive resolution failed for a referenced class
  • ora-39019 : invalid operation type string
  • ora-10574 : Test recovery did not corrupt any data block
  • ora-25235 : fetched all messages in current transaction
  • ora-12016 : materialized view does not include all primary key columns
  • ora-23453 : requested operation is not supported on top flavor
  • ora-32011 : cannot restore SPFILE to location already being used by the instance
  • ora-01941 : SEQUENCE keyword expected
  • ora-13498 : %s
  • ora-37037 : (XSMLTDCL03) You cannot RENAME objects in analytic workspace string because it is attached in MULTI mode.
  • ora-23608 : invalid resolution column "string"
  • ora-27100 : shared memory realm already exists
  • 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.