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 : 30-05-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-12157 : TNS:internal network communication error
  • ora-24431 : Statement does not exist in the cache
  • ora-25106 : only one of PARALLEL or NOPARALLEL clause may be specified
  • ora-09271 : szlon: error verifying user name
  • ora-29813 : non-supported object type with associate statement
  • ora-00038 : Cannot create session: server group belongs to another user
  • ora-24347 : Warning of a NULL column in an aggregate function
  • ora-13303 : failure to retrieve a geometry object from a table
  • ora-39042 : invalid transform name string
  • ora-19571 : %s recid string stamp string not found in control file
  • ora-32337 : cannot alter materialized view with pending changes refresh on commit
  • ora-32322 : PCT refresh of "string"."string" not allowed the sequence of DMLs/PMOPs
  • ora-36762 : (XSLANGDM02) You cannot modify the string property of %J because analytic workspace string is attached in MULTI mode.
  • ora-15078 : ASM diskgroup was forcibly dismounted
  • ora-40252 : no target values were found
  • ora-09775 : osnmrs: reset protocol error
  • ora-03250 : Cannot mark this segment corrupt
  • ora-23407 : object name string must be shaped like "schema"."object" or "object"
  • ora-34489 : (MXMAINT06) You cannot maintain workspace object because it is a SURROGATE.
  • ora-00116 : SERVICE_NAMES name is too long
  • ora-34841 : (OPCREATE02) The string option must be declared with the READONLY attribute.
  • ora-32817 : message system link string is not configured with a log queue for string
  • ora-19668 : cannot do full restore of datafile string
  • ora-09260 : sigpidu: error obtaining process id
  • ora-09270 : szalloc: error allocating memory for security
  • ora-23385 : replication parallel push string argument not valid
  • ora-31082 : invalid attribute "string" specified in declaration of "string"
  • ora-22337 : the type of accessed object has been evolved
  • ora-00334 : archived log: 'string'
  • ora-00031 : session marked for kill
  • 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.