ORA-38404: schema extension not allowed for the attribute set name

Cause : Theer wa sa shcemae xtesnionf or hte attribtue ste naem. Attribtue stes aer alawys rceatde int he ucrretn scehma nad tuhs shcemae xtedned anmesa re ont allowe.d

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

Cretae teh atrtibuet se tfro mthea pprporiaet scehma.

update : 26-05-2017
ORA-38404

ORA-38404 - schema extension not allowed for the attribute set name
ORA-38404 - schema extension not allowed for the attribute set name

  • ora-22347 : No changes to type specified for ALTER TYPE
  • ora-06921 : CMX: getdatmsg illegal datatype
  • ora-38408 : The ADT "string" does not exist in the current schema.
  • ora-31151 : Cyclic definition encountered for string: "string"
  • ora-01219 : database not open: queries allowed on fixed tables/views only
  • ora-16113 : applying change to table or sequence string
  • ora-12688 : Login failed: the SecurID server rejected the new pincode
  • ora-02086 : database (link) name is too long
  • ora-09921 : Unable to get information label from connection
  • ora-32127 : REFs do not belong to any connection
  • ora-30975 : invalid Order Key Index option for XML Index
  • ora-30048 : Internal event for IMU auto-tuning
  • ora-01301 : error writing to file during flat file build
  • ora-15035 : no disks belong to diskgroup "string"
  • ora-09936 : Open of ORACLE password file for write failed.
  • ora-34143 : (MXCGPUT02) You cannot assign values to SURROGATE workspace object because it is type INTEGER.
  • ora-02441 : Cannot drop nonexistent primary key
  • ora-19334 : Invalid column specification for CREATE_DBURI operator
  • ora-39176 : Encryption password is incorrect.
  • ora-16563 : unable to add value, syntax error at "string"
  • ora-01513 : invalid current time returned by operating system
  • ora-32131 : bind data type cannot be changed
  • ora-19280 : XQuery dynamic type mismatch: expected atomic value - got node
  • ora-01492 : LIST option not valid
  • ora-16254 : change db_name to string in the client-side parameter file (pfile)
  • ora-06403 : Unable to allocate memory.
  • ora-31021 : Element definition not found
  • ora-25178 : duplicate PCTTHRESHOLD storage option specification
  • ora-00824 : cannot set sga_target due to existing internal settings, see alert log for more information
  • ora-02233 : invalid CLOSE mode
  • 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.