ORA-36161: (XSAGGRRUVCV) Aggregation variable workspace object cannot have itself as a COUNTVAR.

Cause : The user specified the same variable as both an aggregation variable and a COUNTVAR

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

Specify a different COUNTVAR

update : 28-06-2017
ORA-36161

ORA-36161 - (XSAGGRRUVCV) Aggregation variable workspace object cannot have itself as a COUNTVAR.
ORA-36161 - (XSAGGRRUVCV) Aggregation variable workspace object cannot have itself as a COUNTVAR.

  • ora-13053 : maximum number of geometric elements in argument list exceeded
  • ora-02315 : incorrect number of arguments for default constructor
  • ora-25408 : can not safely replay call
  • ora-36842 : (XSLMGEN12) Hierarchy string.string!string.string was not found
  • ora-27008 : function called with invalid file structure
  • ora-02293 : cannot validate (string.string) - check constraint violated
  • ora-09838 : removeCallback: failure removing the callback port.
  • ora-24402 : error occured while creating connections in the pool
  • ora-06320 : IPA: Remote maximum number of connections exceeded
  • ora-16040 : standby destination archive log file is locked
  • ora-13453 : GeoRaster metadata layer error
  • ora-39306 : schema name mismatch expected "string" got "string"
  • ora-14156 : invalid number of subpartitions specified in [SUBPARTITIONS | SUBPARTITION TEMPLATE] clause
  • ora-26015 : Array column string in table string is not supported by direct path
  • ora-12042 : cannot alter job_queue_processes in single process mode
  • ora-21525 : attribute number or (collection element at index) string violated its constraints
  • ora-19273 : XQ0053 - empty string in namespace declaration
  • ora-32165 : Cannot get XA environment
  • ora-40304 : invalid classname string in prior probability specification
  • ora-38724 : Invalid option to the FLASHBACK DATABASE command.
  • ora-12017 : cannot alter primary key mview 'string' to a rowid mview
  • ora-09856 : smpalo: vm_allocate error while allocating pga.
  • ora-12719 : operation requires database is in RESTRICTED mode
  • ora-13047 : unable to determine ordinate count from table _SDOLAYER
  • ora-23515 : materialized views and/or their indices exist in the tablespace
  • ora-22334 : cannot reset type "string"."string". Dependent tables must be upgraded to latest version
  • ora-36636 : (XSDUNION04) The unique concat dimension workspace object cannot be changed to NOT UNIQUE, because it is a base of at least one other unique concat dimension.
  • ora-37032 : (XSMLTMAINT03) You cannot MAINTAIN partition template workspace object in MULTI mode.
  • ora-24045 : invalid agent address string, agent address should be of the form [SCHEMA.]NAME[@DATABASE LINK]
  • ora-29307 : datafile string error, 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.