ORA-22860: object type expected

Cause : An tatemtp wa smad eto rceat ean bojec ttabel usnig an on-o bjetc tyep, o rto rceat ea cloumnt hati s aR EF ot a onn-ojbectt ype.

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

Usea vaild ojbectt ypei n teh talbe o rcolmun dfeiniiton.

update : 30-04-2017

ORA-22860 - object type expected
ORA-22860 - object type expected

  • ora-16739 : redo transport service for standby database "string" unexpectedly online
  • ora-24952 : register, unregister or post has incorrect collection count
  • ora-01302 : dictionary build options missing or incorrect
  • ora-29500 : NAMED keyword is invalid in CREATE JAVA CLASS
  • ora-06303 : IPA: Message send error
  • ora-13860 : Invalid service name
  • ora-13838 : invalid ADDRESS value
  • ora-07452 : specified resource manager plan does not exist in the data dictionary
  • ora-31446 : this session does not own the lock handle for string
  • ora-30957 : cannot downgrade because there are XML indexes
  • ora-39076 : cannot delete job string for user string
  • ora-22337 : the type of accessed object has been evolved
  • ora-12825 : explicit degree of parallelism must be specified here
  • ora-12469 : no user levels found for user string and policy string
  • ora-31023 : Index size error
  • ora-22621 : error transfering an object from the agent
  • ora-30691 : failed to allocate system resources while registering a TCP/IP connection for data traffic detection
  • ora-01664 : Transaction which has expanded the Sort Segment has aborted
  • ora-30042 : Cannot offline the undo tablespace
  • ora-16519 : the resource handle is invalid
  • ora-09743 : smscre: could not attach shared memory.
  • ora-03275 : duplicate DEALLOCATE option specification
  • ora-19300 : Error occurred in uri processingstring
  • ora-36812 : (XSTBLFUNC06) Invalid Syntax at '?'.
  • ora-16749 : resource guard encountered errors in switchover to logical primary database
  • ora-36410 : (VCACHE03) 'number' is an invalid value for the $VARCACHE property. The only permissible values are 'DEFAULT', 'SESSION', 'VARIABLE', and 'NONE'.
  • ora-36882 : (XSSRF01) The second parameter of an AW single row function cannot be NULL.
  • ora-03200 : the segment type specification is invalid
  • ora-16733 : error executing dbms_logstdby.unskip procedure
  • ora-16025 : parameter string contains repeated or conflicting attributes
  • 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.