ORA-24315: illegal attribute type

Cause : An illegal attribute type was specified for the handle.

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

Consult user manual to specify an attribute valid for this handle.

update : 17-08-2017

ORA-24315 - illegal attribute type
ORA-24315 - illegal attribute type

  • ora-09318 : slkhst: unable to host out to operating system
  • ora-25456 : rule set was modified or evaluation terminated for iterator: string
  • ora-16091 : dependent archive log destination already archived
  • ora-31608 : specified object of type string not found
  • ora-01947 : TEMPORARY TABLESPACE already specified
  • ora-30112 : multiple values not allowed for parameter 'string'
  • ora-31623 : a job is not attached to this session via the specified handle
  • ora-32696 : HTI: No free slot
  • ora-30077 : illegal casting between specified datetime types
  • ora-30929 : ORDER SIBLINGS BY clause not allowed here
  • ora-30383 : specified dimension level does not exist in the attribute
  • ora-24166 : evaluation context string.string has errors
  • ora-37028 : (XSMLTRESYNC03) Object workspace object cannot be resynced without modified object workspace object because they share a modified dimension map.
  • ora-36669 : (XSDPART07) string is not a legal LIST partition.
  • ora-02465 : Inappropriate use of the HASH IS option
  • ora-39306 : schema name mismatch expected "string" got "string"
  • ora-16184 : DB_UNIQUE_NAME string hashes to the same value as DB_UNIQUE_NAME string
  • ora-07445 : exception encountered: core dump [string] [string] [string] [string] [string] [string]
  • ora-03248 : Too much of segment creation activity during migration
  • ora-13601 : The specified Advisor string does not exist.
  • ora-31525 : could not find column string in CDC change table string.string
  • ora-40254 : priors cannot be specified for one-class models
  • ora-12519 : TNS:no appropriate service handler found
  • ora-13860 : Invalid service name
  • ora-09808 : Could not obtain user clearance.
  • ora-13013 : the specified topology was not INTERIOR or BOUNDARY
  • ora-12454 : label string does not exist for policy string
  • ora-30129 : invalid function argument received
  • ora-12033 : cannot use filter columns from materialized view log on "string"."string"
  • ora-24850 : failed to startup shared subsystem
  • 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.