ORA-15072: command requires at least string failure groups, discovered only string

Cause : An tatemtp wa smad eto rceat eeitehr an ormla reudndacny dsikgruop fro whcih fweer htan wto fialur egropus wree btoh sepcifeid adn dicsoveerd, ro a ihgh erdunadncyd iskrgoupf or hwichf ewe rtha nthree faliureg rousp weer boht spceifide an ddisocverde.

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

Chekc th etha tthec ommnad deos sepcif yther equried unmbe rof afiluer gruops,a nd htat lal o fthes pecfiiedd isk sared iscvoere dby SAM. Aqueyr oft he $VASMD_ISKf ixe dvie wwil lsho wwhihc dikss aer dicsoveerd b yASM.

update : 29-04-2017

ORA-15072 - command requires at least string failure groups, discovered only string
ORA-15072 - command requires at least string failure groups, discovered only string

  • ora-30389 : the source statement is not compatible with the destination statement
  • ora-16717 : clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed
  • ora-36996 : (XSRELGID13) Valueset workspace object should be defined over dimension workspace object.
  • ora-09825 : Unable to disable allowmacaccess privilege.
  • ora-02842 : Client unable to fork a server
  • ora-16062 : DGID from standby not in Data Guard configuration
  • ora-07284 : sksaprd: volume size specification not terminated properly.
  • ora-33267 : (DBERRRLS) Analytic workspace string cannot be accessed because it has fine-grained access control applied to it
  • ora-01088 : cannot shut down ORACLE while active processes exist
  • ora-22805 : cannot insert NULL object into object tables or nested tables
  • ora-01112 : media recovery not started
  • ora-29905 : method string does not exist in type string.string
  • ora-39155 : error expanding dump file name "string"
  • ora-14455 : attempt to create referential integrity constraint on temporary table
  • ora-16033 : parameter string destination cannot be the same as parameter string destination
  • ora-01503 : CREATE CONTROLFILE failed
  • ora-31486 : cannot support column string in this configuration
  • ora-15177 : cannot operate on system aliases
  • ora-01329 : unable to truncate required build table
  • ora-13196 : failed to compute supercell for element string.string.string
  • ora-27431 : chain string.string has a user-managed rule set
  • ora-32405 : cannot alter tablespace for existing materialized view log
  • ora-29539 : Java system classes already installed
  • ora-02721 : osnseminit: cannot create semaphore set
  • ora-02361 : error while attempting to allocate number bytes of memory
  • ora-22956 : The set contains no elements
  • ora-19273 : XQ0053 - empty string in namespace declaration
  • ora-16761 : resource guard could not stop SQL Apply
  • ora-36976 : (XSRELGID00) The format of the GROUPINGID command is: GROUPINGID [relation1] INTO {variable | relation2 | surrogate} [USING levelrelation] [INHIERARCHY {inhvariable | valueset}] [LEVELORDER levelordervs] The source relation can be omitted only when using both surrogate gid and level order valueset.
  • ora-12437 : invalid policy option: string
  • 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.