ORA-31662: metadata transform name can not be defaulted

Cause : A null metadata transform name was supplied.

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

Fix the call to specify a metadata transform name.

update : 28-07-2017

ORA-31662 - metadata transform name can not be defaulted
ORA-31662 - metadata transform name can not be defaulted

  • ora-27469 : %s is not a valid string attribute
  • ora-37152 : MDX query error: (string)
  • ora-26667 : invalid STREAMS parameter string
  • ora-40283 : missing cost matrix
  • ora-01080 : error in shutting down ORACLE
  • ora-28655 : Alter table add overflow syntax error
  • ora-01168 : physical block size string does not match size string of other members
  • ora-13219 : failed to create spatial index table [string]
  • ora-08184 : attempting to re-enable Flashback while in Flashback mode
  • ora-37122 : AW Session cache disabled
  • ora-29933 : object being disassociated has some user defined statistics stored
  • ora-19648 : datafile string: incremental-start SCN equals checkpoint SCN
  • ora-30503 : system triggers cannot have a REFERENCING clause
  • ora-25247 : %s is not a recipient of specified message
  • ora-19040 : Element string does not match expected string.
  • ora-27158 : process control failure
  • ora-00824 : cannot set sga_target due to existing internal settings, see alert log for more information
  • ora-01515 : error dropping log group string: no such log
  • ora-19011 : Character string buffer too small
  • ora-13603 : The specified parameter string cannot be fetched as a numeric value for task or object string.
  • ora-01514 : error in log specification: no such log
  • ora-30430 : list does not contain any valid summaries
  • ora-26731 : %s 'string' does not exist
  • ora-22625 : OCIAnyData is not well-formed
  • ora-24342 : unable to destroy a mutex
  • ora-24317 : define handle used in a different position
  • ora-01513 : invalid current time returned by operating system
  • ora-14055 : keyword REBUILD in ALTER INDEX REBUILD must immediately follow
  • ora-32627 : illegal pattern in MODEL FOR LIKE loop
  • ora-00981 : cannot mix table and system auditing options
  • 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.