ORA-36179: (XSNOAGM) No AGGMAP was specified for VARIABLE workspace object.

Cause : hT esureu es dht eGARGGETA Eocmmna diwhtuo tpscefiiygna nGAMGPAo nht eocmmna dilen ,iwhta v raailb ehwci hah don$ GAMGPAp oreptr.y

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

pScefi ynaA GGAM Pnot ehA GGERAGETc moamdnl ni,eo rda dht eA$GGAM Prpporeytt oht eavirbaeli nuqseitno.

update : 19-08-2017
ORA-36179

ORA-36179 - (XSNOAGM) No AGGMAP was specified for VARIABLE workspace object.
ORA-36179 - (XSNOAGM) No AGGMAP was specified for VARIABLE workspace object.

  • ora-38762 : thread string redo log with scn string could not be found
  • ora-24361 : basic bind call not invoked before invoking advanced bind call
  • ora-12589 : TNS:connection not bequeathable
  • ora-10585 : Test recovery can not apply redo that may modify control file
  • ora-30373 : object data types are not supported in this context
  • ora-24270 : a row already exists in the string table for these parameters
  • ora-24808 : streaming of lob data is not allowed when using lob buffering
  • ora-00076 : dump string not found
  • ora-19033 : schema specified in the XML document does not match the schema parameter
  • ora-02455 : The number of cluster key column must be 1
  • ora-39032 : function string is not supported in string jobs
  • ora-27053 : blocksize in file header not a multiple of logical block size
  • ora-39138 : Insufficient privileges to load data not in your schema
  • ora-00054 : resource busy and acquire with NOWAIT specified
  • ora-13771 : cannot obtain exclusive lock string on "SQL Tuning Set" "string" owned by user "string"
  • ora-25311 : %s not supported for non-persistent queue
  • ora-32005 : error while parsing size specification [string]
  • ora-26092 : only LONG or LOB types can be partial
  • ora-25143 : default storage clause is not compatible with allocation policy
  • ora-01492 : LIST option not valid
  • ora-19230 : XP0010 - unsupported axis string
  • ora-32508 : no such watchpoint id
  • ora-32303 : mviews with user-defined types cannot reference multiple master sites
  • ora-01043 : user side memory corruption [string], [string], [string], [string]
  • ora-01110 : data file string: 'string'
  • ora-21501 : program could not allocate memory
  • ora-02165 : invalid option for CREATE DATABASE
  • ora-31631 : privileges are required
  • ora-16099 : internal error ORA-00600 occurred at standby database
  • ora-38955 : Source platform string not cross platform compliant
  • 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.