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 : 20-08-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-32409 : materialized view log on "string"."string" already excludes new values
  • ora-22321 : method does not return any result
  • ora-02067 : transaction or savepoint rollback required
  • ora-27092 : size of file exceeds file size limit of the process
  • ora-00347 : log string of thread string, expected block size string doesn't match string
  • ora-33030 : (XSAGDNGL14) In AGGMAP workspace object, you can have either a single independent PROTECT statement or PROTECT statements in your RELATION statements.
  • ora-25151 : Rollback Segment cannot be created in this tablespace
  • ora-37184 : illegal value string for ADVMODE
  • ora-30971 : illegal operation on the Path Table
  • ora-12682 : Login failed: the SecurID card is in next PRN mode
  • ora-19643 : datafile string: incremental-start SCN is too recent
  • ora-28660 : Partitioned Index-Organized table may not be MOVEd as a whole
  • ora-27160 : process requested to perform operation
  • ora-02001 : user SYS is not permitted to create indexes with freelist groups
  • ora-32834 : Messaging Gateway agent user has not been set
  • ora-31448 : invalid value for change_source
  • ora-23304 : malformed deferred rpc at arg string of string in call string, in tid string
  • ora-26534 : collision: tranID number ignored and purged
  • ora-27484 : Argument names are not supported for jobs without a program.
  • ora-32302 : object materialized views must be object ID based
  • ora-12481 : effective label not within program unit clearance range
  • ora-00308 : cannot open archived log 'string'
  • ora-40284 : model does not exist
  • ora-01451 : column to be modified to NULL cannot be modified to NULL
  • ora-09833 : addCallback: bad message format.
  • ora-30152 : File does not exist
  • ora-22130 : buffer size [string] is less than the required size [string]
  • ora-13619 : The procedure argument string is greater than the maximum allowable length of string characters.
  • ora-28559 : FDS_CLASS_NAME is string, FDS_INST_NAME is string
  • ora-19103 : VALUE keyword keyword
  • 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.