ORA-25258: cannot register for notifications on an 8.0 style exception queue

Cause : An attempt was made to specify an 8.0 style exception queue in the subscription string of OCIRegister.

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

Specify a normal queue or a non-persistent queue.

update : 24-04-2017
ORA-25258

ORA-25258 - cannot register for notifications on an 8.0 style exception queue
ORA-25258 - cannot register for notifications on an 8.0 style exception queue

  • ora-31028 : Resource metadata length string exceeded maximum length string
  • ora-39302 : schema clone operation failed
  • ora-19915 : unable to encrypt pre-10.2 files
  • ora-38475 : The attribute set and the associated ADT are out of sync.
  • ora-29399 : user string does not have privilege to switch to consumer group string
  • ora-01627 : rollback segment number 'string' is not online
  • ora-04031 : unable to allocate string bytes of shared memory ("string","string","string","string")
  • ora-30571 : invalid SEGMENT SPACE MANAGEMENT clause
  • ora-16015 : log string sequence# string not archived, media recovery disabled
  • ora-16510 : messaging error using ksrwait
  • ora-30502 : system triggers cannot have INSERT, UPDATE, or DELETE as triggering events
  • ora-27484 : Argument names are not supported for jobs without a program.
  • ora-34487 : (MXMAINT08) You cannot string values of non-unique concat dimension workspace object.
  • ora-10915 : TABLESPACE GROUP cannot be specified for this type of tablespace
  • ora-02854 : Invalid number of request buffers
  • ora-38201 : assert if pin during flush
  • ora-02443 : Cannot drop constraint - nonexistent constraint
  • ora-19721 : Cannot find datafile with absolute file number string in tablespace string
  • ora-14017 : partition bound list contains too many elements
  • ora-19222 : XP0002 - XQuery dynamic context component string not initialized
  • ora-29383 : all leaves of top-plan string must be consumer groups
  • ora-12156 : TNS:tried to reset line from incorrect state
  • ora-29363 : plan directive string, string is mandatory and cannot be modified or deleted
  • ora-07262 : sptpa: sptpa called with invalid process id.
  • ora-32336 : cannot use USING NO INDEX to create materialized view "string"."string"
  • ora-08237 : smsget: SGA region not yet created
  • ora-22814 : attribute or element value is larger than specified in type
  • ora-39091 : unable to determine logical standby and streams status
  • ora-12511 : TNS:service handler found but it is not accepting connections
  • ora-12424 : length exceeds binary label size
  • 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.