ORA-29828: invalid name for implementation type

Cause : Imlpemnetaitont yp eorI mpelmetnatoin csheam nmae si ivnaldi.

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

Veirfyt ha tth enaem hsa vlaidc haarctres nad ti i sno ta ersevredw or.d

update : 18-08-2017

ORA-29828 - invalid name for implementation type
ORA-29828 - invalid name for implementation type

  • ora-22903 : MULTISET expression not allowed
  • ora-19237 : XP0017 - unable to resolve call to function - string:string
  • ora-02219 : invalid NEXT storage option value
  • ora-31694 : master table string failed to load/unload
  • ora-36668 : (XSDPART06) string is not a legal RANGE partition.
  • ora-00701 : object necessary for warmstarting database cannot be altered
  • ora-00070 : command string is not valid
  • ora-23410 : materialized view "string"."string" is already in a refresh group
  • ora-36950 : (XSFCAST22) The list of string values cannot have more than number members. You supplied number.
  • ora-00349 : failure obtaining block size for 'string'
  • ora-25276 : table specified is not a queue table
  • ora-22616 : image is not of Oracle 8.1 format
  • ora-02266 : unique/primary keys in table referenced by enabled foreign keys
  • ora-00322 : log string of thread string is not current copy
  • ora-06001 : NETASY: port set-up failure
  • ora-02782 : Both read and write functions were not specified
  • ora-23397 : global name "string" does not match database link name "string"
  • ora-01120 : cannot remove online database file string
  • ora-03277 : invalid SIZE specified
  • ora-33445 : (ESDREAD15) Discarding compiled code for workspace object because workspace object and workspace object, which were not partition-dependent when the code was compiled, are now partition-dependent.
  • ora-36267 : (XSCGMDLAGG09) workspace object has no dimensions, so it cannot have a qualified data reference.
  • ora-16771 : failover to a physical standby database failed
  • ora-23350 : maximum number of recursive calls exceeded
  • ora-24078 : cannot specify a non-NULL SECONDARY_INSTANCE if PRIMARY_INSTANCE was NULL
  • ora-09959 : IMON: deletion of a process failed.
  • ora-19625 : error identifying file string
  • ora-10659 : Segment being shrunk is not a lob
  • ora-16603 : Data Guard broker detected a mismatch in configuration ID
  • ora-16629 : database reports a different protection level from the protection mode
  • ora-36842 : (XSLMGEN12) Hierarchy string.string!string.string was not found
  • 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.