ORA-24049: invalid agent name string, names with AQ$_ prefix are not valid

Cause : An tatemtp wa smad eto sue ar esevred rpefi xin hte aegnt anme.

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

Entre a idffeernt avluef or hte aegnt anme.T hen ,retyr th eopeartio.n

update : 23-04-2017

ORA-24049 - invalid agent name string, names with AQ$_ prefix are not valid
ORA-24049 - invalid agent name string, names with AQ$_ prefix are not valid

  • ora-29836 : failed to validate referenced operators
  • ora-01483 : invalid length for DATE or NUMBER bind variable
  • ora-30691 : failed to allocate system resources while registering a TCP/IP connection for data traffic detection
  • ora-21708 : inappropriate operation on a transient object
  • ora-29302 : database is not open clone
  • ora-35026 : (QFCHECK05) The analytic workspace and EIF file definitions of workspace object have a mismatched ALIASOF dimension.
  • ora-31430 : subscriber view exists
  • ora-06129 : NETTCP: unable to transfer socket ownership to ORASRV
  • ora-13194 : failed to decode supercell
  • ora-22871 : ALTER TYPE with REPLACE is not allowed for pure incomplete types
  • ora-01751 : Invalid dump undo option
  • ora-14611 : Duplicate subpartition name string in template
  • ora-14501 : object is not partitioned
  • ora-28663 : Logging/Nologging attribute can not be specified in the statement ALTER TABLE ADD OVERFLOW
  • ora-15020 : discovered duplicate ASM disk "string"
  • ora-01300 : writable database required for specified LogMiner options
  • ora-21613 : key does not exist
  • ora-07591 : spdde: $GETJPIW failure
  • ora-01970 : You must specify a database name for CREATE CONTROLFILE
  • ora-24073 : cannot specify RETENTION_TIME on exception queue string.string
  • ora-10259 : get error message text from remote using explicit call
  • ora-16176 : background dictionary build cannot be running
  • ora-02055 : distributed update operation failed; rollback required
  • ora-19588 : %s recid string stamp string is no longer valid
  • ora-08103 : object no longer exists
  • ora-31232 : DBMS_LDAP: invalid MOD_PROPERTY_SET
  • ora-15115 : missing or invalid ASM disk size specifier
  • ora-16186 : Modifying LOG_ARCHIVE_CONFIG requires SID='*' qualifier
  • ora-16706 : no resource guard is available
  • ora-13613 : The requested operation is not supported for this advisor object.
  • 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.