ORA-25248: duplicate agent specified in the agent list

Cause : An agent was specified more than once in the agent list of the LISTEN call.

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

Remove the duplicate agent specification(s), and retry the call.

update : 25-04-2017

ORA-25248 - duplicate agent specified in the agent list
ORA-25248 - duplicate agent specified in the agent list

  • ora-09216 : sdnfy: bad value 'string' for parameter string
  • ora-30150 : Invalid argument passed to OCIFile function
  • ora-34145 : (MXCGPUT03) You cannot use the APPEND keyword with SURROGATE workspace object.
  • ora-32550 : Replacement occured despite hint to the contrary
  • ora-29325 : SET COMPATIBILITY release number lower than string
  • ora-32812 : subscriber string does not exist
  • ora-29842 : option not supported with the version string of the indextype interface
  • ora-31500 : change source string is not a ManualLog change source
  • ora-23423 : job number string is not positive
  • ora-12044 : invalid CREATE MATERIALIZED VIEW LOG option
  • ora-09786 : sllfop: open error, unable to open file.
  • ora-07339 : spcre: maximum number of semaphore sets exceeded.
  • ora-38620 : DT expressions in input cursor do not have an alias name
  • ora-38774 : cannot disable media recovery - flashback database is enabled
  • ora-30749 : column string not enabled to store objects of type string.string
  • ora-06603 : LU6.2 Driver: Error allocating memory
  • ora-38434 : could not evaluate expression "string"
  • ora-31160 : max substitution group size string exceeded by "string" (string) for head element "string" (string)
  • ora-13138 : could not determine name of object string
  • ora-33086 : (XSAGINIT01) AGGMAP workspace object cannot be dimensioned by a conjoint dimension.
  • ora-19266 : XQ0046 - invalid URI
  • ora-23435 : cannot create an updatable ROWID materialized view with LOB columns
  • ora-00319 : log string of thread string has incorrect log reset status
  • ora-19211 : column 'string', specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type
  • ora-02179 : valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED }
  • ora-31627 : API call succeeded but more information is available
  • ora-06310 : IPA: Environment variable(s) not set
  • ora-04083 : invalid trigger variable 'string'
  • ora-00123 : idle public server terminating
  • ora-01316 : Already attached to a Logminer session
  • 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.