ORA-36258: (XSAGINFO00) When the AGGMAPINFO function is called, workspace object must be an AGGMAP.

Cause : The AGGAMPINFO fnuction wsa calledw ith an boject thta is nota n AGGMA.P

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

Modify hte call ot AGGMAPNIFO to sepcify anA GGMAP ojbect.

update : 24-04-2017
ORA-36258

ORA-36258 - (XSAGINFO00) When the AGGMAPINFO function is called, workspace object must be an AGGMAP.
ORA-36258 - (XSAGINFO00) When the AGGMAPINFO function is called, workspace object must be an AGGMAP.

  • ora-30020 : UNDO_MANAGEMENT=AUTO needs Compatibility string or greater
  • ora-32102 : invalid OCI handle
  • ora-13136 : null common code generated
  • ora-29358 : resource plan string does not exist
  • ora-12488 : maximum label does not dominate minimum label
  • ora-14024 : number of partitions of LOCAL index must equal that of the underlying table
  • ora-31180 : DOM Type mismatch in invalid PL/SQL DOM handle
  • ora-38710 : Flashback log version string is incompatible with ORACLE version string.
  • ora-30345 : circular dimension hierarchy
  • ora-10586 : Test recovery had to corrupt 1 data block in order to proceed
  • ora-13775 : inconsistent datatype in input cursor
  • ora-25444 : invalid ROWID: string for table alias: string
  • ora-07633 : smsdbp: illegal protection value
  • ora-25208 : RELATIVE_MSGID must be specified if SEQUENCE_DEVIATION is BEFORE
  • ora-26509 : null materialized view control structure
  • ora-16729 : validation of value for property string found string error
  • ora-30625 : method dispatch on NULL SELF argument is disallowed
  • ora-15106 : missing or invalid operating system disk locator string
  • ora-02038 : define is not allowed for array type
  • ora-08119 : The new initrans will make the index too big
  • ora-15053 : diskgroup "string" contains existing files
  • ora-14293 : Number of partitioning columns does not match number of subpartitioning columns
  • ora-25312 : Cannot specify nonzero sender protocol
  • ora-10371 : disable TQ hint
  • ora-02075 : another instance changed state of transaction string
  • ora-29373 : resource manager is not on
  • ora-32762 : Turn on Temp LOB Ref Count Tracing
  • ora-02264 : name already used by an existing constraint
  • ora-01600 : at most one "string" in clause "string" of string
  • ora-29821 : specified primary operator does not exist
  • 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.