ORA-24235: bad value for object type: string

Cause : The specified object type was not appropriate.

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

Make sure the specified object type is one of the following: package, package body, procedure, function, trigger, type, and type body.

update : 20-08-2017

ORA-24235 - bad value for object type: string
ORA-24235 - bad value for object type: string

  • ora-01272 : REUSE only allowed when a file name is provided.
  • ora-24165 : invalid rule engine object privilege: string
  • ora-30747 : cannot create substitutable tables or columns of non final type string.string
  • ora-12988 : cannot drop column from table owned by SYS
  • ora-37072 : (XSMCSESS00) Object workspace object has the wrong type.
  • ora-01614 : instance string (thread string) is busy - cannot enable
  • ora-36988 : (XSRELGID06) The related dimension of relation workspace object must be of type NUMBER.
  • ora-00113 : protocol name string is too long
  • ora-38765 : Flashed back database cannot be opened read-only.
  • ora-00720 : ALTER DATABASE RESET COMPATIBILITY command has been de-supported
  • ora-00305 : log string of thread string inconsistent; belongs to another database
  • ora-14633 : Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table
  • ora-26564 : %s argument is not of specified type
  • ora-30352 : inconsistent numeric precision or string length
  • ora-22296 : invalid ALTER TABLE option for conversion of LONG datatype to LOB
  • ora-09779 : snyGetPort: failure to allocate a port.
  • ora-22370 : incorrect usage of method string
  • ora-30939 : Order violation: Element 'string' may not follow element 'string'
  • ora-19568 : a device is already allocated to this session
  • ora-09751 : pw_attachPorts: server call pws_attach failed.
  • ora-07493 : scgrcl: lock manager error.
  • ora-36161 : (XSAGGRRUVCV) Aggregation variable workspace object cannot have itself as a COUNTVAR.
  • ora-08401 : invalid compiler name: string
  • ora-28553 : pass-through SQL: invalid bind-variable position
  • ora-07633 : smsdbp: illegal protection value
  • ora-12443 : policy not applied to some tables in schema
  • ora-13780 : SQL statement does not exist.
  • ora-16212 : number processes specified for APPLY is too great
  • ora-30451 : internal error
  • ora-09833 : addCallback: bad message format.
  • 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.