ORA-38476: abstract type used for an Attribute set may not be modified.

Cause : Ana ttmeptw asm ad etoa ltre at yp e(ATD) htati s suedt o aminatina n tatrbiut ese tofa n xEprsesino ste.

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

Don otm odfiy hte DAT idretcly .Us eDBSM_EPXFI LAPsI isnteda.

update : 24-04-2017

ORA-38476 - abstract type used for an Attribute set may not be modified.
ORA-38476 - abstract type used for an Attribute set may not be modified.

  • ora-06301 : IPA: Cannot allocate driver context
  • ora-14137 : Table in partially dropped state, submit DROP TABLE PURGE
  • ora-36643 : (XSDUNION21) Concat dimension workspace object cannot be changed to NOT UNIQUE because it contains custom member values.
  • ora-16502 : the Data Guard broker operation succeeded with warnings
  • ora-31616 : unable to write to dump file "string"
  • ora-38759 : Database must be mounted by only one instance and not open.
  • ora-03239 : maxextents (string) reached in LOB segment string.string subpartition string
  • ora-14611 : Duplicate subpartition name string in template
  • ora-32331 : type "string"."string" is incompatible with the master site
  • ora-31503 : invalid date supplied for begin_date or end_date
  • ora-12322 : unable to mount database (link name string)
  • ora-01218 : logfile member is not from the same point-in-time
  • ora-30971 : illegal operation on the Path Table
  • ora-29305 : cannot point-in-time recover tablespace 'string'
  • ora-23414 : materialized view log for "string"."string" does not record rowid values
  • ora-09941 : Version of orapasswd or installer is older than file.
  • ora-28334 : column is already encrypted
  • ora-02044 : transaction manager login denied: transaction in progress
  • ora-24304 : datatype not allowed for this call
  • ora-36180 : (XSAGGR08) AGGREGATE cannot function because there is a permission clause associated with variable workspace object.
  • ora-00405 : compatibility type "string"
  • ora-12914 : Cannot migrate tablespace to dictionary managed type
  • ora-10943 : trace name context forever
  • ora-13260 : layer table string does not exist
  • ora-13521 : Unregister operation on local Database id (string) not allowed
  • ora-28671 : UPDATE BLOCK REFERENCES may not be used on a partitioned index as a whole
  • ora-27193 : sbtinfo2 did not return volume label
  • ora-33458 : (ESDREAD09) Discarding compiled code for workspace object because number is now type string, whereas it was type string when the code was compiled.
  • ora-02260 : table can have only one primary key
  • ora-30746 : error occured while trying to drop column "string" in table "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.