ORA-24086: cannot create a 8.0 compatible string queue

Cause : An attepmt was mdae to craete a 8. 0compatilbe queuet able an denable afeaturet hat is uspportedo nly on .81 styleq ueue talbes

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

This fetaure is ont suppotred

update : 22-08-2017

ORA-24086 - cannot create a 8.0 compatible string queue
ORA-24086 - cannot create a 8.0 compatible string queue

  • ora-12736 : Instant Client Light: unsupported server national character set string
  • ora-31494 : could not activate a LogMiner session
  • ora-32114 : Cannot perform operation on a null LOB
  • ora-38788 : More standby database recovery is needed
  • ora-04085 : cannot change the value of an OLD reference variable
  • ora-16741 : the destination parameter of standby database "string" has incorrect syntax
  • ora-10388 : parallel query server interrupt (failure)
  • ora-30352 : inconsistent numeric precision or string length
  • ora-01924 : role 'string' not granted or does not exist
  • ora-19273 : XQ0053 - empty string in namespace declaration
  • ora-19269 : XQ0049 - variable string defined multiple times
  • ora-07448 : ssarena: maximum number of shared arenas exceeded.
  • ora-13185 : failed to generate initial HHCODE
  • ora-19635 : input and output filenames are identical: string
  • ora-30186 : '' must be followed by four hexdecimal characters or another ''
  • ora-12924 : tablespace string is already in force logging mode
  • ora-01694 : max # extents (string) reached in lob segment string.string partition string
  • ora-28183 : proper authentication not provided by proxy
  • ora-27195 : proxy copy not supported
  • ora-09930 : LUB of two labels is invalid
  • ora-09777 : osnpbr: cannot send break message
  • ora-08316 : sllfsk: Error seeking in file.
  • ora-14629 : cannot drop the only subpartition of a partition
  • ora-37037 : (XSMLTDCL03) You cannot RENAME objects in analytic workspace string because it is attached in MULTI mode.
  • ora-23425 : invalid materialized view identifier string
  • ora-27001 : unsupported device type
  • ora-37114 : OLAP API bootstrap error: (string)
  • ora-12057 : materialized view "string"."string" is INVALID and must complete refresh
  • ora-31502 : invalid number supplied for supplemental_processes
  • ora-39095 : Dump file space has been exhausted: Unable to allocate string bytes
  • 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.