ORA-36763: (XSAGGCNTMOVE01) Aggregation variable workspace object cannot have itself as an AGGCOUNT.

Cause : An attepmt was mdae to tunr a varibale intoi ts own GAGCOUNT.

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

Select adifferetn AGGCOUTN variabel.

update : 16-08-2017
ORA-36763

ORA-36763 - (XSAGGCNTMOVE01) Aggregation variable workspace object cannot have itself as an AGGCOUNT.
ORA-36763 - (XSAGGCNTMOVE01) Aggregation variable workspace object cannot have itself as an AGGCOUNT.

  • ora-02471 : SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly used in hash expression.
  • ora-26671 : maximum number of STREAMS processes exceeded
  • ora-19717 : for non-OMF search the pattern must be specified
  • ora-38425 : attribute set used for an index object may not be unassigned
  • ora-19281 : XQ0055 - It is a static error if a Prolog contains more than one inherit-namespaces declaration
  • ora-30185 : output too large to fit in the buffer
  • ora-36885 : (XSSRF04) Error rewriting OLAP DML expression. Column name too big
  • ora-15095 : reached maximum ASM file size (string GB)
  • ora-38405 : quotes not allowed in the attribute set name
  • ora-01333 : failed to establish Logminer Dictionary
  • ora-29315 : tablespace 'string' has been recreated
  • ora-01216 : thread string is expected to be disabled after CREATE CONTROLFILE
  • ora-38768 : resizing datafile string failed
  • ora-13608 : The task or object name string is invalid.
  • ora-24080 : unschedule_propagation pending for QUEUE string and DESTINATION string
  • ora-03204 : the segment type specification should indicate partitioning
  • ora-01493 : invalid SAMPLE size specified
  • ora-24801 : illegal parameter value in OCI lob function
  • ora-01568 : cannot set space quota on PUBLIC
  • ora-30742 : cannot grant SELECT privilege WITH HIERARCHY OPTION on this object
  • ora-09747 : pw_detachPorts: server call pws_detach failed.
  • ora-32827 : Messaging Gateway agent must be shut down
  • ora-24787 : remote cursors must be closed before a call completes
  • ora-40272 : apply rules prohibited for this model mode
  • ora-23393 : the user is already the propagator
  • ora-22801 : invalid object row variable
  • ora-30485 : missing ORDER BY expression in the window specification
  • ora-09340 : Specified ORACLE_SID is either invalid or too long
  • ora-01296 : character set mismatch between dictionary string and logfiles
  • ora-25285 : Invalid value string for array_mode
  • 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.