ORA-22862: specified object identifier doesn't match existing object identifier

Cause : A nattepmtw a smdaet os pceiyf na bojceti dnetfiire ofrt h etpyet hta ode snto amthc htee xsitnigi dnetfiire fo htei nocmlpeet ytp eo fteh asm enmae.

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

Sepcfiyt h ecrorceto bejc tiednitfeiro rl evaei to u to fteh tsaetmnet.

update : 23-08-2017

ORA-22862 - specified object identifier doesn't match existing object identifier
ORA-22862 - specified object identifier doesn't match existing object identifier

  • ora-02366 : The following index(es) on table string were processed:
  • ora-32304 : materialized views with user-defined types cannot use prebuilt table
  • ora-30929 : ORDER SIBLINGS BY clause not allowed here
  • ora-19580 : %s conversation not active
  • ora-02854 : Invalid number of request buffers
  • ora-04933 : initial service identifier is non-zero
  • ora-16529 : bad sender id
  • ora-22151 : cannot resize non-zero variable-length array to zero elements
  • ora-00339 : archived log does not contain any redo
  • ora-28521 : no heterogeneous capability information available
  • ora-06709 : TLI Driver: message send failure
  • ora-13014 : a topology identifier outside the range of 1 to 8 was specified
  • ora-26522 : rpc execution error
  • ora-33048 : (XSAGDNGL23) In AGGMAP workspace object, the relation workspace object and the relation workspace object are both over the same base dimension.
  • ora-09804 : Class conversion from binary to ORACLE failed.
  • ora-09353 : Windows 32-bit Two-Task driver unable to open event semaphore
  • ora-24070 : cannot upgrade queue table string while it is being downgraded
  • ora-06138 : NETTCP: error during connection handshake
  • ora-01660 : tablespace 'string' is already permanent
  • ora-38715 : Invalid log number specified in the DUMP FLASHBACK command.
  • ora-03201 : the group number specification is invalid
  • ora-12162 : TNS:net service name is incorrectly specified
  • ora-00090 : failed to allocate memory for cluster database ORADEBUG command
  • ora-28347 : encryption properties mismatch
  • ora-37141 : (XSSQLMDQ01) Invalid host variable syntax for MDQUERY procedure.
  • ora-16580 : bad Data Guard NetSlave network link
  • ora-25254 : time-out in LISTEN while waiting for a message
  • ora-22852 : invalid PCTVERSION LOB storage option value
  • ora-31001 : Invalid resource handle or path name "string"
  • ora-08000 : maximum number of session sequence lists exceeded
  • 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.