ORA-23404: refresh group "string"."string" does not exist

Cause : A refresh group name was given that is not in sys.rgroup$.

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

Provide a refresh group name that is in sys.rgroup$ or dbs_rgroup.

update : 26-09-2017

ORA-23404 - refresh group "string"."string" does not exist
ORA-23404 - refresh group "string"."string" does not exist

  • ora-16025 : parameter string contains repeated or conflicting attributes
  • ora-39036 : invalid metadata filter name string
  • ora-25008 : no implicit conversion to LOB datatype in instead-of trigger
  • ora-12813 : value for PARALLEL or DEGREE must be greater than 0
  • ora-26695 : error on call to string: return code string
  • ora-00488 : RBAL process terminated with error
  • ora-23409 : could not find an unused refresh group number
  • ora-25110 : NOSORT may not be used with a bitmap index
  • ora-26055 : Invalid buffer specified for direct path unload
  • ora-12317 : logon to database (link name string) denied
  • ora-36679 : (XSDPART17) workspace object contains a leaf (workspace object) that is not part of the partition dimension workspace object.
  • ora-07443 : function string not found
  • ora-00102 : network protocol string cannot be used by dispatchers
  • ora-02140 : invalid tablespace name
  • ora-32304 : materialized views with user-defined types cannot use prebuilt table
  • ora-29868 : cannot issue DDL on a domain index marked as LOADING
  • ora-24313 : user already authenticated
  • ora-00092 : LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC
  • ora-14194 : only one subpartition may be rebuilt
  • ora-32591 : connect string too long
  • ora-13219 : failed to create spatial index table [string]
  • ora-19265 : XQ0045 - invalid or unknown prefix string in function declaration
  • ora-29925 : cannot execute string
  • ora-21608 : duration is invalid for this function
  • ora-33304 : (DBVALID02) Note: Record number was allocated but not used. This can result in wasted space.
  • ora-16079 : standby archival not enabled
  • ora-14113 : partitioned table cannot have column with LOB datatype
  • ora-39775 : direct path API commit not allowed due to previous fatal error
  • ora-02300 : invalid value for OIDGENERATORS
  • ora-25404 : lost instance
  • 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.