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 : 25-09-2017
ORA-31662

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

  • ora-32582 : table function with left correlation to a table cannot also be left outer-joined to the table
  • ora-39213 : Metadata processing is not available
  • ora-00334 : archived log: 'string'
  • ora-31443 : deadlock detected while acquiring lock on string
  • ora-40321 : invalid bin number, is zero or negative value
  • ora-12213 : TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA
  • ora-01544 : cannot drop system rollback segment
  • ora-24192 : the property name cannot be null
  • ora-12217 : TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA
  • ora-01973 : Missing change number
  • ora-26761 : Standby Redo Logs not available for real time mining
  • ora-37042 : (XSACQUIRE_DEP_DEADLOCK) Cannot wait to acquire composite, concat, dimension map, or internal partition workspace object since doing so would cause a deadlock.
  • ora-07447 : ssarena: usinit failed.
  • ora-29822 : selectivity cannot be specified for the type of object
  • ora-15156 : cluster in rolling upgrade from version [string] to [string]
  • ora-09767 : osnmfs: bad return code from msg_send.
  • ora-12830 : Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE
  • ora-16728 : consistency check for property string found string error
  • ora-36881 : (XSSRF00) The OLAP DML ROW2CELL function can only be used in a LIMITMAP.
  • ora-38742 : Flashback log file has incorrect log reset status.
  • ora-02300 : invalid value for OIDGENERATORS
  • ora-10628 : Turn on sanity check for kdiss index skip scan state
  • ora-30071 : conversion between datetime/interval and string fail
  • ora-33030 : (XSAGDNGL14) In AGGMAP workspace object, you can have either a single independent PROTECT statement or PROTECT statements in your RELATION statements.
  • ora-08193 : Flashback Table operation is not allowed on temporary tables
  • ora-14132 : table cannot be used in EXCHANGE
  • ora-01198 : must specify size for log file if RESETLOGS
  • ora-14074 : partition bound must collate higher than that of the last partition
  • ora-26507 : null master connection
  • ora-01928 : GRANT option not granted for all privileges
  • 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.