ORA-25246: listen failed, the address string is an 8.0 style exception queue

Cause : An 8.0 style exception queue was specified in the agent-list for the LISTEN call.

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

Specify a normal 8.0 style queue or an 8.1 style queue in the agent-list.

update : 28-07-2017

ORA-25246 - listen failed, the address string is an 8.0 style exception queue
ORA-25246 - listen failed, the address string is an 8.0 style exception queue

  • ora-13290 : the specified unit is not supported
  • ora-22163 : left hand and right hand side collections are not of same type
  • ora-15071 : ASM disk "string" is already being dropped
  • ora-13219 : failed to create spatial index table [string]
  • ora-13870 : Database-wide SQL tracing is not enabled
  • ora-10572 : Test recovery canceled due to errors
  • ora-13151 : failed to remove exception record
  • ora-16011 : Archivelog Remote File Server process in Error state
  • ora-00325 : archived log for thread string, wrong thread # string in header
  • ora-16587 : ambiguous object specified to Data Guard broker
  • ora-15121 : ASM file name 'string' contains an invalid diskgroup name
  • ora-38736 : Wrong thread number string in flashback log file header.
  • ora-31631 : privileges are required
  • ora-06955 : Number of database servers exceed limit
  • ora-24430 : Null values for sqltext and key were specified.
  • ora-39504 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-12409 : policy startup failure for string policy
  • ora-04098 : trigger 'string.string' is invalid and failed re-validation
  • ora-03297 : file contains used data beyond requested RESIZE value
  • ora-02171 : invalid value for MAXLOGHISTORY
  • ora-28030 : Server encountered problems accessing LDAP directory service
  • ora-08176 : consistent read failure; rollback data not available
  • ora-24072 : cannot execute MIGRATE_QUEUE_TABLE procedure; must own queue table
  • ora-29251 : Index1 is greater than Index2 in call to dbms_sql.bind_array
  • ora-12814 : only one CACHE or NOCACHE clause may be specified
  • ora-31167 : XML nodes over 64K in size cannot be inserted
  • ora-02260 : table can have only one primary key
  • ora-19862 : backup pieces must be validated before accessing results
  • ora-25144 : invalid option for CREATE TABLESPACE with TEMPORARY contents
  • ora-21607 : memory cartridge service handle not initialized
  • 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.