ORA-25252: listen failed, the address string is a non-persistent queue

Cause : A non-persistent queue was specified as an address for an agent in the LISTEN call.

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

Specify a normal queue as address for the agent, and retry the the LISTEN call.

update : 19-08-2017
ORA-25252

ORA-25252 - listen failed, the address string is a non-persistent queue
ORA-25252 - listen failed, the address string is a non-persistent queue

  • ora-07251 : spcre: semget error, could not allocate any semaphores.
  • ora-16792 : configuration property value is inconsistent with database setting
  • ora-12336 : cannot login to database (link name string)
  • ora-12600 : TNS: string open failed
  • ora-30032 : the suspended (resumable) statement has timed out
  • ora-00287 : specified change number string not found in thread string
  • ora-37181 : expected exactly string columns for dimension string, got string
  • ora-30486 : invalid window aggregation group in the window specification
  • ora-16604 : unable to describe template using package "string"
  • ora-15196 : invalid ASM block header [string:string] [string] [string] [string] [string != string]
  • ora-26709 : Streams RFS restart
  • ora-29970 : Specified registration id does not exist
  • ora-19863 : device block size string is larger than max allowed: string
  • ora-23366 : integer value string is less than 1
  • ora-13223 : duplicate entry for string in SDO_GEOM_METADATA
  • ora-39018 : master process received invalid message number string
  • ora-36764 : (XSAGGCNTMOVE02) AGGCOUNT variable workspace object must be of type INTEGER, not string.
  • ora-39081 : failed to unsubscribe agent string from queue "string"
  • ora-01221 : data file string is not the same file to a background process
  • ora-22909 : exceeded maximum VARRAY limit
  • ora-19564 : error occurred writing string bytes at block number string
  • ora-31183 : Node type string cannot be converted to desired type
  • ora-16720 : no LOG_ARCHIVE_DEST_n initialization parameters available
  • ora-30345 : circular dimension hierarchy
  • ora-32319 : Cannot use direct loader log to FAST REFRESH materialized view "string"."string"
  • ora-28172 : distinguished name not provided by proxy
  • ora-21520 : database server driver not installed
  • ora-12028 : materialized view type is not supported by master site string
  • ora-32742 : Hang analysis initialize failed
  • ora-13040 : failed to subdivide tile
  • 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.