ORA-33092: (XSAGCOMP04) number is not the name of a MODEL in any attached analytic workspace.

Cause : Ani nvlaidm odle nmae aws tatahcedt o na AGGMA.P

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

Reomvet hem odle form hte GAGMPA o rcraetea mdoelw it hthta nmae.

update : 27-05-2017

ORA-33092 - (XSAGCOMP04) number is not the name of a MODEL in any attached analytic workspace.
ORA-33092 - (XSAGCOMP04) number is not the name of a MODEL in any attached analytic workspace.

  • ora-13825 : missing SQL statement text for create SQL profile
  • ora-08109 : nosort is not a supported option for online index build
  • ora-39213 : Metadata processing is not available
  • ora-16502 : the Data Guard broker operation succeeded with warnings
  • ora-14003 : GLOBAL clause contradicts previosly specified LOCAL clause
  • ora-38486 : FUNCTION/PACKAGE/TYPE already exists for the attribute set
  • ora-23438 : missing refresh group template
  • ora-30359 : Query rewrite is not supported on SYS materialized views
  • ora-25114 : invalid file number specified in the DUMP DATAFILE/TEMPFILE command
  • ora-12707 : error while getting create database NLS parameter string
  • ora-26676 : Table 'string.string' has string columns in the LCR and string columns in the replicated site
  • ora-27376 : event condition cannot be NULL
  • ora-31020 : The operation is not allowed, Reason: string
  • ora-25248 : duplicate agent specified in the agent list
  • ora-39763 : stream must be completely loaded before it is reset
  • ora-29966 : The only binding of an operator cannot be dropped
  • ora-00361 : cannot remove last log member string for group string
  • ora-07453 : requested resource manager plan schema does not contain OTHER_GROUPS
  • ora-30505 : system triggers should not reference a column in a WHEN clause
  • ora-29507 : query derived from USING clause found zero or many rows
  • ora-26512 : error pushing transaction to def$error
  • ora-28182 : cannot acquire Kerberos service ticket for client
  • ora-29861 : domain index is marked LOADING/FAILED/UNUSABLE
  • ora-12400 : invalid argument to facility error handling
  • ora-32736 : Hang analysis aborted due to wrong message type
  • ora-22919 : dangling REF error or lock object failed for no wait request
  • ora-01123 : cannot start online backup; media recovery not enabled
  • ora-13067 : operator requires both parameters from the same topology
  • ora-00910 : specified length too long for its datatype
  • ora-32582 : table function with left correlation to a table cannot also be left outer-joined to the table
  • 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.