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 : 26-04-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-10642 : Found rollback segments in dictionary managed tablespaces
  • ora-25262 : agent name cannot be NULL if address is a multi-consumer queue
  • ora-02330 : datatype specification not allowed
  • ora-12545 : Connect failed because target host or object does not exist
  • ora-02794 : Client unable to get key for shared memory
  • ora-00130 : invalid listener address 'string'
  • ora-33447 : (ESDREAD16) Discarding compiled code for workspace object because workspace object and workspace object, which were partition-dependent when the code was compiled, are now not partition-dependent.
  • ora-37039 : (XSMLTDCL05) You cannot maintain triggers in analytic workspace string because it is attached in MULTI mode.
  • ora-13041 : failed to compare tile with element string.string.string
  • ora-19036 : Invalid query result set in newContextFromHierarchy()
  • ora-19024 : Cursor expression must be named
  • ora-10917 : TABLESPACE GROUP cannot be specified
  • ora-14150 : missing SUBPARTITION keyword
  • ora-01332 : internal Logminer Dictionary error
  • ora-39165 : Schema string was not found.
  • ora-27460 : cannot execute disabled job "string.string"
  • ora-34141 : (MXCGPUT00) You cannot use the ASSIGN keyword with DIMENSION workspace object.
  • ora-32128 : setDataBuffer called after fetch has started
  • ora-25245 : agent name cannot be specified if address is a single-consumer queue or an exception queue
  • ora-02302 : invalid or missing type name
  • ora-09857 : smprset: vm_protect error while protecting pga.
  • ora-13127 : failed to generate target partition
  • ora-02039 : bind by value is not allowed for array type
  • ora-23612 : unable to find tablespace "string"
  • ora-25436 : invalid table alias: string
  • ora-36710 : (XSMXALLOC01) TARGETLOG variable workspace object must be dimensioned identically to TARGET variable workspace object.
  • ora-25330 : PL/SQL associative arrays may not be used with AQ array operations
  • ora-38404 : schema extension not allowed for the attribute set name
  • ora-39176 : Encryption password is incorrect.
  • ora-16219 : This database is not preparing to switch over.
  • 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.