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 : 24-04-2017

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-31414 : error(s) occurred during change table advance
  • ora-12901 : default temporary tablespace must be of TEMPORARY type
  • ora-25437 : duplicate table value for table alias: string
  • ora-37181 : expected exactly string columns for dimension string, got string
  • ora-21607 : memory cartridge service handle not initialized
  • ora-14076 : submitted alter index partition/subpartition operation is not valid for local partitioned index
  • ora-16619 : health check timed out
  • ora-27000 : skgfqsbi: failed to initialize storage subsystem (SBT) layer
  • ora-38720 : Missing log file number.
  • ora-13900 : missing or invalid parameter string
  • ora-12569 : TNS:packet checksum failure
  • ora-15201 : disk string contains a valid RDBMS file
  • ora-39951 : incomplete values specified for PL/SQL warning settings
  • ora-16217 : prepare to switchover has not completed
  • ora-36930 : Cannot start a recursive call to Oracle OLAP because a ROLLBACK past an UPDATE to an attached analytic workspace has been performed.
  • ora-37157 : MDX syntax error was found in MDX query string but error text was missing
  • ora-39112 : Dependent object type string skipped, base object type string creation failed
  • ora-02495 : cannot resize file string, tablespace string is read only
  • ora-06309 : IPA: No message queue available
  • ora-25251 : exceeded maximum number of recipients for message
  • ora-24063 : cannot downgrade QUEUE_TABLE that has queues with rule-based subscribers
  • ora-15081 : failed to submit an I/O operation to a disk
  • ora-31159 : XML DB is in an invalid state
  • ora-13154 : invalid precision specified
  • ora-00602 : internal programming exception
  • ora-38853 : cannot mark instance string (redo thread string) as disabled
  • ora-16649 : database will open after Data Guard broker has evaluated Fast-Start Failover status
  • ora-24194 : attempt to read data in a message as the wrong type
  • ora-09798 : Label comparison failed.
  • ora-26083 : unsupported direct path stream version 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.