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 : 27-04-2017

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

  • ora-16230 : committing transaction string string string
  • ora-36278 : (XSCGMDLAGG07) workspace object does not exist or is not valueset.
  • ora-25446 : duplicate column value for table alias: string, column: string
  • ora-01044 : size string of buffer bound to variable exceeds maximum string
  • ora-28539 : gateway does not support result sets
  • ora-21603 : property id [string] is invalid
  • ora-01519 : error while processing file 'string' near line string
  • ora-13482 : GeoRaster object is not initialized for the image
  • ora-24437 : OCIStmtExecute called before OCIStmtPrepare2.
  • ora-06575 : Package or function string is in an invalid state
  • ora-24171 : creation properties are only for internal use
  • ora-12010 : cannot create materialized view log on table owned by SYS
  • ora-16079 : standby archival not enabled
  • ora-01640 : cannot make tablespace read only with active transactions
  • ora-32311 : materialized view definition query selects an unsupported user-defined type
  • ora-13905 : Critical or warning threshold have incorrect values
  • ora-06605 : LU6.2 Driver: Unexpected line turnaround
  • ora-39059 : dump file set is incomplete
  • ora-01941 : SEQUENCE keyword expected
  • ora-23483 : object "string"."string" not allowed in this operation.
  • ora-03292 : Table to be truncated is part of a cluster
  • ora-01084 : invalid argument in OCI call
  • ora-02794 : Client unable to get key for shared memory
  • ora-01041 : internal error. hostdef extension doesn't exist
  • ora-30017 : segment 'string' is not supported in string Undo Management mode
  • ora-00953 : missing or invalid index name
  • ora-24807 : LOB form mismatch
  • ora-07275 : unable to send signal to process
  • ora-14262 : new subpartition name must differ from the old subpartition name
  • ora-02310 : exceeded maximum number of allowable columns in 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.