ORA-25215: user_data type and queue type do not match

Cause : A user tries to enqueue an object to a queue that was created for objects of different type.

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

Try enqueue again with an object of the right type.

update : 27-06-2017
ORA-25215

ORA-25215 - user_data type and queue type do not match
ORA-25215 - user_data type and queue type do not match

  • ora-19616 : output filename must be specified if database not mounted
  • ora-01061 : cannot start up a V8 server using a V7 client application
  • ora-13612 : The recommendation action string,string is not valid for task string.
  • ora-15010 : name is already used by an existing ASM disk
  • ora-13462 : invalid blocking specification
  • ora-00218 : block size string of control file 'string' does not match DB_BLOCK_SIZE (string)
  • ora-24373 : invalid length specified for statement
  • ora-16227 : DDL skipped due to missing object
  • ora-03222 : average row size and row count must be greater than zero
  • ora-02275 : such a referential constraint already exists in the table
  • ora-09750 : pw_attachPorts: port_rename failed.
  • ora-32805 : identifier for string too long, maximum length is string characters
  • ora-25183 : index-organized table top index segment is in a different tablespace
  • ora-01290 : cannot remove unlisted logfile string
  • ora-06707 : TLI Driver: connection failed
  • ora-00471 : DBWR process terminated with error
  • ora-16574 : switchover disallowed when required databases are offline
  • ora-30771 : Cannot add more than one referential constraint on REF column "string"
  • ora-00299 : must use file-level media recovery on data file string
  • ora-00484 : LMS* process terminated with error
  • ora-09844 : soacon: Archmon unable to open named pipe.
  • ora-38783 : Instance recovery required.
  • ora-01999 : password file cannot be updated in SHARED mode
  • ora-37143 : (XSSQLMDQ03) string is not a valid analytic workspace name.
  • ora-31198 : Mismatch in number of bytes transferred due to non-binary mode
  • ora-24815 : Invalid character set form
  • ora-13206 : internal error [string] while creating the spatial index
  • ora-13466 : format not appropriate for specified compression method
  • ora-19805 : recid string of string was deleted to reclaim disk space
  • ora-27373 : unknown or illegal event source queue
  • 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.