ORA-25245: agent name cannot be specified if address is a single-consumer queue or an exception queue

Cause : The agent name for the agent in the LISTEN call was specified when the agent address was a single-consumer queue or an exception queue.

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

Do not specify the agent name.

update : 25-04-2017

ORA-25245 - agent name cannot be specified if address is a single-consumer queue or an exception queue
ORA-25245 - agent name cannot be specified if address is a single-consumer queue or an exception queue

  • ora-14162 : subpartition "string": sum of PCTUSED and PCTFREE may not exceed 100
  • ora-09758 : osnipn: could not check port in name server.
  • ora-16186 : Modifying LOG_ARCHIVE_CONFIG requires SID='*' qualifier
  • ora-39102 : Timeout before master process string finished initialization. Master error:
  • ora-22919 : dangling REF error or lock object failed for no wait request
  • ora-36164 : (XSMXAGGR07) When using the COUNTVAR clause, the number of variables to be aggregated (number) must match the number of COUNTVAR variables (number).
  • ora-25149 : Columns of UROWID type may not be indexed
  • ora-07216 : slghst: gethostname error, unable to get name of current host.
  • ora-12091 : cannot online redefine table "string"."string" with materialized views
  • ora-06932 : CMX: error in local name
  • ora-02187 : invalid quota specification
  • ora-28342 : integrity check fails on column key
  • ora-22914 : DROP of nested tables not supported
  • ora-14306 : List value 'string' specified twice in partitions 'string', 'string'
  • ora-06925 : CMX: disconnect during connect request
  • ora-01518 : CREATE DATABASE must specify more than one log file
  • ora-38476 : abstract type used for an Attribute set may not be modified.
  • ora-31398 : DBMS_LDAP: Shared servers are not supported.
  • ora-14604 : During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified
  • ora-25284 : Invalid value string for string
  • ora-16622 : two or more broker database objects resolve to one physical database
  • ora-02843 : Invalid value for kernel flag
  • ora-23531 : site owner already exists in the template.
  • ora-31117 : Table "string"."string" is not resource metadata enabled
  • ora-32342 : The EXPLAIN_MVIEW facility failed to explain the materialized view statement
  • ora-16024 : parameter string cannot be parsed
  • ora-22880 : invalid REF
  • ora-13502 : Cannot rename SYSAUX tablespace
  • ora-31477 : could not detach LogMiner session during cleanup
  • ora-01619 : thread string is mounted by another instance
  • 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.