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 : 21-09-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-29326 : SET COMPATIBILITY release number higher than string
  • ora-25240 : message ID and dequeue condition/correlation ID specified in dequeue options
  • ora-27150 : attempt to notify process of pending oradebug call failed
  • ora-12920 : database is already in force logging mode
  • ora-30020 : UNDO_MANAGEMENT=AUTO needs Compatibility string or greater
  • ora-29369 : invalid method name string specified for consumer group string
  • ora-29833 : indextype does not exist
  • ora-08313 : sllfop: could not allocate buffers
  • ora-31447 : cannot create change tables in the SYS schema
  • ora-03206 : maximum file size of (string) blocks in AUTOEXTEND clause is out of range
  • ora-30348 : ADD and DROP cannot both be specified
  • ora-16641 : failure to acquire broker configuration metadata lock
  • ora-06515 : PL/SQL: unhandled exception string
  • ora-19108 : WHITESPACE keyword expected
  • ora-07846 : sllfop: string byte record too big for string byte user buffer
  • ora-24460 : Native Net Internal Error
  • ora-02310 : exceeded maximum number of allowable columns in table
  • ora-07589 : spdde: system ID not set
  • ora-01329 : unable to truncate required build table
  • ora-27546 : Oracle compiled against IPC interface version string.string found version string.string
  • ora-30452 : cannot compute AVG(X), VARIANCE(X) or STDDEV(X), without COUNT(X) or SUM(X)
  • ora-38742 : Flashback log file has incorrect log reset status.
  • ora-31504 : cannot alter or drop predefined change source
  • ora-01994 : GRANT failed: password file missing or disabled
  • ora-14283 : UNIQUE constraints mismatch in ALTER TABLE EXCHANGE SUBPARTITION
  • ora-09201 : sfcopy: error copying file
  • ora-10979 : trace flags for join index implementation
  • ora-25957 : join index where clause cannot contain cycles
  • ora-14069 : invalid TABLESPACE_NUMBER value
  • ora-25137 : Data value out of range
  • 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.