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-05-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-23457 : invalid flavor ID string
  • ora-16727 : resource guard cannot close database
  • ora-01734 : illegal parameters - EXTENT MIN higher than EXTENT MAX
  • ora-40304 : invalid classname string in prior probability specification
  • ora-01149 : cannot shutdown - file string has online backup set
  • ora-03286 : ALLOCATE EXTENT not valid for HASH CLUSTERS
  • ora-22919 : dangling REF error or lock object failed for no wait request
  • ora-19664 : file type: string, file name: string
  • ora-02267 : column type incompatible with referenced column type
  • ora-29805 : missing COLUMN keyword
  • ora-31468 : cannot process DDL change record
  • ora-06268 : NETNTT: cannot read /etc/oratab
  • ora-02367 : file truncated error in string
  • ora-25219 : enqueue failed, sequence deviation not allowed for queue string.string
  • ora-15103 : conflicting or duplicate REPAIR options
  • ora-10579 : Can not modify control file during test recovery
  • ora-13019 : coordinates out of bounds
  • ora-12642 : No session key
  • ora-13762 : The string ranking measure is invalid.
  • ora-23476 : cannot import from string to string
  • ora-10691 : Set background process core file type (Unix only)
  • ora-02217 : duplicate storage option specification
  • ora-16413 : Unsupported database type for ONDEMAND archivelog destinations
  • ora-02248 : invalid option for ALTER SESSION
  • ora-09914 : Unable to open the ORACLE password file.
  • ora-09291 : sksachk: invalid device specified for archive destination
  • ora-13007 : an invalid HEX character was detected
  • ora-19012 : Cannot convert XML fragment to the required datatype
  • ora-29263 : HTTP protocol error
  • ora-39141 : dump file "string" is a duplicate of dump file "string"
  • 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.