ORA-23451: flavor string already defined for object group "string"."string"

Cause : The given object group already contains a (possibly unpublished) definition of the specified flavor.

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

Check the spelling of the flavor name. Check for an unpublished flavor of the desired name.

update : 20-08-2017

ORA-23451 - flavor string already defined for object group "string"."string"
ORA-23451 - flavor string already defined for object group "string"."string"

  • ora-36181 : A VARIABLE cannot have both the $AGGREGATE_FROM and $AGGREGATE_FROMVAR properties applied to it.
  • ora-00972 : identifier is too long
  • ora-25213 : message with specified RELATIVE_MSGID has been dequeued
  • ora-25136 : this cluster can contain only one table
  • ora-32730 : Command cannot be executed on remote instance
  • ora-12094 : error during online redefinition
  • ora-13233 : failed to create sequence number [string] for R-tree
  • ora-04015 : ascending sequences that CYCLE must specify MAXVALUE
  • ora-02177 : Missing required group number
  • ora-19225 : XP0005 - XQuery static type error: expected non empty type got empty sequence
  • ora-02192 : PCTINCREASE not allowed for rollback segment storage clauses
  • ora-01640 : cannot make tablespace read only with active transactions
  • ora-10562 : Error occurred while applying redo to data block (file# string, block# string)
  • ora-29309 : export dump file was generated by different version of DBMS_PITR package
  • ora-31463 : logfile location string is an empty directory
  • ora-16710 : the resource guard is out of memory
  • ora-16017 : cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination
  • ora-40213 : contradictory values for settings: string, string
  • ora-12206 : TNS:received a TNS error during navigation
  • ora-26029 : index string.string partition string initially in unusable state
  • ora-13601 : The specified Advisor string does not exist.
  • ora-19209 : invalid or unsupported formatting argument
  • ora-25961 : join index prevents dml cascade constraint operation
  • ora-13386 : commit/rollback operation error: [string]
  • ora-22337 : the type of accessed object has been evolved
  • ora-29822 : selectivity cannot be specified for the type of object
  • ora-06431 : ssaio: Invalid Block number
  • ora-09779 : snyGetPort: failure to allocate a port.
  • ora-12665 : NLS string open failed
  • ora-40105 : input data incompatible with model signature
  • 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.