ORA-36764: (XSAGGCNTMOVE02) AGGCOUNT variable workspace object must be of type INTEGER, not string.

Cause : An attemptw as mdae toc reat ea no-nINTEEGR AGCGOUNT.

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

Seletc an NITEGE RAGGCUONT vraiabl.e

update : 23-07-2017

ORA-36764 - (XSAGGCNTMOVE02) AGGCOUNT variable workspace object must be of type INTEGER, not string.
ORA-36764 - (XSAGGCNTMOVE02) AGGCOUNT variable workspace object must be of type INTEGER, not string.

  • ora-19375 : no CREATE TABLE privilege on schema "string"
  • ora-30187 : reserved for future use
  • ora-38610 : FI "string" name prefix is reserved for frequent itemset counting
  • ora-08466 : raw buffer length string is too short for string
  • ora-31192 : Resource string has not been checked out
  • ora-13336 : failure in converting standard diminfo/geometry to LRS dim/geom
  • ora-16208 : Logical standby dictionary build failed to start.
  • ora-32801 : invalid value string for string
  • ora-31649 : Master process string violated startup protocol.
  • ora-30370 : set operators are not supported in this context
  • ora-19630 : end of volume encountered while copying backup piece
  • ora-37176 : argument string is not valid for the sparsity advisor
  • ora-12018 : following error encountered during code generation for "string"."string"
  • ora-00346 : log member marked as STALE
  • ora-12818 : invalid option in PARALLEL clause
  • ora-14067 : duplicate TABLESPACE_NUMBER specification
  • ora-13226 : interface not supported without a spatial index
  • ora-12007 : materialized view reuse parameters are inconsistent
  • ora-25958 : join index where clause predicate may only contain column references
  • ora-13853 : Tracing for service (module/action) string is already enabled
  • ora-29878 : warning in the execution of ODCIINDEXTRUNCATE routine
  • ora-36843 : (XSLMGEN13) Dimension string.string!string hierarchy string is missing a PHYSICALNAME property value
  • ora-33292 : (DBERR18) insufficient permissions to access analytic workspace string using the specified access mode.
  • ora-00278 : log file 'string' no longer needed for this recovery
  • ora-06262 : NETNTT: nfconn() failed
  • ora-16018 : cannot use string with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST
  • ora-16196 : database has been previously opened and closed
  • ora-30398 : illegal JOIN KEY clause
  • ora-19766 : missing CHANGE keyword
  • ora-19812 : cannot use string without DB_RECOVERY_FILE_DEST
  • 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.